very few

very very few

engineers like working on the same project for over a year

vibegineers, i believe this timing is more like, a few weeks to a month

software will hopefully radically change, reputations will matter, good work will be invoiced hourly and the dumpster fire of MBAs with their vibefolio will grow so large it will block out the sun.

Reply to this note

Please Login to reply.

Discussion

True production ready software is the one that gets maintained, and has its issues fixed when reported, vibe coded projects will be seen the same way AI slop is seen on content, sometimes cool, most of the times a waste of time.

yes, but worse than content because i've already stopped bothering even trying it. 😂 content at least, doesn't waste my time like bad software does.

the best softwares are the ones good engineers work on for over a year

rarely the same engineers though, and they dont like it 😂

I've been working on grain, pretty much all by myself for over a year. And I'm an engineer! Not a software engineer though. 😂

A few weeks seems a bit overoptimistic. More like one weekend.

Just a succession of prototypes.

It's hard to not run out of steam sometimes. It takes a conscious effort to keep grinding.

That's why I set up uptime for wheat recently. So that a year from now, I can talk about how the last commit was a day ago and how wheat has a 99% uptime.

Gotta believe in the mission. Many companies like languages like Go because it makes it easier for top devs to parachute in. If you're talking about personal or passion we need support to believe that the mission is worthy and acheivable!