wreath

To me AI conversations are exactly like ones about VIM config etc. ok cool, but show me something cool you built with it, and most importantly something that was worth the cost.

Otherwise, it sucked the air out of everything else especially in tech and startup culture.

Yeah I totally agree. My point was that it can be intimidating as an intro book to the topic. Excellent material otherwise

I don't think this is a good resource for an intro tbh. Unless you are interested in proofs and have some probability basics covered, it feels quite dense.

I liked Principles of Product Development Flow a lot more because it was easier to digest, although it's a different application of queuing theory.

What kind of problems do people solve that require this amount of money per month, let alone per day?

Is anyone reviewing the output of the generated work (PRs, docs etc)?

At work we are literally forced to use AI and it’s part of our performance review. Even though I really like coding by hand, I have to now use AI so I can keep my job. I will try this out though, 2 days per week using AI and the rest handcoding, enough to stave off the inevitable lay off perhaps.

And what of the original author is not there anymore?

Even with enough money, you may not be able to attract/keep talented engineers who are willing to put up with such a work environment (the codebase itself, and probably the culture that led to its state) and who want to ship well built/designed software but are slowed down by the mess.

PMs do different things in different organizations.

In my last job, PMs were responsible for identifying problems that were worth solving and align with the overall company vision and plans within the owned domain, and design+engineering decided how to solve those problems and what to build. Of course with collaboration w/ the PMs (and EMs).

The job before that, PMs wrote jira tickets and nagged engineering when tickets will be delivered. The "what problems to solve and what to build" questions came straight from CEO/CTO.

i see how one they cannot think and feel clearly anymore if your neighbours dream constantly about your elimination. All sides just need to stop with that hatred. It leads to so much pain.

I think by now we all know this is a straw man, considering the disproportionate amount of power both parties have. There is absolutely no excuse left for what Israel has been doing in Gaza.

I dont think parent was questioning it, sounded they were more curious but thanks for explaining because i wasnt sure myself.

Re: safe from LLMs, id imagine the level of rigor in sys engineering is higher so maybe people are more wary of LLM produced code?

Yeah to get the definitive answers, sure AI is quicker. Google is more like the librarian pointing you at possibly good resources to get your answers from after reading the materials and there are a lot of good learning opportunities there. LLMs just give you the answer and robs you of those opportunities.

Technical debt is never a problem now since only AI reads code /s

Exactly! How do other parts of the organization deal with this avalanche of features in terms of documenting, pricing and packaging, marketing, selling and getting feedback on them. How do users adopt these features and incorporate them in their workflows so fast? Never in my career was the speed of writing code alone the bottleneck.

It's hard to be engaged when you are constantly jumping from one thing/prompt to another vs you are actually doing the work.

I dont even think you need to be neurodivergent or anything to answer this question like the parent’s cofounder did.

From one side, we call ourselves problem solvers, on the other hand we are not satisfied with simple solutions to these problems. If im interviewing for a job, i should be expected to behave and solve hypothetical problems the way id do it on the job. If that screws up your script, you probably suck at hiring and communicating your expectations.

Thats interesting. While i do get mentally tired after a session of focused coding, i feel like i have accomplished something. Using AI for coding feels similar to spending hours doom scrolling reels. Less engaging but Im drained as hell at the end.

I think reading queries that are always served from cache are CPU bound because it also involves locking the buffers etc and there is no I/O involved.

You don't have to take 5 years off for it. Just continue same old business (assuming you don't have outside pressure to use this slop-machine) and keep your skills and judgment sharp until the tools and workflow stabilizes, and most of all, the money to fuel this hype runs out.

We already knew this, but in the light of this AI hysteria we pretend like coding speed has always been the bottleneck

And not to mention that most tests available to AI training is trash, so no wonder AI-generated tests are not only worthless but costly in terms of false sense of reliability.

He’s been building tech companies for 20 years, he sure knew smaller teams move faster when he was hiring thousands of more people during covid

Right on.. we already have open source alternative to all the major SaaS out there and companies still opt for the SaaS option instead to avoid the headache of self-hosting and all the other stuff. The extra resources that AI affords you will be directed to building more features for your customers.

This has been my experience as well. I get drained at the end, and I spent most of my energy and thinking capacity dealing with the LLM instead of the problem space.

More like the fresh parents who start schooling everyone else on how to parent…

Then what will AI be trained on in let's say 20-30 years? Old code? It's own AI developed code for vibe coded projects?

I’ve seen variation of this question since first few weeks /months after the release of ChatGPT and I havent seen an answer to this from leading figures in the AI coding space, whats the general answer or point of view on this?

so is the 10-20% in velocity worth the money and the process-complexity added? I'm assuming you're measuring your own velocity, not your team's, since that includes time to review and deploy etc.

You can change the max_connections in RDS though. The default is insanely high and I have no idea what it is that way. 4vCPU instances running with 5k max connections iirc, I have never seen an instance this size handle more than 100-200 concurrent connections on a CPU bound workload.

What often baffles me with engineers and especially engineering managers is that they don't derive the estimates from metrics of prior projects, especially for long running teams (as opposed to project teams). You don't need to estimate down to the minute, but you already know how many tickets/work items the completes at a given time interval with how many people in the team etc. This should give a rough estimate of how long a project might take, and you can confidence intervals like 90% confidence we finish this in 3 months, 70% confidence we finish it in 10 weeks, 50% confidence in 6 weeks and 10% confidence we finish it in 2 weeks.

IMO this is also a better way to communicate with stakeholders outside the team instead of committing to a specific date. It gives more context and clearly communicates that this is a probability game after all since there are quite few moving variables.

Why do that if your competitor already has it? I'd just go talk to the competitor instead. If you aren't able to ballpark when the feature will be done, why should I trust you will once I pay part of the price?

I actually started doing this for side projects that I use as a vehicle for learning and not necessarily to solve a problem and it's been great. 1) I don't feel like I just commissioned someone to do something and I half-ass checking it and 2) I actually do learn about new stuff as well even though sometimes it distracts me from the goal (but that's on me)