It looks exactly like c++ and c# and java and probably others.

Which language are we talking here? Cpp? Because typeof hasn’t ever seemed useful to me in how I use cpp or how I have ever really used a language. I also remember it being criticized in java class more than 20 years ago when OOP was solely preached, even for scientific people like me.

My hairline has started receding very rapidly. There’s there’s these fine hairs all over my desk, and I see the photo I took when joining directly before turning on my camera every meeting.

Again, who is saying that? I don’t find janitorial duty shameful neither do I find sanitation engineer shameful. That’s you

I guess you’d also rather be called butcher or barber than surgeon?

After all, rebranding implies you’re ashamed.

Tell me about it…

I left my more mature company for a startup.

I feel like Tyler Durden sometimes.

A more standard definition in my tenure in academia is that scientists solve problems because they want to know the answer. Engineers solve problems because they want the problem to be solved.

In any case, the difference is just, heh, academic.

I’m very much the latter.

Who is saying that?

There’s too much virtue signaling here. No engineer thinks poorly of the trades. That’s the point of the conversation.

I just made a joke about how burger flippers can be called engineers, and I have a PhD.

Agreed.

I might also argue that those people are all still engineers.

Engineer just means “problem solver”. Everyone gets paid for solving problems.

The real question in my head is how far does this go?

Sometimes the problem is that these burgers need flipping. Protein disk translocation engineers? I’m cool with that.

I always thought about going to be a farmer. Then I watched some videos from farmers and realized they are also engineers.

A large faction of engineers, especially software-type engineers, have these types of hobbies.

I’m sitting here right beside the heirloom quality (compared to most furniture) coffee table I made in my garage with my nearly complete wood shop.

I make stuff in two ways in my day job. I design something and someone else makes it, or it’s just some idea as software.

Engineers are a type. We’re just wired differently from most other people.

A fresh ham? In a crock pot or smoker?

This post got me craving soup, so I made another post on cooking. Care to continue the discussion there?

There’s something wrong with the way your soup was prepared.

Diced carrots, onion, celery. Saute in butter until ready. Add rinsed split peas, a few bay leaves, salt and pepper. Ham and a ham bone really make this, but make sure there’s not too much ham. That means too much salt. Put those in and cover with (ideally home made, no salt) stock. Cook until done. Remove bone, return meat and cartilage to soup.

So much fiber, so tasty. Everyone is entitled to their own opinions (I really, really despise green beans), but some opinions are less good than others.

There’s nothing that can possibly be bad in that.

Pasta fagioli for me.

The texture of pasta and beans together is just all wrong.

Anyway, if you make homemade stock, that stock plus anything is delicious soup.

Have you ever had split pea soup?

You will be the most regular you’ve ever been the next morning. Like toothpaste.

Plus so tasty.

War dialing. Social engineering. Absolutely.

Also, hackers (except for the screen projecting on the characters faces).

It’s in that place I put that thing that time.

Bless the maker and his water.

good question.

Because even trivial things like Fourier transforms (to people like me) are very difficult to understand to those that don’t know them. They took me years to understand. Non scientific software engineers do not understand those. It’s just a different course of education.

You’re also right about old code base as well. Algorithms like these belong in c++ (or C or fortran), and it’s extremely difficult to explain why to people who have no understanding of numerical computing.

It’s just different education.

I’ve been working at my current company for almost a year.

I had no idea it could be this bad.

I actually had to fight/plead with someone to “please read the code”. Guy did get fired though.

Good on you for acknowledging that. 👍

I’ve fixed 20 year old issues that could kill people.

Different requirements. Different solutions.

That’s why it’s great to be an engineer!

Bruh. I fixed software from the 90’s.

Scientific software too. Which is way weirder.

😀