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.
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!
Can you link or provide reference to the official US narrative?
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.
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.
Have you tried Scala.js ?
fyi the NeXT OS is called NeXTSTEP.
along these lines, you should also know about the condensate drain from your air conditioner – since water drips out of it all summer, it has a tendency to grow some algae or mold, and if it plugs up your air conditioner may flood and ruin your ceiling/walls/floor.
it’s worth paying that AC guy to come by every couple of years even if you’re not on their service plan.
for what it’s worth, coolant is not consumed by an air conditioner – the same initial charge can last 20+ years. Low coolant either means a leak, which the technician should have investigated and fixed or ruled out, or improper initial installation.
For most organizations, the cost of paying programmers far exceeds the cost of CPU time; benchmarks really should include how long the solution took to envision/implement and how many follow up commits were required to tune it.
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.