51–60 of 110 posts
The manager's job is to manage multiple programmers to let them write code. A good manager should focus on management rather than write code himself.
But keep doing for many years will make manager out of touch from modern coding so he is starting to mismanage people or issue technically wrong order.
For me the biggest issue with AI coding model is not that it writes code, or how it writes code, or whether it will replace me or not. I mean, these are real problems, but just not the ones that makes the difference to me daily. Instead what sets my feeling about the AI is simple: the experience of working with AI models, because it's the worse experience of my life so far. Every single LLM will make up stuff, go dow…
> doing ALMOST what I asked it to do, but just not quite This is my exact experience. LLMs get 95% of the way to my personal quality bar, and for simple tasks 100% of the way. More complex things, no. This means that, in practice, I end up having to understand the code pretty much as much deeply as I would anyway, without agents. So, essentially, my experience is that it's automated away the easy bits, but left the h…
Earlier quoted context omitted.
Yeah it’s gonna be funny looking back in ~5 years. And probably embarrassing for some. “Age of AI” but most people actively dislike it and hasn’t had a clearly positive impact on the economy after ~4 years.
How do you want to define "clearly positive impact on the economy"? NVDA and a bunch of other stocks are way up. If you got in early, you're sitting pretty. I'd call that positive for those lucky people.
Earlier quoted context omitted.
This is not true. First of all, not all software is written in the context of a FAANG company with “feature requests”. Secondly, writing software is similar to the process of design , this comment reads like “the vast majority of handbag design is mapping problem between features and leather”, ignoring that both the design and implementation can be rewarding to work on. Eg. I’m working on a program for myself and the…
> I’m working on a program for myself and the overall architecture of the program as well as some parts of its implementation are clever and compose well to make the codebase a joy to work in. I am not simply “mapping features to mundane technical details”. You said it: you are working on a "program for yourself". Hobbyist craft programming will always be here. The question is what kind of software engineering will b…
Earlier quoted context omitted.
| type errors, scope issues, import resolution, dependencies. I write code myself and use the LLM to find mistakes then fix them manually. I recommend inverting the conventional wisdom on LLMs: 1. Don't use it to write code. It's a terrible programmer. But it's an intelligent rubber duck and a solid analysis tool. 2. Write the code yourself. It'll go faster than figuring it out as you go along. It's just typing if yo…
> Don't use it to write code. It's a terrible programmer. I see this sentiment often, and I’m honestly not sure where this comes from, as it’s really not been my experience. I feel like this must come from people feeling threatened and just moving the goals posts, or not knowing how to use the tools effectively.
1) lies and/or cope
2) lack of actual software ability, therefore over evaluating your own skill
3) haven’t actually used LLMs, and want to do a “look at me I’m so unique and different”
I roll my eyes whenever someone says “AI bad” “AI sucks” “AI can’t replace me”
Yeah. Load of
How does Andrew manage being a full-time software developer and an author? Both jobs are so cognitively demanding.
As for how I did it, I would wake up very early and put in a few hours of writing, then I would put in a full day's work at the office. After my first twelve years or so in the industry, coding was almost second nature and came quite easily. Also, I do much of my writing and programming in my head while I'm walking, running or biking. (I bike to work and back every day.) By the time I sit down to write or code, I already know what I'm going to write, so it's just a matter of getting it through the keyboard.
But yeah, do both for a few years and it really taxes your brain. In both novel writing and programming, you're carrying an entire world in your brain: the plot and characters are one world, the architecture of the software you're working on is another. By 2025, I truly, literally felt like I needed to be shipped off to a madhouse in the countryside. A hundred years ago, people used to call that "the rest cure for a nervous breakdown."
Anyway, cutting back to part-time work has been a huge help. Sanity restored.
Earlier quoted context omitted.
| type errors, scope issues, import resolution, dependencies. I write code myself and use the LLM to find mistakes then fix them manually. I recommend inverting the conventional wisdom on LLMs: 1. Don't use it to write code. It's a terrible programmer. But it's an intelligent rubber duck and a solid analysis tool. 2. Write the code yourself. It'll go faster than figuring it out as you go along. It's just typing if yo…
> Don't use it to write code. It's a terrible programmer. I see this sentiment often, and I’m honestly not sure where this comes from, as it’s really not been my experience. I feel like this must come from people feeling threatened and just moving the goals posts, or not knowing how to use the tools effectively.
If you see people saying it often, but you are convinced they are just feeling threatened, what AI generated software would point to to say, "Look at this! Definitive evidence that they are just coping!"
I’ve been successfully shipping software since 1998. I just got the first payment on a greenish-field software product I’m doing on the side solo (that I couldn’t have done solo in 2019 without the tools). This is my workflow: 1. Client asks you to add a feature(s) 2. Spend two weeks unpaid walking the client through scoping down to the most minimal viable set of features that tests the business hypothesis and roadma…
You’re the founder and CEO of an AI startup but also vibecoding side gig work?
In addition to many other things (like being a dad and farming peaches - hopefully 50 lbs this year)
I’ve been successfully shipping software since 1998. I just got the first payment on a greenish-field software product I’m doing on the side solo (that I couldn’t have done solo in 2019 without the tools). This is my workflow: 1. Client asks you to add a feature(s) 2. Spend two weeks unpaid walking the client through scoping down to the most minimal viable set of features that tests the business hypothesis and roadma…
For websites this work. But now you are a core developer of the GTA6 engine. Your task is to create a fast efficiënt occlusion mapper. One that works from all angles. Has cavities and rt support. Good luck doing this with Claude. It's not gonna achieve this. Because only a handful of games achieved this partly. Maybe next gen AI can do it. But for complex tasks LLMs are still not good enough.