141–150 of 432 posts
Earlier quoted context omitted.
Are you paying for the higher end models? Do you have proper system prompts and guidance in place for proper prompt engineering? Have you started to practice any auxiliary forms of context engineering? This isn't a magic code genie, it's a very complicated and very powerful new tool that you need to practice using over time in order to get good results from.
That's the beauty of the hype: Anyone who cannot replicate it, is “holding it wrong”.
Reading articles like this feels like being in a different reality. I don't work like this, I don't want to work like this and maybe most importantly I don't want to work with somebody who works like this. Also I am scared that any library that I am using through the myriad of dependencies is written like this. On the other hand... if I look at this as some alternate universe where I don't need to directly or indirec…
Imagine a future where creating software is about the designing the UX, overseeing the architecture and quality assurance. Implementation is farmed out.
The only thing that should matter in software development is: does it work to spec? Why are these chatbots that mangle data 1/3 to 1/2 of the time getting their budgets 10x over and over again? This is irrational. If the code mangles data this bad, it's garbage.
Unless you've never written code outside of a classroom you should know how unbelievably wrong this is.
I'm loving the new programming. I don't know where it goes either, but I like it for now. I'm actually producing code right this moment, where I would normally just relax and do something else. Instead, I'm relaxing and coding. It's great for a senior guy who has been in the business for a long time. Most of my edits nowadays are tedious. If I look at the code and decide I used the wrong pattern originally, I have to…
So more work gets to penetrate a part of your life that it formerly wouldn't. What's the value of “productivity gains”, when they don't improve your quality of life?
https://github.com/jerpint/context-llemur
The idea is to track all of the context of a project using git. It’s a CLI and MCP tool, the human guides it but the LLM contributes back to it as the project evolves
I used it to bootstrap the library itself, and have been using it more and more for context management of all sorts of things I care about
Reading articles like this feels like being in a different reality. I don't work like this, I don't want to work like this and maybe most importantly I don't want to work with somebody who works like this. Also I am scared that any library that I am using through the myriad of dependencies is written like this. On the other hand... if I look at this as some alternate universe where I don't need to directly or indirec…
But you also can't not swim with the tide. If you drove a horse-buggy 100 years ago, it was probably worth your while to keep your eye on whether motor-cars went anywhere. I was super skeptical about a year ago. Copilot was making nice predictions, that was it. This agent stuff is truly impressive.
There's a huge disconnect I notice where experienced software engineers rage about how shitty things are nowadays while diving directly into using AI garbage, where they cannot explain what their code is doing if their lives depended on it.
Earlier quoted context omitted.
I think the agent stuff is impressive because we are giving the AI scaffold and tools and things to do. And that is why it is impressive because it has some directive. But it is obvious if you don't give it good directives it doesn't know what to do. So for me, I think a lot of jobs will be making agents do things, but a lot won't. i think its really strange that people are all so against all this stuff. it's cool ne…
People are afraid that instead of skilled craft guild members they will become assembly line workers like Charlie Chaplin in Modern Times. And in 10 years unemployed like people in the Rust Belt.
As has been the case for all those jobs changed by programmers, the people who keep an open mind and are willing to learn new ways of working will be fine or even thrive. The people rusted to their seat, who are barely adding value as is, will be forced to choose between changing or struggling.
It’s amazing to me all the Luddite developers who are “against” all this. Completely new ways of programming are forming, completely new ways of computing and the best the luddites can do is be “against it”. A revolution came along, a change in history and instead of being excited by the possibilities, joining in, learning, discovering, creating …… the luddites are just “against it all”. I feel sorry for them. Why be…
Because computers can be used to run programs.
You feel sorry for them. I feel sorry for the future.
Earlier quoted context omitted.
The way I ended up paying for Claude max was that I started on the cheap plan, it went well, then it wanted more money, and I paid because things were going well. Then it ran out of money again, and I gave it even more money. I'm in the low 4 figures a year now, and it's worth it. For a day's pay each year, I've got a junior dev who is super fast, makes good suggestions, and makes working code.
> For a day's pay each year For anyone trying to back of the napkin at $1000 as 4-figures per year, averaged as a day salary, the baseline salary where this makes sense is about ~$260,000/yr? Is that about right lordnacho?
Earlier quoted context omitted.
Imagine a future where creating software is about the designing the UX, overseeing the architecture and quality assurance. Implementation is farmed out.
But the architecture is the important (and hard) part!!! Not the UX!
Users see and care about the UX; the product. They only notice the engineering when it goes wrong.