Thomas Bonnin

A software engineer I interviewed yesterday just changed everything... Let me explain: Yesterday, I was on an interview with Frank R.. A software engineer we were talking to for the new Full-Stack Engineer role started telling us about how much he loves the platform. He told us he was turn his favorite song lyrics into the short-form videos on the ossa.ai platform, and then sending them to his wife. Right away, my founder cap was put on, and we started asking questions about what he liked and what he thought could be better. One thing he mentioned was that the landing page could be more clear about what the product does. He was right. Our headline on the landing page was currently "The #1 AI-Tool for Short-Form Content Creators." That headline doesn't tell a new visitor what the product does. Right after the call, I created a ticket in the engineering backlog for our Head of Growth, Brennan Duncan, to change the headline to "Text to Short-Form Video In Minutes." Since that conversation yesterday morning, we have seen a significant jump in conversion rates. Moral of the story? Always be learning and listening to your users. P.S. - We just dropped a massive new feature that no other company in the world has thought about trying to create. You can check it out below. ⤵ https://lnkd.in/gZh_bPpM

21

7 Comments

I have been thinking about "Why, after 6 years, I'm over GraphQL" (https://lnkd.in/g_XDCvbQ). I faced many of the same issues with my GraphQL implementations but came to a different conclusion that led to Exograph (https://exograph.dev/). ❗ Problem: GraphQL authorization is a nightmare to implement. ✅ Solution: A declarative way to define entity or field-level authorization rules. In Exograph, you define authorization rules alongside your data definitions. This not only makes it easy to audit authz rules, but lets you lean on the engine to enforce them. ❗ Problem: GraphQL queries can ask for multiple resources in a single query, overwhelming the backend. ✅ Solution: Trusted documents, query depth limiting, and rate limiting. Exograph supports trusted documents/persisted queries and other mechanisms to control the load on your backend. ❗ Problem: GraphQL queries can overwhelm the parser. ✅ Solution: The same solution as above. You can control the load on your parser by using trusted documents and limiting query depth. ❗ Problem: GraphQL queries can lead to the N+1 problem. ✅ Solution: Defer data fetching to a query planner. The classic and dreaded N+1! Exograph uses a query planner to ensure that you never run into this. ❗ Problem: Balancing authorization and the N+1 problem can be tricky. ✅ Solution: Make authorization rules a part of the query planning process. By making authorization rules a part of the query planning process, Exograph ensures that you never fetch data the user is not authorized to see. ❗ Problem: GraphQL makes it quite hard to keep code modular. ✅ Solution: Reduce the amount of code by leaning on a declarative approach. More code, more problems! In Exograph, you write only a few hundred lines of code to define even complex data models. ❗ Problem: GraphQL makes balancing authorization, performance, and modularity tricky. ✅ Solution: Simplify implementing GraphQL through a declarative way to define data models and authorization rules. This is the core of Exograph: declarative data models and authorization rules. Read the full blog post at https://lnkd.in/gBwpXMHF

11

3 Comments

Carta's data is ....off? Coastal Recruiting communicates with hundreds of engineers weekly, primarily in New York and San Francisco. We consistently encounter software engineers with 2-6 years of experience requesting base salaries between $180,000 and $250,000, plus equity. Perhaps "misleading" is a better term, as I frequently hear founders saying, "But Carta indicates we can hire this engineer for $140,000 to $160,000." We then observe Seed/Series A companies paying $200,000 to $300,000 for top talent. The disconnect may stem from the fact that companies raising funds from Sequoia, Khosla, Founders Fund, Lightspeed, a16z, KP, Greylock, Index, NEA, Lux, and others are not seeking what 95% of the companies providing data to Carta are seeking. These companies are looking for the top 0.01% of engineers. I say all this while also acknowledging my appreciation for Carta. I value the data and charts it provides, but it's important to remember: "There are three kinds of lies: lies, damned lies, and statistics."

26

9 Comments

The Automation Takeover: Are Software Engineers Becoming Obsolete? The speed at which LLMs have dominated the industry creates evidence of substantial change, including the evolving role of the software developer. from a 10,000-foot view, what is this signaling for what’s to come for jobs across sectors? LLMs are not just tools for generating text; they are becoming increasingly adept at understanding context, interpreting nuance, and engaging in meaningful conversations. This expansion of capabilities raises profound questions about the future role of software engineers. Are we entering an era where LLMs will take on more responsibilities traditionally handled by human developers? How will this impact the skill set required in the tech industry? Hessie Jones Jones explores the implications of LLMs' rise and the potential transformations awaiting the software engineering landscape in her thought-provoking piece. Check the first comment below. #ai #chatgpt #automation #softwareengineering #forbes #innovation

4

2 Comments

With the announcement today that Momento's Topics has gone GA, wanted to bring this content back up to the front. If you are looking for rock solid consistency, amazing performance, and the option to bring your own language to connect to their SDK, you need to be checking it out. Here's an article I wrote about Topics and Webhooks with #rust and their SDK https://lnkd.in/ghHuR-cC

13

1 Comment