I totally get that: use the right tools and you’ll be okay. This applies to many technologies in this space.
With respect, I still take this advice like hearing “look out for rattlesnakes if you’re hiking there.” It might be safer to just hike where there are no rattlesnakes, instead.
I swear, overcoming fixed functional-ness is like a superpower when you can apply it.
I once shared a small office with a co-worker. I had the idea to move the desks away from the walls and place them back-to-back, diagonally, in the middle of the room. Other co-workers scoffed and remarked at how dumb and unconventional this looked. Then I explained that we each now had nearly full privacy from each other, much more personal space in our respective corners, no more glare from the window, and nobody could sneak up on us from the door anymore. Things got pretty quiet after that.
Useful? Not exactly. But you’d never look lazy or idle, that’s for sure.
/me goes back to get second folding chair.
Pascal went to military school.
I’m not in love with the idea, but a language that cuts out the BS has a sudden appeal when on a group/team project.
I take this as less of a “I can’t use this intuitive feature reliably” thing and more of a “the truth table will bite you in the ass when you least expect it and/or make a mistake” thing.
The worst ones are safety rules: those are (sometimes) written in blood, with stories to match.
Company: Provides amenities and services that would (technically) allow a person to live on premises. Pays you enough to retire early if you didn’t have to bother with rent or a mortgage.
Also company: “We can’t hire you without a permanent residential address.”
I also worked at multiple places that had fully decked out break-rooms: free food, game consoles, VR, and 60-inch TVs. Everyone was afraid to use them for fear of looking like they were screwing around. Except the interns. They used the hell out of that stuff.
I’ve seen this kind of thing too many times to count. First it was in high school, then the workplace.
Some people just want to push the envelope. Other times, people can have a poor grasp of social norms, or they simply don’t respect others. But on the other side of the coin, people get annoyed for good and bad reasons; sometimes, no reason at all.
Bottom line: it’s a mess, so we get rules. But nobody wants to spend time writing these things and enforcing them, so there’s usually a reason/person/event why they’re there.
Yes. Not enough daydreaming about winning arguments, mixed with intrusive thoughts and general self-loathing.
a lot of devs love watching stuff like speedrunning
True, but some of them hate it. But with the growing presence of speedrunning friendly features in new titles (looking at you, Supergiant), I think that’s becoming less of a problem.
Either way, these “devs watch” reaction videos are fantastic.
Software maintenance was seen as a necessary evil.
The most important lesson I learned about the economics of software is that sourcecode is always accounted as a liability and not an asset. Accountants will never let you code your way into more value. Everything else you see stems from that truth.
A times B times C equals X. If X is more than the cost of a failure or security breach, we don’t fix the software.
Are there a lot of these kinds of problems?
You wouldn’t believe.
Which Fortune 500 company do you work for?
A major one.
Also that’s likely a team that doesn’t use a branching workflow, has poor review on merges, and/or using Git like it’s SVN.
Same.
Wow, what a bro. Where was this guy when I was in school?
::re-reads comment and thread::
Oh. Yeah, that one’s on me. That makes a little more sense.
Also AMA about soda dispensing at bars.
It’s been ages since I worked in a restaurant. IIRC, I never saw that place purge or clean the soda lines. And there was a LOT of plumbing between the fountains and the back where the syrup was kept.
At the risk of making everyone re-think ever eating out again: how often do establishments do that kind of maintenance? And is that within the recommended manufacturer interval?
Exactly. And while we’re educating the forum here, Wikipedia has the details on the loophole that circumvents this:
https://en.wikipedia.org/wiki/Gun_show_loophole#Provenance
Sometimes referred to as the Brady bill loophole,[9] the Brady law loophole,[10] the gun law loophole,[11] or the private sale loophole,[12][13][14] the term refers to a perceived gap in laws that address what types of sales and transfers of firearms require records and or background checks, such as the Brady Handgun Violence Prevention Act.[15] Private parties are not legally required by federal law to: ask for identification, complete any forms, or keep any sales records, as long as the sale is not made in interstate commerce (across state lines) and does not fall under purview of the National Firearms Act. In addition to federal legislation, firearm laws vary by state.[16]
I am not a lawyer. I do not sell firearms.
The gist I get is that this opens up enough loopholes to permit unlicensed mules/fences on either side of the transaction. Depending on what political leanings and circumstances are in play, this legal framework might actually encourage that behavior.
All you need is a red shirt, a grey hoodie, a windswept location, and some nearby transportation project. Preferrably a defunct or about-to-be-closed transportation project.
That said, there’s a Tom-shaped hole in my youtube recommendations these days.
This goes especially for EVs. Wind resistance really chews up your power budget once you’re above 55mph or so. May as well run the heater with the windows down at that point.
NPM
ruin devis a new advanced feature that endorses opinionated “extreme programming” techniques. First it gets to work rebuilding node_modules, but with all the least compatible module versions in order to accelerate testing. It also minifies your .js code in place, to save you some CPU cycles later. Lastly, it squashes your entire git history on all branches, to save space.