331–340 of 592 posts
Everyone is talking about layoffs and lack of hiring, but I've found the problem to be that companies are cutting costs by silently increasing workload on existing employees. Everyone is getting burnt out trying to keep a 300-person engineering team running on only 100 head count. That leads to more incidents, slower delivery, less innovation, longer hours. Even those who are still employed are seeing working conditi…
Earlier quoted context omitted.
To me it looks like tech is just falling more in line with other industries pay/workload. I think there are many who joined the tech workforce during the pandemic thinking the norm was to make $135k while doing 10 hours of real work a week from home, twiddling a few lines of bootcamp level javascript to appease your largely absent boss. Many may forget, or not have been there, but 10-15 years ago tech jobs were notor…
I am dumbfounded this idea gets trotted around HN so freely. I’ve met nobody like this in the industry. Most people I know are burnt out from many years of having to work over 40 hours.
Earlier quoted context omitted.
I am dumbfounded this idea gets trotted around HN so freely. I’ve met nobody like this in the industry. Most people I know are burnt out from many years of having to work over 40 hours.
Which one? A large part of the IT community does indeed very little work. As for having to work over 40 hours and being stressed, I guess there's a price to having to work in US under such lax worker's rights and benefits, in Europe you just say no thanks boss see you on Monday.
Earlier quoted context omitted.
> I'm more likely to be loyal The funny thing, is that I've been told that "Old people are just cruising to retirement," but it's OK to establish your entire business infrastructure on the idea that your young, energetic, engineers will not remain at the company for more than 18 months.
> but it's OK to establish your entire business infrastructure on the idea that your young, energetic, engineers will not remain at the company for more than 18 months. Yeah, it's a tough nut. It's understandable that SV companies want ambitious strivers that move on every 2 years, for the same reason many of these CEOs consider the "job done" as soon as they get "an exit". The life of the company is measured in mont…
It seems that many startups don’t actually have a product, other than the startup, itself.
A “successful exit” means that the company is sold. The company is the product.
I have spent my entire career at companies that made actual products, for use by actual end-users. These corporations never had any “exit strategy,” because they were meant to be ongoing, perpetual, concerns. They had “future planning,” and “growth strategies,” that often looked a decade into the future.
Things have changed.
Everyone is talking about layoffs and lack of hiring, but I've found the problem to be that companies are cutting costs by silently increasing workload on existing employees. Everyone is getting burnt out trying to keep a 300-person engineering team running on only 100 head count. That leads to more incidents, slower delivery, less innovation, longer hours. Even those who are still employed are seeing working conditi…
I think a lot of big-co are setting up subsidiaries overseas and hiring there. It's different from the contract based offshoring model that happened in 2007 or so which had rather disastrous results. I know my company has and plans to have almost 1/2 its IT workforce as direct employees overseas.
Earlier quoted context omitted.
My previous company was doing this. I basically quit out of frustration. They weren't much better than picking random people off the street and pointing them at code. It bled into my work life when they took over a project I was on and was pinging me constantly with "hello" and "good morning" expecting to jump on calls with their teams to explain exactly how to do their jobs. An example to illustrate what I was worki…
My company's doing apprenticeships; take somebody with no CS education, not even a college degree, and teach them to code. It's an interesting model, I remember folks on HN calling for more companies to try it since it seems to have had some success in Germany, but I predict a lot more security bugs and unmaintainable code in the near future.
This sounds like the kind of situation he'd excel with - is your company currently hiring U.S. based folks?
Earlier quoted context omitted.
I think a lot of big-co are setting up subsidiaries overseas and hiring there. It's different from the contract based offshoring model that happened in 2007 or so which had rather disastrous results. I know my company has and plans to have almost 1/2 its IT workforce as direct employees overseas.
My previous company was doing this. I basically quit out of frustration. They weren't much better than picking random people off the street and pointing them at code. It bled into my work life when they took over a project I was on and was pinging me constantly with "hello" and "good morning" expecting to jump on calls with their teams to explain exactly how to do their jobs. An example to illustrate what I was worki…
Everyone is talking about layoffs and lack of hiring, but I've found the problem to be that companies are cutting costs by silently increasing workload on existing employees. Everyone is getting burnt out trying to keep a 300-person engineering team running on only 100 head count. That leads to more incidents, slower delivery, less innovation, longer hours. Even those who are still employed are seeing working conditi…
I think a lot of big-co are setting up subsidiaries overseas and hiring there. It's different from the contract based offshoring model that happened in 2007 or so which had rather disastrous results. I know my company has and plans to have almost 1/2 its IT workforce as direct employees overseas.
A lot of hiring here is for low end work or at very junior levels (If you are a 10+ years experienced guy, good luck getting a job. I know a close friend of mine struggling to get one - ready for even a 40pc pay cut)
If you apply for a Principal or Staff position (few), be ready to grind out 1 easy, 1 medium and 1 hard Leetcode problem and doing a System design interview where you do FB with Instagram design reels all at once in 1 hour). Surprisingly when you attend meetups and talk with "Senior" managers who used to hire dozens with shambolic interviews, seem to be opting for getting "good" "resources" with DSA skills from this market (Imagine working in core engineering and then going on to do body shop consulting at an IT provider migrating from Java 4 to Java 17)
While the general sense on lot of jobs are going offshore is true, it is possibly very low paying entry level jobs.
You can now possibly correlate these to a lot of comments you see, junior folks who (no offense intended) :
* Given a spec hack something up and never think of how a customer will use this * Exceptions (sorry, we code Hail Mary scenarios) * Monitoring (sorry, that is ProdOps issue not mine) * Alert Management (this is non critical anyway & maintenance is someone else's job) * Testing (shambles)
Add to this targets such as "automate" with "Gen AI", We paid your co-pilot license where is the productivity increase number (you are an under performer and did not "customer delight" experience)
Sure is frustrating (onshore or offshore) & sad to see this where this is. One just thinks we'd have to live with this at-least for now. Hoping that things get better (overall in the world), sanity prevails and we can all have better lives ahead of us
Earlier quoted context omitted.
I am dumbfounded this idea gets trotted around HN so freely. I’ve met nobody like this in the industry. Most people I know are burnt out from many years of having to work over 40 hours.
Which one? A large part of the IT community does indeed very little work. As for having to work over 40 hours and being stressed, I guess there's a price to having to work in US under such lax worker's rights and benefits, in Europe you just say no thanks boss see you on Monday.
1) People who can leave will leave if the work load is too high. Those who can leave are usually the best team members.
2) It does not work. Research has shown most people are incapable of producing more than 40 hours of work a week over the long term. They can do it for a week, maybe a month but after that their productivity is either the same as a 40 hour/week work or maybe even less. People are not machines and just because they are asked to do something (or ordered to) does not mean they will or even can.
One last thing, what keeps employers inline in the US is people can leave. If you are in a bad job, you can switch to a good one.