Just going to throw out an anecdote that I don’t use it for the same reason.
It’s closed unless I get a DM on my phone and then I suffer the 2-3 minute startup/failed update process and quit it again. Not a fan of leaving their broken, resource hogging app running at all times.
Denmark has a smaller population than Massachusetts, how is that a valid comparison to a massive country like the US?
Again using Massachusetts as an example, a place with a similar population to Denmark, if you instead look at fatalities per billion vkm, you would actually find MA to be about twice as safe (~1.74 vs 2.8).
The data is inherently misleading because drivers in countries in Europe don’t drive nearly as much, they travel at much lower speeds, plus cars are simply unattainable to the average person as a result of socioeconomic factors.
FSD on the other hand works fine without sleight of hand techniques, since I’ve taken it up to rural Maine without any cellular connectivity and it worked great, even in irregular rural traffic situations.
At the last company I worked at (Large popular tech company) it took an act of the CTO to get engineers to simply attach a JIRA Ticket to the PR they were working on so we could track it for tax purposes.
The Devs went in kicking and screaming. As an SRE it seemed like for SDEs, writing a description of the change, explaining the problem the code is solving, testing methodology, etc is harder than actually coding. Ironically AI is proving that this theory was right all along.
It could be a death-by-a-thousand-cuts situation and we don't have enough context. My company has spent the last few years really going 1000% on the capitalization of software expenses, and now we have to include a whole slew of unrelated attributes in every last Jira ticket. Then the "engineering team" (there is only one of these, somehow, in a 5K employee company) decrees all sorts of requirements about how we test our software and document it, again using custom Jira attributes to enforce. Developers get a little pissy about being messed with by MBAs and non-engineer "engineers" trying to tell them how to do their job. (as an aside, for anybody who is on the giving end of such requirements, I have to tell you that people working the tickets will happily lie on all of that stuff just to get past it as quickly as possible, so I hope you're not relying on it for accuracy)
But putting the ticket number in the commit ... that's basically automatic, I don't know why it should be that big a concern. The branch itself gets created with the ticket number and everything follows from that, there's no extra effort.
> The branch itself gets created with the ticket number and everything follows from that, there's no extra effort.
Only problem there is the potential for a deeply-ingrained assumption that the Jira key being in the branch name is sufficient for the traceability between the Jira issue and commits to always exist. I've had to remind many people I work with that branch names are not forever, but commit messages are.
Hasn't quite succeeded in getting everyone to throw a Jira ID in somewhere in the changeset, but I try...
> But putting the ticket number in the commit ... that's basically automatic, I don't know why it should be that big a concern. The branch itself gets created with the ticket number and everything follows from that, there's no extra effort.
That poster said "attach a JIRA Ticket to the PR", so in their case, it's not that automatic.
A lot of Jira shops use the rest of the stack, so it becomes automatic. The branch is named automatically when created from a link on the Jira task. Every time you push it gives you a URL for opening the PR if you want, and everything ends up pre-filled. All of the Atlassian tools recognize the format of a task ID and hyperlink automatically.
I haven't dealt with non-Atlassian tools in a while but I assume this is pretty much bog standard for any enterprise setup.
Invite engineers to solve it in a way that makes it cheap for them.
Most shops I've been at prefix their branch names with ticket numbers ("bug-X-" or "TCKT-Y-"), and then it's trivial to reference it back. Some will write scripts on top, which gets them even more motivated to solve your problem (and might add links into the tracking tools too, move the ticket to "In Review" when the PR is up, close it after it's merged...).
Strange, I thought this is actually the norm. Our PRs are almost always tagged with a corresponding Jira ticket. I think this is more helpful to developers than to other roles, because it allows them to have history of what has been fixed.
One can also point QA or consultants to a ticket for documentation purposes or timeline details.
I think the parent has a valid point. What's the big deal with simply stating the facts?
When I think about dirty industry I don't think of CO2, I think of Sulfur Dioxide, Nitrogen Oxide, etc. For example a Natural Gas plant that emits CO2 is not even remotely "dirty" the way that a Coal plant is. When you trivialize the issue you're training people to stop caring about pollution that actually causes acute and immediate health consequences to the people around it.
> For example a Natural Gas plant that emits CO2 is not even remotely "dirty" the way that a Coal plant is.
Wait, are you saying that because there is more than one way to be dirty (I agree, there is), then something that is (far) less dirty by being dirty in fewer of those ways can't possibly be called dirty at all? I really struggle with this logic.
At this rate by 2135 Europe will have returned to feudal society, most people will be living without electricity, and the primary source of heating will be wood and coal.
Why do I have a feeling this is one of those "green" ideas that has some horrible environmental consequence. One that could have been solved with a way simpler technology for far less money in exchange for a bit of efficiency loss.
It's so ridiculously easy to vacuum and charge a heat pump it's kind of unnecessary.
I think I spent $200 in parts on Amazon and have done 4 heat pumps now. It's a vacuum pump, a scale, and a digital manifold/guage. Punch the numbers for subcool/superheat into a calculator and use the temp probes on the lines where they connect to the condenser and you can even skip the scale.
Isn't the problem having access to the gas in the end ?
They are tightly regulated, and this is why installers can charge a lot of money, I believe.
How did you manage to locate a source?
For a typical new install, the outdoor unit contains the charge and unless your lineset is unusually long, you just use that, releasing it with the valves after installing and leak-checking the lines.
In the US, you can get your EPA 508 cert online in a couple hours and buy the refrigerant online. (You need the cert to be legal, but it’s not really checked just to buy.) Tightly regulated is not true in practice. You could buy some in 3 minutes online and have it Monday.
Yes, in the US I think it's fine; you have a lot more freedom.
In France, access to the gas technically requires a certification that is not available to regular people. You need to be professional and bow to the bureaucracy.
I know somebody who was required to pay the full installation price for a heat pump he installed himself because there was no professional that was willing to charge and launch the installation for the small fee it should require.
This is the hypocrisy and value-destroying behavior of EU collectivist governments. They tout ecological solutions, but you need to pay far more than is reasonable for those modern solutions. Predictably, people chose things that are worse but cheaper, like wood-burning stoves or pellet stoves.
Those things are made artificially expensive for no good reason, and that's because they get built overseas mostly, and this happened because of regulations in the first place.
Then they wonder why the EU is losing ground economically…
For your friend’s new install, the refrigerant was in the outdoor unit when shipped from the factory. Accessing that gas just takes an ordinary hex key/Allen wrench. Only if they’d made a mistake and let the refrigerant leak out (or had a ridiculously uncommon length of lineset) would they need access to additional refrigerant.
Yeah, I know they come pre-charged now. But I can't remember what his problem was back then. Maybe he didn't know, or he fucked up…
From what I understand, self-install should be fine up to a 12m run, but if you let too much gas leak, you may have issues because of low pressure.
At least now you can buy them for relatively cheap. Mine required a swap of the control board on the inside unit, and it was ridiculously expensive (almost as much as buying a new unit).
I am not sure why it fried, but probably bad solder from old age (it's about 15 years old at this point).
It's an excellent technology, but the surrounding business feels extremely shady.
Why then, outside of Norway, Luxembourg, Switzerland, and the UAE (All of which are tiny countries, and at least two of them are Petrostates), does the United States have the world's highest median income with a population of over 342 million people?
The typical American is insanely wealthy by global standards.
Insanely wealthy when your comparison includes tin pot dictatorships, theocracies, and ex-soviet countries that still haven't gotten their shit together. Weird how that unimaginable wealth doesn't translate into financial security, access to high quality healthcare, or the ability to own a home.
Who cares? If higher wealth inequality produces a higher standard of living for the majority (note, median not mean), I’m all for it. Policy should not be driven by envy.
You should care because people vote and the social consequences are going to be devastating.
It is easy for me to take this perspective too because I never had much student debt or children.
The median though is getting crushed if they went to college and are paying for daycare.
If you are getting crushed for going to school and having children that is a pretty clear breakdown of the social contract.
The consequences are obvious. People are going to vote in socialist policies and the whole engine is going to get thrown in reverse.
The "let them eat cake" strategy is never the smart strategy.
It is not obvious at all our system is even compatible with the internet. If the starting conditions are 1999, it would seem like the system is imploding. It is easy to pretend like everything is working out economically when we borrowed 30 trillion dollars during that time from the future.
> The median though is getting crushed if they went to college and are paying for daycare.
> If you are getting crushed for going to school and having children that is a pretty clear breakdown of the social contract.
That isn't a factor in wealth inequality. Inequality is how much money they have relative to people like Musk and Bezos - or just local business owners. The poor side of that comparison always has such little wealth/income that their circumstances don't really matter. Someone poor will be sitting in the +-$100k band and not be particularly creditworthy. When compared to a millionaire the gap is still going to be about a million dollars whether they're on the crushed or non-crushed side of the band.
Part of the reason the economic situation gets so bad is because people keep trying to shift the conversation to inequality instead of talking about what actually matters - living standards and opportunities. And convincing people to value accumulating capital, we're been playing this game for centuries, inter-generational savings could have had a real impact if people focused on being effective about it.
The 1870-1900 period experienced the greatest expansion of U.S. industry, and the fastest rise in both U.S. wages and U.S. life expectancy, in history.
Right we had a functioning labor movement to thank for productivity gains being distributed to the working class. When that got undermined beginning late seventies early 80s with offshoring we see wealth just flowing to the top without significantly benefiting the working class.
It’s closed unless I get a DM on my phone and then I suffer the 2-3 minute startup/failed update process and quit it again. Not a fan of leaving their broken, resource hogging app running at all times.
reply