bottlepalm

8 ms·

181.
by bottlepalm 5mo ago
Damn, at 3k a month, that's like 3 years of rent right there.
182.
by bottlepalm 5mo ago
Taxes goes up, insurance goes up, repair costs goes up, and with a 30 year mortgage you lose like 50% the value of the home in interest payments.
183.
by bottlepalm 5mo ago
Ah the classic thinking that 'code documents itself'. It does not. Some devs are so full of themselves they think their code is so good that it is obvious what their intent was. It never is obvious, and just ends up as tech debt.
184.
by bottlepalm 5mo ago
Yes exactly. I don't like Codex not writing comments - and even proactively removing useful comments! There was some change in the last month that causes Claude to write crazy long comments. I routinely have to ask Claude to 'tigh
185.
by bottlepalm 5mo ago
Like I said, we either need more people or some paradigm shift in tooling that allows us to do more with less.
186.
by bottlepalm 5mo ago
Lets see, front end presentation, front end service, frontend api, backend to front end (BFF) api/routing, BFF logic, BFF api, backend routing, backend logic, backend database, worker routing, worker logic, worker storage. And then the
187.
by bottlepalm 5mo ago
How does that work? Isn't writing code and reviewing code things that happen in serial?
188.
by bottlepalm 5mo ago
> You design, Claude writes, Codex reviews, and Gemini doesn't get installed hahahahaha
189.
by bottlepalm 5mo ago
I've worked in large teams for many years and yes it's just like that, but without the time constraint. PR's can only go back and forth so many times. Depending on the reviewer they may phone it in, or focus on different thin
190.
by bottlepalm 5mo ago
Quality is 100x more important than cheaper/faster.
191.
by bottlepalm 5mo ago
No, I find it stimulating. With AI I'm moving faster and producing code at a higher quality than ever before. Don't get me wrong I used to enjoy writing code by hand, but I don't think I would anymore. I don't like writi
192.
by bottlepalm 5mo ago
I do multi-task a bit while AI is running, sometimes working on another feature with AI in parallel, but jumping between reviewing different feature iterations is draining, though not much different than the real world juggling PR reviews f
193.
by bottlepalm 5mo ago
I think you're projecting.
194.
by bottlepalm 5mo ago
This is where the human element is critical, but cause it'll infinite loop review feedback if you let it and the code will easily go off the rails into an over engineered mess. That's why I review the code before/after as wel
195.
by bottlepalm 5mo ago
Oh course it's not black and white, there are many shades of grey in how detailed the design of a feature can be. Often even if I know low level details, I'll only give the AI high level requirements because I want to see how it w
196.
by bottlepalm 5mo ago
I don't have it automated, but I score on minimizing lines of code added, readability of the code, and quality of the architecture.
197.
by bottlepalm 5mo ago
The problem is that I manually review the code before/after the review, as well as review the items to review themselves. You could easily put AI into a review infinite loop if you let it, and you also risk the code base going off the
198.
by bottlepalm 5mo ago
It is.. but so is dealing with issues at runtime, going through weeks of revisions, and dealing with technical debt.
199.
by bottlepalm 5mo ago
$200/month split between Claude Code Max and Codex Pro. Given how many hours a month I spend programming, my hourly rate, the amount of time saved, and the productivity/quality boost - I would pay a whole lot more if I had to.
200.
by bottlepalm 5mo ago
Refactoring is the natural evolution of a growing application. Refactoring too soon, too fast is what we call over engineering. Too little refactoring and your code becomes spaghetti slop. Regardless - the application will change across all
201.
by bottlepalm 5mo ago
Semantics. In reality yes it is the v3 version equivelent in terms of maturity and iteration. I know because I've been doing this for a long time. We are getting to v3 and beyond faster than ever before. In the new world there is no ti
202.
by bottlepalm 5mo ago
Unfortunately the projects are still too big. Projects with hundreds of thousands to millions of lines of code can't be maintained by a single person reviewing all the the changes. And AI only increases the speed of iteration and the a
203.
by bottlepalm 5mo ago
Nothing wrong at all. Some features you can bolt on, and some features fundamentally change how a system works requiring changes at many different levels of the stack. Happens all the time.
204.
by bottlepalm 5mo ago
If you can't understand why the code is done in a certain way from reading it then the code is missing comments or needs to be refactored. Even code you write yourself, given enough time, you will forget the why unless you wrote commen
205.
by bottlepalm 5mo ago
Indeed. AI is bumping everyone up to manager level, and having dealt with long PR feedback cycles with humans for years - I don't mind the promotion. Also shipping a v3 is so much nicer than shipping a v1 and dealing the all the corner
206.
by bottlepalm 5mo ago
One strategy I use in the planning phase is even when I know how I'd implement the solution, I ask the Claude/Codex how they would solve the problem or implement the feature without giving them any clues - and then compare their s
207.
by bottlepalm 5mo ago
A lot of people say you need to go through at least three versions of something before it is mature - and v3 is not something you can design upfront. You need to see v1 both in code, and at runtime. Use it, get the feedback, and iterate. Th
208.
by bottlepalm 5mo ago
I would never imagine this is where programming would be five years ago, but at the end of day having the AI write the code is easier, faster, and results in higher quality. The mental model is still in my head, my brain is overloaded, but
209.
by bottlepalm 5mo ago
Heh it feels like that in a way, and the more complex the feature, the more endless the back and forth reviews can be - there seems to be always some feedback, so you need to decide when to be done with it and commit. You can easily get int
210.
by bottlepalm 5mo ago
Yea I'll take the review feedback from one, validate it, and then copy/paste it into the other session saying like, "hey I got this feedback, what do you think?" So I'm not even telling the other AI the feedback is

More ›