4 ms·
My workflow used to be as most did agents in the command line, whenever bugs happened i tried to enforce verification layers, preferably deterministic to make s
by jwpapi 6mo ago
My workflow used to be as most did agents in the command line, whenever bugs happened i tried to enforce verification layers, preferably deterministic to make sure it doesnt happen again. I dug deep into linting, biome and type rules. I tried to make the rules as tight as possible. I also thought about general design patterns, boundaries, enforcing these rules with file names and probabl some other enforcements.
For some of you that might be the obvious consequences and I don’t claim I’m right. I’m just writing down my feelings in that case as they’ve massively switched and I feel very disconnected to the world right now, reading everything that companies do, people post and write.
I have a huge distrust, and I understand that this is a skill issue, but the question still remains. When I don’t have the skill to build a good app, what is my best bet. To hope AI does it for me or to grind and learn?
Re Strauva I didn’t game it. I just used Claude Code everyday 12 hours approx.
Now I’m back in the idea and I sleep much better, I feel master of my codebase and my business domain again and most clearly have a tremendously better mental model about how things work and should work.
I utilize auto complete and auto next edit and I chat with AI in a browser window. I make it a habit to test every assumption fast (custom shortcuts in my idea (alt + gv = generate vitest, creates test file from every function, ctrl + t to run) AI throws at me and in new domains.This gives me a fast feedback loop to learn new stuff and makes it more likely I’ll remember.
Like have you seen cracked coders working, they are like fast apm coders and worlds more accurate then AI.
I try to learn stuff from the bottom up. After a while its faster for me to code it than to ask ai and wait for exploration and have to go through review iterations.
- krapp 6mo agoIf you hate AI, don't use AI. If you aren't being forced by your employer, just don't use it. If you do find a way to get AI to generate a "good app," that won't do anything for your own skill. It sounds like this concerns you. If you actually want to improve your skill you need to grind and learn. The only thing you'll learn using AI is how to use AI. 12 hours a day doing something you hate? That seems like an addiction. And it seems like more work than actually doing the work would be.
- bigyabai 6mo ago> When I don’t have the skill to build a good app, what is my best bet. To hope AI does it for me or to grind and learn? You can do both. I can't design a UI to save my life, but I know how GTK's backend works and I can pick the widgets I like from a gallery: https://gnome.pages.gitlab.gnome.org/libadwaita/doc/main/widget-gallery.html https://gnome.pages.gitlab.gnome.org/libadwaita/doc/main/wid... If I can describe the architecture/stack that I want for an app, most AI models can build the desktop app for me. You have to remain conscious of the tools you're using, but AI can produce great boilerplate for this type of rote programming. > Like have you seen cracked coders working, they are like fast apm coders and worlds more accurate then AI. I've worked with 10x engineers before, most of them were not Carmack-level geniuses. They simply understood their stack and stayed laser-focused on the goal. 10xers are impressive because they're specialists, and most of them go back to the 1-2x level if you force them to use technology they don't understand.