namingthingsiseasy

joined 2 years ago
[–] namingthingsiseasy@programming.dev 4 points 2 weeks ago (1 children)

Your post is a succinct summary of the "study" of economics. It's just supporting a conclusion in exchange for taking a bunch of bribes and cherry-picking data to support your argument.

I remember being taught how to use maps in elementary school. Now I can’t help but wonder if that’s taught at all these days.

For what it's worth, I was never taught how to use a paper map but always found it easy to do.

But I definitely agree about over-reliance on GPS is pretty sad. I love the fact that I can just try a different route and see where it takes me. Sure, I sometimes waste 20 minutes doing the opposite direction of what I want, but I also discover new things along the way which is really nice.

I know what you mean, just beware: in lots of cases it’s not as universal (as in distro-independent) as some still think it is.

This is especially true when we start talking about BSDs and other non-GNU platforms.

Interesting. Were you using a Jenkinsfile? I'm not sure I completely understand your use case, but using a Jenkinsfile would mean that your entire pipeline would be defined in a file in source control, so you could roll it back if you made a change that didn't work quite right. Seems to be what your looking for if I'm understanding what you're looking for.

https://www.jenkins.io/doc/book/pipeline/jenkinsfile/

I looked at it for 5 seconds. The UI looked pretty hideous. Even new reddit looks better than it.

[–] namingthingsiseasy@programming.dev 2 points 3 weeks ago (2 children)

I've found the edit/test/debug loop in Jenkins to be much faster than Github Actions. It was quite a refreshing change when I made that transition.

The best way I found to do this is by commenting out the portions of the build that take the longest.

Which is stupid, but that's what you get with Microsoft products.

(I get that there may be ways to test this locally, but I found this method to be the easiest.)

I thought they renamed their entire product line to "Copilot" by now, didn't they?

Uninstalling it at this point would leave absolutely nothing left!

[–] namingthingsiseasy@programming.dev 6 points 3 weeks ago (1 children)

It's called tivoization and started with a device called "Tivo" which was the first of its kind to attempt this procedure.

There are probably lots of hardware devices in your house that use GPL software but prevent you from actually modifying it because the hardware will refuse to run modified copies. If a piece of software is licensed GPLv3, it would violate the license terms to do something like this.

[–] namingthingsiseasy@programming.dev 10 points 1 month ago (5 children)

This has to be the most pathetic thing I've ever read. A CEO just asking people to stop saying mean things about the garbage he's pushing out.

It's just so pathetic. I'd be embarrassed if I were affiliated with his company in any way.

That's certainly one possibility. But another possibility is that the people praise LLMs are not very good at judging whether the code it generates is of good quality or not....

Agreed. To make it a bit more general, whenever I see people claiming to be able to predict the future with absolute certainty and confidence, that to me is just a sign they are idiots and shouldn't be listened to. Definitely had a lot of those in past companies I have worked in. A lot of the time, they're trying to gaslight people into believing in their version of the future so they can sell us garbage (products, stock price, etc.). They'll always get some fools to believe them of course.

 

I've used a US-QWERTY keyboard layout my entire life. I've seen other layouts that do things like reduce the size of the enter/backspace keys, move the pipe operator (|) and can't wrap my head around how I would code on those.

What are your experiences? Are there any layouts that you prefer for coding over US English? Are there any symbols that you have a hard time reaching ($ for example)?

view more: ‹ prev next ›