Looks like my approach is as old school as it gets. For complex piece of work, the only way to be in flow for me is when I'm driving the engagement. I start with a high level requirement and a high level design plan to achieve it. I also provide constraints that needs to be satisfied (efficiency, performance, cost, scale etc) and write it all into a markdown document and ask LLMs to review it, find blindspots and refine it until I can get a detailed design for that phase.
Then I pass that to another LLM provider to review and check for any bloat that can be cut or blindspots that need to be addressed.
Finally I get a test plan to help me test different components directly and in debug mode. I then ask LLMs to implement in stages where I can test them in small components as possible.
I think I end up spending more time (easily 2x) than hand rolling. But the upside is the design is more thought out compared to hand rolled code. It has fewer accidental complexities and I have a clear mental model of the entire design that can also be shared to others through the document
Assuming you live in a crazy big house (1000 m2), it cleaned your house 74000 times. Given S5 was released 8 years ago, even approximating it to 10, that's 20 times a day. I can imagine it taking about an hour to do one clean run. Jesus, did it ever stop cleaning
My sense is you only submit if you are in the business of selling supercomputing cluster (IBM, Cray). If you are a consumer or build to consume internally, you would care less.
The default must be pull, unless opt in for push. At the moment I would like notifications once a day or once a week for most apps. But instead I ha e turned it off completely, because of the push abuse. If I can configure to pull all the notifications on a predetermined cycle, it makes my life even better
This, we learn natural language like English first before we can use it to express ideas, argue for or against those ideas with evidence. The problem is not teaching a programming language, the problem is stopping there and not teaching how to use it to solve real problems.
Humanity has been using steel for over a millenia, however it's only in the past 100 years or so we have a good understanding of how carbon interacts with iron at an atomic level to create the strength characteristics that makes it useful. Based on this argument, we should not have used steel, until we had a complete first principles understanding.
No disrespect to the person, but this seems to be written by someone who has spent their life in academic bubble, without having to deal with people and entities with diverging interests and the impact of time on any decisions. I'm sure many artists will love to spend more time perfecting their art, based on their subjective interests. However, if they prioritize that, without understanding what their customer wants, they will go bankrupt. Nourish your interests through your hobbies. If they align with money making capability, you are one of the lucky few. For a significant majority, they do not align.
Technical feedback yes, but always reject any career feedback from your advisor since the data shows it's unlikely a good model for future career success
So Mozilla is not part of this consortium, i'm guessing for deliberate reasons to make safari and chrome the default browsers. I don't think Firefox can survive the upcoming attacks, without robust support from foundational AI providers to secure the browser.
Best way to deal with this is take them to small claims court. If enough people do this, They have to send representations that will cost them enough to stop such nonsense.
Micropayments gives me flexibility that subscription doesn't. I'm happy to pay $5 a month just to read Matt Levin. I'm not paying $40 for Bloomberg subscription. It also gives publishers signal on what really users care about and more importantly what are they willing to pay for. Maybe, there is a truly crypto market here for micropayments without the overhead of operators like Stripe
Whenever technically more capable folks diss the growth of a non technical person into bigger roles, I'm obligated to post this Steve Jobs video being asked about Java.
My nitpick is that thinking and dreaming about solving the problem is part of doing. Its the planning phase. Skipping This planning phase in Software engineering is the root cause of most Day 2 operations issues. However I agree that thinking or announcing about outcome is not doing.
Then I pass that to another LLM provider to review and check for any bloat that can be cut or blindspots that need to be addressed.
Finally I get a test plan to help me test different components directly and in debug mode. I then ask LLMs to implement in stages where I can test them in small components as possible.
I think I end up spending more time (easily 2x) than hand rolling. But the upside is the design is more thought out compared to hand rolled code. It has fewer accidental complexities and I have a clear mental model of the entire design that can also be shared to others through the document