Yeah that feels like the right approach to enable the code generation to test itself which then becomes a matter of specification and functionality definition instead of worrying about code quality.
Are you doing all of this in cursor or something like Claude code?
There is a common theme of "the end result is all that matters" but there are pretty big long term repercussions of design and implementation choices. For side projects and POC experiments this feels like the right approach but the risk flip flops for large scale projects that have the more risk associated with them. Maybe it is just through testing and validation checks?
I posit that most software isn't large scale projects.
Certainly mine isn't. But I've still generated hundreds of thousands of lines of code.
But no one will ever read them. And solid engineering defines the interfaces between them. So we specify the ins and outs and let the rest take its course.
> there are pretty big long term repercussions of design and implementation choices
At least this part I am still specifying. It doesn't get to choose its own technologies. It generally includes the architecture in the plan that I review.
Me too. I specify everything like that. Which database to use, which style of database to use, etc. the sort of thing a Team Leader would pick (after consulting the team, of course).
I've been coding since the 8-bit days.
With the added benefit I can specify, "let's try using this stack this time." I haven't got to spend two months learning it to get to MVP.
Not trying to diminish the work at all because it works well but I hate this UX pattern. There is likely a reason this hasn't been done. If it wasn't for the pick -> scroll -> place instruction I would have no idea how to use it.
It’s possible, but maybe unlikely. A tower is hard-wired to fiber, and immensely cheaper than a satellite, per pound. Satellites are always going to be more expensive than land based equipment, and cost is critical here, plus fundamentally more powerful with better data connections to the trunk.
> Put simply, it's all about electrons. For data storage and transfer to happen on any device — smartphone, desktop PC or internet server — you need electrons. And while these particles aren't exactly massive, they do have weight: approximately 9.1 x 10^-31 kg. Take that and apply it to an ordinary email, which comes in at about 50 kilobytes: You need 8 billion electrons. Sounds like a lot but only comes in at two ten-thousandths of a quadrillionth of an ounce.
> Seitz scaled this up to determine the weight of all internet traffic and got 50g, or the weight of one strawberry. Applied to all the stored information online, which is around 5 million terabytes, the number is just 0.2 millionths of an ounce
I like the idea of having a four day work week that everyone is expected to work and one day that is a flexible optional deep work type of day. No required meetings and no shipping etc. The idea being that people can choose to take it off if they want to or work half the day etc.
reply