HN user

ah88

34 karma
Posts0
Comments24
View on HN
No posts found.

Midwest. Was hiring entry-level consultants from a reputable company for about $100/hr. Never saw rates for the lower-tier shops but I’d guess it’s about $70-80/hr for low quality engineer. This is how much we were paying companies, heard their engineers cut was about 25-50% of that.

When a director pulled two engineers together, gave them the problem and told them they had until the end of the year to make it happen. Ended up hiring an external consultant to help get stuff done. Delivered 3 months early. Team was very small, 2 engineers dedicated 100%, one dedicated 50%, an intern, part-time product manager and part-time tester who knew the domain well. Most fun team I've ever been on. Interesting what happens when you give people a problem and get out of their way.

Being a new parent, I realized this is one thing I have failed at in my 20s with my parents. Should have definitely called them more often, even if it's just for a few minutes here and there.

It's common practice to change procedures instead of certification.

I flew an airplane that was getting ready to be retired after it's been in service for ~30 years and we had a lot of emergency procedures and memory items (items that pilots have to memorize) that were add over the years after various incidents.

The 737 MAX wasn't necessarily an unsafe airplane, it's pilots were not made aware of how everything worked, which led to the two crashes.

Somewhat surprised at the number of negative experiences. I've had them for ~3 weeks and can't believe I didn't buy them sooner. I did go from a wired headset to these for work and they're a game changer. Battery life is excellent. Noise cancelling is great. Yes, it seems to pair to the closest device but pairing is a couple of clicks away.

That sounds not great. Two years into your career you need a better experience and great mentors. Get any job that is writing code. What's great is that you're only two years in, I see people like this 10 years into their career. They get laid off and can't find a job because they don't have any skills others value;

I like their interview process (minus the leetcode grind that’s been happening lately). They focus on fundamentals and core CS knowledge. Other company interviews, like mine, focus on knowledge or current trends, which change over time.

Mostly pair programming for about 7 years now. It's not a silver bullet and don't overdo it but it definitely has advantages. I like it but don't love it.

People dislike it when they pair on a story that's trivial or both parties know exactly what needs to be done. I've also found that people haven't taken the time to look at different strategies of pairing.