Not sure why the downvotes, it's largely true. Almost every non-techie I encounter in real life incorrectly uses the term "memory" to mean storage space.
Is it really that incorrect? Flash memory is persistent storage. Memory cards used to be how game saves were stored on consoles. The M in ROM stands for memory.
So it seems like we're using the term memory too narrowly, rather than them using it incorrectly.
I think it would be enough to simply move the 3 point line back a couple feet AND have it follow its natural arc out of bounds, thus eliminating the shorter and easier corner 3 shot.
I’d rather defenses covered it better to give up more 2s in the paint. If we make it too far out it no longer spaces the floor and then we’re back to a game in the paint.
This is my preferred answer. Bring back physicality into the sport, especially on defense. There are moving screens on every play, and yet a defender can stand and get jumped into resulting in free throws.
couple of feet is not enough. the line needs to move far enough such that vast majority of the players (more than 95%) shoot less than 30% from there. so probably 8 to 10 feet back. absolutely should happen but they will likely do something awesome like shortening quarters to 10 minutes
curry and bol bol are two good candidates. in today’s nba you can’t tell difference between them on the court except for several feet of height difference. but practically same player as they shoot about the same shots
Yes. I think part of the problem is how good it is at starting from a blank slate and putting together an MVP type app. As a developer, I have been thoroughly impressed by this. Then non-devs see this and must think software engineers are doomed. What they don't see is how terrible LLMs are at working with complex, mature codebases and the hallucinations and endless feedback loops that go with that.
The tech to quickly spin up MVP apps has been around for a while now. It gets you from a troubling blank slate to something with structure, something you can shape and build on.
I am of course talking about
npx create-{template name}
Or your language of choice's equivalent (or git clone template-repo).
Yes, but the LLM driven MVP-s are not only builerplates but actual functioning apps. The "create-" is somewhat good, but it's usually throwaway code and do it properly later. While my LLM made boilerplate is the actual first few steps to get the boring parts done. It also needs refactoring and polishing, but it's an order of magnitude better than the "MVP helper tooling" before.
I used to feel they just served as a great auto complete or stack overflow replacement until I switched from VSCode to Cursor. Cursor's agent mode with Sonnet is pretty remarkable in what it can generate just from prompts. It is such a better experience than any of the AI tools VSCode provides, imo. I think tools like this when paired with an experienced developer to guide it and oversee the output can result in major productivity boosts. I agree with the sentiment that it falls apart with complex tasks or understanding unique business logic, but do think it can take you far beyond boilerplate.
I've tried several times to migrate a few apps I have from Dokku to Kamal because I've been intrigued by all the hype in the Rails community about it, but I've always given up after an hour or so of unsuccessful tinkering around. Maybe it is just because it's what I'm used to, but the Dokku experience is so much better than Kamal.
Exactly. But I'd love to hear what the next step after dokku is. But maybe it's just moving the db to another, separate vps, and spinning up more instances of the service all pointing at that db instance, with all of that using dokku.
I'm of the opinion that a single VPS can take you a very long way. Once you get to the point where you've outgrown that model, you're likely making enough money where something like Digital Ocean App Platform, as another commenter suggested, would be money well spent.
One option is that Dokku can orchestrate k3s and Nomad. I don't know how well it works, but it sounds like it gives you the same simple ops interface with a clear incremental migration path to horizontal scaling.
I find myself contemplating this more and more now, especially as my interest in discovering new music has declined significantly as I enter middle age. My biggest concern would be replicating the cloud aspect of streaming music. Is there a good solution for having access to my library on all my devices as well as my sonos system?
I can listen to my DRM free music from anything with speakers by just converting my FLACs and copying files where they need to go.
The only way I can play music in my car is radio or USB storage. There is an aux port that is broken, and bluetooth only works for call audio. I play my music from a USB drive.
That's fine, but going and sourcing DRM free versions of everything I want to listen to, managing the conversions, making it available in a cloud streaming setup of some kind, all of that just sounds like more work than I really want to do
I agree this is the correct way to use it, and it is incredibly useful in that case, but I think a study like this is valuable in the face of all the hype/fud about how AI Agents can program entire complex applications with just a few prompts and/or will replace software engineers shortly.
The spotify app experience is what drove me away in the first place. Once they started cluttering the home screen with TikTok style videos and banner sized ads for podcasts I have no interest in, I left for Apple Music and have not looked back.
The spatial audio is also keeping me with Apple Music, although I will say that while most are incredible, sometimes I'll come across an album where the spatial mix is laughably terrible.
I have been golfing in a weekly league for 10+ years and was frustrated by the complex spreadsheet our league manager built to track everything. I Figured there must be an app we could replace it with... While there were plenty, most were severely outdated or simply did not do what we needed. So I created https://golfsheet.app