sarchertech

If you have little experience writing code, do you know that you actually understand what you’re reading though?

For example could you reproduce the code you read immediately after writing it?

It’s very easy to “read code” if you’re just reading for surface level understanding.

Have you tried in both directions though? You need to test both sensitivity and specificity.

> I'm already paying 10-times more for water usage than I spend on gas

Are you irrigating an enormous yard?

Well historically the consensus was that it was harder to read code than to write it, but that leads to uncomfortable conclusions these days, so that bit of common wisdom has mostly been ejected.

> I'm not a coder so I have zero idea. Thoughts?

I’m not trying to be mean, but this comment is basically “I have no experience with this topic, but it can just be boiled down to this one simple question right?”

The only time I really heard the term load bearing in a software engineering context (pre LLM) was in the phrase “load-bearing bug”.

There’s still browser/OS typo mitigation.

You can’t always tell the difference, but you can filter out businesses that lasted less than a year, temporary businesses that were setup for real estate transactions, and business that never made a profit.

Unless you get caught up in a big layoff where the people you have relationships with have zero input.

I’m also confused.

The difference was 3.6cm in the study that measured 10 more years 30-80. And 5cm in the study that measured 10 fewer years 40-80.

The studies were conducted over different time periods when average nutrition changed, and demographics changed. And the study demographics just vary by location.

Height loss with age is incredibly well documented. Here’s a few more studies.

This is just basic medical textbook information. No one in the world is arguing that this phenomenon doesn’t exist.

https://pubmed.ncbi.nlm.nih.gov/32611342/

https://pubmed.ncbi.nlm.nih.gov/24962157/

https://pubmed.ncbi.nlm.nih.gov/10602346/

https://www.sciencedirect.com/science/article/pii/S266703212...

No that’s not what I was getting at. The post was edited and originally mentioned absolute amount of fat being bad for your heart.

I mean median household income in 1999 was $40k and median household income now is $84k.

Still doesn’t make sense if you believe that AI is making a meaningful boost to productivity.

If you are the kind of person who thinks AI will drive down the wages of software engineers that much, you have to think that it is at least a 2x multiplier.

$65k salary all in for a company is easily $100k. So spending anything less than $100k would be what you would aim for.

I’m well aware of the history of the fed.

Most small businesses fail because they were never serious businesses to begin with. A business closing down after running for a year with no profit isn’t relevant.

That’s not the question I ask though. I asked about the specific claim that absolute fat was bad for your heart.

But also short people living longer has so many more possible explanations than less overall fat.

Short people have fewer incidences of cancer, so I don’t think you can say that lower overall risk of death implies lower risk of heart disease.

As for 2, men in the US are getting shorter because of immigration which adds many confounders.

Do short people have much lower risk of heart disease?

> Instead, I was responding to a very specific observation the gp made: he saw that both senior and junior devs were interchangeable when randomly assigning the next JIRA ticket. That can only happen in a situation where the JIRA tickets are similar enough in complexity that the difference in skills between your senior and junior devs are irrelevant when the work is assigned.

That’s not what I was saying.

I was saying that the perception of management is that the tickets are interchangeable. Not that the tickets are actually interchangeable.

Notice what I said after that. That this usually results in seniors coming in at the end to rescue the project.

All of those things are true. There are downsides to any of the levels they can adjust. I’d there weren’t, they’d already be doing it.

But it’s wrong to model businesses as if they have no ability to increase profit per customer and predict catastrophe from minor reductions in customer traffic.

They can and do figure out how to do more with less.

That’s not what I was saying. I’m saying that we have small downturns where consumer spending drops yet those drops don’t result in crisis levels of small businesses closing. Which it would if most of them were structured like that.

Sure that’s one of the argument for why they do it but the money doesn’t directly to most small businesses, we do have small downturns, and they don’t result in the majority of small businesses going out of business.

That assumes he has a fixed profit per person.

In reality most business can do things like cut hours for staff, postpone upgrades or long term maintenance, cut amenities, raise prices etc…

If most businesses were structured in a way that a small decline in customers immediately puts them out of business, any minor economic downturn would be an unrecoverable positive feedback loop for the economy.

I’m not saying a 10% drop won’t put a lot people out of business, but it’s not as much of an existential crisis for the economy as a whole as that story makes it seem.

>This has traditionally been offloaded by having seniors do the hard thinking then distill it into a jira ticket which could be handed off to an engineer that'd actually write the code and punch every hiccup into google along the way.

This is the theory, but I’ve never worked anywhere (and I’ve worked at a lot of places over 20 years) that actually did it like that in practice.

What tends to happen is that the EMs and PMs look at who’s free and give that person the task. This means that sometimes you get a senior leading a simple project and sometimes you get a junior leading/designing a complex project (usually with help from a very minorly technical PM).

Then the senior/staff/principal (often on a different “special” team) gets pulled in at the last minute to rescue the project.

If your company is highly product driven, you’ll often find that the juniors end up leaving projects more often than not because they will tell the PM exactly what they want to hear.

I’ve worked at many startups and consulted at many more over the last 20 years. I’ve never seen 2 million lines of code happen that fast at a small startup.

15 devs putting out 400k LOC a year into the same codebase is not normal at all. I’ve never seen anything close to that kind of rate of growth across that number of people.

And 50 engineers is not even remotely close to a small startup. I have worked at a startup that had 50 engineers after a few years, but it was a multi billion dollar unicorn.

Definitely possible, but up thread they wrote:

>”Have you worked at many startups?”

In response to a question about a legacy codebase at a startup. That implies that they think whatever they are doing is common. And forking a multi million line codebase and heavily developing it isn’t common for startups.

How long has your startup been around? I’ve worked at plenty of startups over the past 20 years. Including one that was still calling themselves a startup 10 years out. The org I work at now was a startup before my tech giant employer acquired them. We have a very bloated and very profitable 8 year old codebase that is barely 500k LOC.

I’ve never seen a startup with a multi million line legacy codebase.

To continue the analogy, it’s like writing answers that are so convoluted that no one can understand them.

> 1 day turnaround build permits, to any proposed off-the-grid data centers.

Utility planning is one tiny part of approving a building permit. You still need to look at storm water runoff, fire safety, environmental impact etc…

I’m also not even sure what bring your own water even looks like.

And even if they are providing their own wastewater treatment, that requires an even closer look than hooking up to municipal sewage. It also requires at least occasional long term inspection because these kinds of systems fail at insanely high rates.

That wasn’t the US supporting liberal democracies. A full 20% of Lend-Lease went to the Soviet Union, and the US provided plenty of support to Nationalist (and very authoritarian) China.

We had friendly relations and supported many counties that weren’t liberal democracies before the war. We were friendly with Japan before they started expanding and threatening free trade/access to Asia.

> That's why we entered WWII

The US entered World War II in the pacific after Pearl Harbor and in Europe after Germany declared war.

Before those 2 events, there was still a strong isolationist contingent in the US.