You have to explicitly check if the return value is an error and propagate it. You write the same boilerplate if (err) return err over and over again, which just litters your code.

That’s only true in crappy languages that have no concept of async workflows, monads, effects systems, etc.

Sad to see that an intentionally weak/limited language like Go is now the counterargument for good modeling of errors.

He really doesn’t understand that tariffs are not paid by the exporting country.

Yes, it is a huge pain, especially if you want to have round-trip interoperability with humans using markup. Wikipedia had a major challenge with this when they decided to add a rich text editor alongside wiki markup.

If you also do this for the container you drain old oil into, you will be able to see if your car is starting to shown signs of oil consumption issues.

E.g. if you know you fill with 3.7qt, and you drain less than 3.7qt, you know you need to start checking the oil level every few fillups.

This kind of neglect of proper maintenance is why it started burning oil at 100k.

If you want your engine to last, you change the oil every 5000 to 7500 miles.

Surge suppressors do not drop extra voltage to ground. They selectively short out surges between whatever two conductors have a high potential between them.

No ground conductor means there cannot be a high potential between it and anything else!

Calling people “resources” and the mindset that delivery teams are just a number that you can spend money to increase is a mark of poor project and personnel management, as well.

Why should no one be touching it? You’re basically forcing manually communicated sync/check points on a system that was designed to ameliorate those bottlenecks

If “we work in a way that only one person can commit to a feature”, you may be missing the point of collaborative distributed development.

Never use rebase for any branch that has left your machine (been pushed) and which another entity may have a local copy of (especially if that entity may have committed edits to it).

Not just calls to self - any time a function’s last operation is to call another function and return its result (a tail call), tail call elimination can convert it to a goto/jump.

Data access is just one issue. Executing CCP propaganda policy (shadowbanning topics critical of the CCP and amplifying topics that divide/destabilize western democracies) is at least as worrisome.

TikTok is actively censoring any criticism of the CCP - a much larger global actor who is currently erasing the Uighur and Tibetan cultures.

Probably did it to stop Republican senators from trolling for anonymous sex a la https://en.m.wikipedia.org/wiki/Larry_Craig_scandal

If your company is using story points to “measure” developers, they are completely misusing that concept, and it probably results in a low-teamwork environment (as you describe).

The purpose of story points is so a team can say “we’re not taking more than X work for the next two weeks. Make sure it’s the important stuff.” It is a way to communicate a limit to force prioritization by the product owner.

And, in fact, data shows that point estimation so poorly converges on reality that teams may as well assign everything a “1”. The key technique is to try to make stories the same size, and to reduce variability by having the team swarm/mob to unblock stuck work.

Who creates these tasks? They need to close the year old items, reevaluate the work and break it down into sub-5-day chunks. If there are so many unknowns that it’s impossible to do that, the team needs to brainstorm how to resolve them.

I got permanently banned for reporting spam (“abusing the report button”) after I reported 8 Vice articles posted in /r/politics by the Vice self-promotion account in one day.

Meanwhile, the spam guidelines page says - if you create an account primarily to promote your own content, you may be a spammer. And as a redditor, you should report spam.

They lost a 12 year long user who primarily engaged in niche technical subjects who went out of their way to answer newcomers’ questions.

Have you tried Scala.js ?

FYI, banks do run exactly this type of analysis inside their own system to get around not being able to share your account activity.

Yes, the center (neutral) is connected to ground somewhere, but is not a suitable ground reference - because current on the neutral creates a voltage drop along the neutral conductor. A North American outlet box has Hot (L1), maybe another Hot (L2), Neutral, and also an earth/ground conductor.

Neutral is not ever treated as ground; it’s impermissible to connect it to any bare metallic surface. Other than not being switched, and being the side that ends up on the threads of a light socket, it’s handled the same way as a hot/line conductor. Just like a 240V system.

It would dissipate static fine, if you were allowed to touch it.

I think that’s incorrect. The ground pin is a dedicated equipotential reference bonded to the earth via an acyclic wiring path which carries no current. It does go pretty directly to the ground rod via the breaker panel ground bus. Neutral happens to be connected to it at the entrance panel for fault clearing, but not really for any other reason.

Since all metallic chassis, pipes, ducts, etc are connected to it and it is available pretty much throughout a building, it is a logical place to connect ESD-prevention gear, even if the earth has little to do with that. (But, a grounding electrode system installed to code should have less than 25 ohm impedance to ideal earth - not exactly a “poor” conductor)