![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/eb9cfeb5-4eb5-4b1b-a75c-8d9e04c3f856.png)
yeah, communities should have subject tag sets. I don’t care for anime or sports or video games - i should be able to turn off those tags. Not block 50 different game communities ad hoc
yeah, communities should have subject tag sets. I don’t care for anime or sports or video games - i should be able to turn off those tags. Not block 50 different game communities ad hoc
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!
Sadly my parents’ new IP phone service uses the dialtone as some kind of branding trick - you go off-hook and get this “designed” audio prompt that slides into a normal dialtone, presumably to make you remember you’re not just using “the phone”. It was very disconcerting when I first heard it.
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, banks do run exactly this type of analysis inside their own system to get around not being able to share your account activity.
honestly, I don’t want established Reddit supermods land grabbing topics in the Fediverse. The right people will find it organically based on their own motivation (as simple as searching for “reddit alternatives”).
Especially don’t want the shallow, low-quality content from default/“top” subreddits.
Is there a reason you post identical posts to multiple instances?
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.
“prove it wrong”? “as we’re told”? Do you start conversations this way?
Bro, if you don’t like it you don’t have to use it.
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.
you have to go all the way down below the dirt to prep a site for residential units. With a toilet, shower, and sink per unit, the density of sewer and water plumbing is much higher than commercial. Fire codes also demand egress points (a.k.a. windows) for every bedroom - hard to do Inside a big box retail space.