suraj

Back in 2022, my at-the-time workplace decided to sponsor folks for AWS certifications. To get people to start studying for the test, they asked that folks pick one of the many services or configurations you can/might/will end up using on AWS and do a 1-hour group discussion on it.

And this code in this branch was, one way or another, a stranger's labour. It was someone else who had gone to the trouble of learning and making and sharing. What did I get out of using an LLM for my task? Nothing. I spent a few dollars and got some code, but having the code was not the point.

Back in 2022, my at-the-time workplace decided to sponsor folks for AWS certifications. To get people to start studying for the test, they asked that folks pick one of the many services or configurations you can/might/will end up using on AWS and do a 1-hour group discussion on it.

I decided to give Claude a shot at making what I was trying to make. I bought a few dollars' worth of credits, configured the auth token, and let it rip. It took a few minutes, and in a separate git branch, made what I was trying to make. It felt gross. It wasn't me who made this.

Back in 2022, my at-the-time workplace decided to sponsor folks for AWS certifications. To get people to start studying for the test, they asked that folks pick one of the many services or configurations you can/might/will end up using on AWS and do a 1-hour group discussion on it.

Stuff like that used to happen often at that workplace. I'm glad I left. The places I've worked since then have been better, but there are always people like that. LLMs have given some of them a lot of leeway towards this behaviour. How do we expect to build a community of people actually interested

Back in 2022, my at-the-time workplace decided to sponsor folks for AWS certifications. To get people to start studying for the test, they asked that folks pick one of the many services or configurations you can/might/will end up using on AWS and do a 1-hour group discussion on it.

At the end of my slideshow, before starting the broader discussion with the dumb hypotheticals and so on, I'd asked the group at large, "What even is a VPC?" — informally, almost jokingly, in an effort to put everyone at ease. I saw a couple of colleagues start typing. Likely into Google search.

Back in 2022, my at-the-time workplace decided to sponsor folks for AWS certifications. To get people to start studying for the test, they asked that folks pick one of the many services or configurations you can/might/will end up using on AWS and do a 1-hour group discussion on it.

Which took all of 30 minutes, with the rest remaining for questions and activities. With the number of folks who'd already done presentations in the weeks prior, I wanted to keep things lively. Silly questions and hypotheticals welcome. Like, what if we want an EC2 instance to have 2 IP addresses?

Back in 2022, my at-the-time workplace decided to sponsor folks for AWS certifications. To get people to start studying for the test, they asked that folks pick one of the many services or configurations you can/might/will end up using on AWS and do a 1-hour group discussion on it.

I was wrong, of course. It was a bit of fun to do the reading on VPCs and then CIDR blocks and the general principles of designing and building networks — all very interesting stuff, a rabbit hole leading down into a veritable warren of topics that I wish I'd taken better notes on. But anyway.

Back in 2022, my at-the-time workplace decided to sponsor folks for AWS certifications. To get people to start studying for the test, they asked that folks pick one of the many services or configurations you can/might/will end up using on AWS and do a 1-hour group discussion on it.

Lately starting to become aware of how much work stuff I actually do sort of on autopilot where I’m not consciously thinking about what message I’m typing or code I’m writing or such. Gets jarring when I’m doing this stuff while on a call because I see what I’ve done but don’t remember how.

Going to be a bit crude here but the disconnect between management and ground-level folks when it comes to the conversation about (effective) use of GenAI might vanish if the latter were allowed to call out the former for being stupid fucks by actually calling them "stupid fucks". Might help a bit.

To add here though, I think I understand some of why it's going this way. The dream is that GenAI trivializes software development (and maybe most development/processes) that have been outsourced, right? And not speaking purely geographically here. This applies to all sorts of large organizations.

Going to be a bit crude here but the disconnect between management and ground-level folks when it comes to the conversation about (effective) use of GenAI might vanish if the latter were allowed to call out the former for being stupid fucks by actually calling them "stupid fucks". Might help a bit.

It's necessary work. And the people who work on these systems, with modern tools, modern languages and frameworks that were created to make programming more accessible, I don't think they're trained/motivated to approach GenAI tools with the caution+rigor that celebrity programmer of the day might.

Going to be a bit crude here but the disconnect between management and ground-level folks when it comes to the conversation about (effective) use of GenAI might vanish if the latter were allowed to call out the former for being stupid fucks by actually calling them "stupid fucks". Might help a bit.

Anyone from a third world country who's done some basic reading in high school knows that statements like "90% of code will be written by AI in a few years" was wished upon a shriveled monkey's paw — I don't understand why so many programmers with online clout don't seem to think that way

Going to be a bit crude here but the disconnect between management and ground-level folks when it comes to the conversation about (effective) use of GenAI might vanish if the latter were allowed to call out the former for being stupid fucks by actually calling them "stupid fucks". Might help a bit.

"code is just a means to an end" yes "write code but be prepared to throw it away" very true "we now have tools that write code faster than you can comprehend (or read), said tools have more memory than you but less than they need for whole tasks — we think this'll make you faster" wait what?

Going to be a bit crude here but the disconnect between management and ground-level folks when it comes to the conversation about (effective) use of GenAI might vanish if the latter were allowed to call out the former for being stupid fucks by actually calling them "stupid fucks". Might help a bit.

In my (limited) experience, ever since GenAI coding tools have become mainstream the conversation about long-term maintenance has gone right out of the window and it's all become a discussion about generating the right solution or prompting the model right or figuring out the right context...