1,375 karma · joined February 23, 2010
> The developer does not review or edit the code, but solely uses tools and execution results to evaluate it and asks the LLM for improvements. Unlike traditional AI-assisted coding or pair programming, the human developer avoids examination of the code, accepts AI-suggested completions without human review, and focuses more on iterative experimentation than code correctness or structure.
Even within techno (my favorite genre), which is already a quite narrow genre in terms of sounds, the variety of novel sounds birthing new techno sub-genres over the last 10-15 years has been wild.
Agreed. And strongly related to your other comment about selfies/bugs/flowers/boring landscapes…
One of the best pieces of advice for leveling up from novice snapshots to compelling photographs is: take photos about things, not photos of things.
Purposefully including people in the frame goes a long way to make photos more interesting because it instantly attaches a narrative.
I’m curious what you do with this information. Can you share?
You said: “Around the xp times, unit tests were not per-method.”
Beck said: “Unit tests are usually individual methods”
“Unit tests are small tests, each one exercising a little piece of functionality. The units tested are usually individual methods, but sometimes clusters of methods or even whole objects.”
Extreme Programming Explained: Embrace Change, 2nd Edition (2004) Kent Beck
It's not surprising there's a strong correlation between "rich people" hobbies (horses, golf, tennis, sailing, etc.) and health outcomes/longevity.
Counterpoint: my wife owns an accounting firm and publishes a lot of highly valuable informational content on their website's blog. Stuff like sales tax policies and rates in certain states, accounting/payroll best practices articles, etc. I guess you could call it "content marketing".
Lately they have been getting highly qualified leads coming from LLMs that cite her website's content when answering questions like "What is the sales tax nexus policy in California?". Users presumably follow the citation and then engage with the website, eventually becoming a very warm lead.
So LLMs are obviously not search engines in the conventional sense, but it doesn't mean they are not useful at generating valuable traffic to your marketing website.
If everyone was able to afford a Rolex or a 911, they wouldn’t be cool anymore because their unattainability is what makes them desirable.
That said, even if I could afford a GT3 RS or a Daytona, I would never play their stupid game to get one.
Only if population is held constant.
Housing supply is inelastic, but housing demand is somewhat elastic. As seen in Denver, an increase in housing supply would decrease prices. But those lower prices will increase demand from people that want to live in Denver but previously couldn’t afford it.
If you go to the Rolex subreddit, it's full of people getting waitlisted for watches they want to buy and excitedly posting when they finally "get the call" from the dealer — sometimes years later — that they are now allowed to buy the watch. It's a common "strategy" to buy lesser watches to ingratiate oneself with the precious Authorized Dealer™ demigod so that one day you might be able to buy the watch you actually want.
Go search /r/rolex for the phrase "got the call" and prepare to cringe.
This is strange to me. You could give me 100 chances to guess which “mind-altering drug” you are thinking of and Adderall wouldn’t cross my mind. Amphetamine is a stimulant; it’s plainly not mind-altering in the way that psychedelics are. Adderall is mind-altering in the same way that caffeine is. Which is to say, it isn’t.
Perhaps they mean it looks better for Reddit’s smarmy user engagement metrics.
For your personal hobby project, go nuts. Break all the rules and cowboy all your own conventions.
But for business applications, the conventions Rails enforces at least make codebases somewhat familiar if you've seen a Rails codebase before.
At a certain codebase size, boilerplate is almost unavoidable. Unpleasant, but necessary. Personally, I'd rather have some conventions, rules, and guardrails for where the boilerplate lives rather than trying to navigate your homegrown pile of code. Good luck maintaining that spaghetti when you've got multiple developers.
It's not clear how this new web framework avoids boilerplate anyway, so I don't see how this is an improvement over Rails. Presumably you'll still need to set up lots of stuff yourself, like RSpec. If the framework sets all of that stuff up for you in a conventional way, then you're just back to square one as soon as you need to fight against the framework's conventions.
This type of mechanical copying is probably very important for learning and staying familiar with what it is doing.
Just last night I had ChatGPT help me with some algebra and geometry for a hobby project I'm working on. I'm rusty and got stumped so I asked the bot to unblock me. It helpfully walked through the entire simplification / substitution / solving process step-by-step, which I manually copied down using pencil and paper. Following along like that, mechanically, really helped it click for me. I plan to do more of that.
It is a very nice palette generator, but I really dislike all the talk of magic/mysticism/sorcery/witchcraft. It's a dang color generator, ease up on the dungeon master language.
Code reviews for 1000 lines of code: LGTM
Omnibus bill packages get the same LGTM treatment where legislators don’t even read the whole thing.
I think there might be a few typos of the file format?
- 14 instances of "HEIC"
- 3 instances of "HIEC"
- A Formula 1 wheel when all you need is a bicycle wheel, but the person in charge of choosing wheels chooses it on the basis of “if we want to be as good as Formula 1, then we need to use the same wheels as Formula 1”
Engineering is all about compromises. If near-term velocity is more important to you than long-term evolution and maintainability, then go ahead and use all of the dependencies if it allows you to ship faster. But that is a form of technical debt that you will have to pay down eventually.