It ws only like a decided ago when I had multiple amazing ideas for games and other software, only to have nearly none when I actually started to do some programming for fun.
I think there’s only one game I would like to try making where I see it may have some success, but the idea is very vague and devil is in the details and execution I guess.
There’s a cool computer game that makes this point as part of the story line… I’d recommend it, but I can’t recommend it in this context without it being a spoiler!
Kil’n People by David Brin - it’s a futuristic Murder Mystery Novel about a society where people copy their consciousnesses to temporary clay clones to do mundane tasks for them. Got some really interesting discussions about what constitutes personhood!
Also multiple systems included. the old base plotting from the 90s, lattice for really custom things, ggplot as the most humanely understandable and reasonable system for composing plots and great interfaces to plotly and d3.js
I don’t get it. Where does he say “algorithm”? Does Google Gemini do PAC learning?
AFAIK “AI” means “machine learning” and machines with “intelligent” behaviour, whatever that means. It includes everything from expert systems, statistics, markov chains to LLMs. And people nowadays slap it on every product out there.
“Algorithm” means a (finite) sequence of (rigorous) instructions. At least that’s what Wikipedia says. It’s well defined and doesn’t talk about where the instructions come from or if it includes statistics.
Agree. Not sure if I’d use the word “tool” to describe him… But he’s certainly “special”. Glad I found one of the few discussions where it’s not just his fans praising him for his " visions" despite him not delivering on the last 50 promises he made. Or the latest edgy memelord thing he read somewhere or came up with… Usually I just shut my mouth and don’t comment on that because it’s just so many people following the hype.
The UK press every year makes a huge song and dance in opinion pieces about getting rid of DST. However I’m always horrified to see that people want us to keep British Summer Time instead of Grenwich Mean Time. I understand that there are “longer evenings” in BST; however we literally invented GMT and coerced the rest of the world to adjust their times based on that. From the point of view of being constantly compatible with UTC and having more consistent business hours for international companies it makes more sense to me if we kept GMT.
Also the longer evenings thing can be achieved by simply staying up an hour later. It’s not exactly like an hour is being stolen from you when the times switch, the change of clocks are mainly pointless admin.
Lastly I read an article recently that described a correlation between the incidence of heart attacks and the clocks changing. The theory is that just slightly messing with people’s sleeping patterns can cause additional strain on the body.
No the longer evenings are achieved by work starting and ending an hour earlier. And it’s literally easier to change the time zone than to change corporate culture.
I think I want work to end an hour earlier in the winter because of how early the sun sets, and care much less about the summer. So however it’s done, it would be great if office jobs could happen when it’s dark outside and we could live our lives during daylight.
Mmm yeah I’ve noticed that my retired parents keep telling me what a great summer we’re having every year and I’m completely unaware of it due to being cooped up inside.
Another point for GMT, in the mid '70s, the US went onto DST year round for a couple years. People hated it so much they changed back to switching the time.
If we wanna do away with DST and BST, we need to go back to standard time, as the later sunset in the summer translates to no sunlight for workers in the winter
I use interactive rebases to clean up the history of messy branches so they can be reviewed commit by commit, with each commit representing one logical unit or type of change.
Mind you, getting those wrong is a quick way to making commits disappear into nothingness. Still useful if you’re careful. (Or you can just create a second temporary branch you can fall back onto of you need up your first once.)
If you’re using “trunk-based development” (everything is a PR branch or in main), this works great.
If you’re using GitFlow, it can make PRs between the major prod/dev/staging branches super messy. It would be nice if GitHub would let you define which merge strategies are allowed per-branch, but that’s not a thing (AFAIK). So you’re probably better off not squashing in this situation.
The way I structure my commits, it is usually (but not always) easier and more reliable for me to replay my commits one at a time on top of the main branch and see how each relatively small change needs to be adapted in isolation–running the full test suite at each step to verify that my changes were correct–than to be presented with a slew of changes all at once that result from marrying all of my changes with all of the changes made to the main branch at once. So I generally start by attempting a rebase and fall back to a merge if that ends up creating more problems than it solves.
Only before you collaborate with anyone else. After that, don’t ever use rebase, or they’ll get an error, and will have to overwrite their local history with the one you’ve rewritten.
programmer_humor
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.