“We're in the realm where we might be essentially killing off everything within that first hour or two."

I finally shipped the first version of my freelance landing page. The funny part? I spent weeks thinking I had a design problem. I didn't. I had a content problem. The layout is good enough. The copy is good enough. The CSS is good enough. What the page really needs now is more real projects. Instead of redesigning it again, I'm going to spend my time replacing concept work with actual client work as it comes in. Sometimes the next version isn't another refactor. It's simply experience. 🔗 https://lksvn.com.br/freelance/

Before we start This is a series about the intermediate results of an ongoing effort, not a finished story. It isn't an academic paper — it's a record of real engineering work and the insights that emerged along the way. Also, it's not about AI generating code. The AI angle here is about investigation and research — a careful, governed use of AI as a tool, not an autopilot — something I'll come back to in the final part. A word on why now, with the project still unfinished: details fade — the small technical decisions, the intermediate observations, the context in which a given call was made. Writing this down while the work is still ongoing is partly how I keep that context from slipping away. And that context matters: it's a reminder that every past decision, mine or anyone else's, was made for reasons that made sense at the time. One more note: none of this happened instead of product work. All of it ran alongside building new features and fixing bugs — the roadmap never paused for it. On confidentiality: I don't name the Customer, and I avoid any personal data or details a competitor could use. For the same reason, I don't mention anyone by name and refer to colleagues only by role. I won't name them, but I want to acknowledge up front that much of what follows was only possible thanks to the people I work with. The numbers are approximate and rounded — the point is the order of magnitude and the reasoning, not the exact figure. And a framing to carry through the series: at this scale, optimization is less a sprint than a marathon — yes, probably the most overused metaphor around, but here it genuinely fits: steady pacing beats sprinting, and you get there one careful step at a time. How I ended up here I'm a software engineer, and I've spent most of my career close to backends and databases. I've also led teams as a technical team lead — though over time I've deliberately shifted back toward more hands-on technical roles, which is where I'm most effective and m

Runlayer is suing Rippling after Rippling evaluated the startup's MCP gateway product and then opted to build one itself.

The final condition will shock you! (It won’t. It’s taxes.)

submitted by /u/Refresh98370 [link] [留言]

Analysis of 15 million real AI interactions finds most tasks at most jobs are unaffected.

submitted by /u/Happycodeine [link] [留言]