131–140 of 301 posts
Earlier quoted context omitted.
Projects managers are absolutely getting slaughtered right now
How so?
Earlier quoted context omitted.
Which in today’s days of remote work, management may actually like. You may have hit on a carrot.
Mentally making the move from writing code to management needs to be a shift in mentality from "I'm making software systems that solve problems" to "I'm building teams that solve problems". Team building is people skills, and it's about finding well springs of motivation, soft skills, getting people talking to each other, making sure people aren't forgetting things. Unfortunately people coming from an engineering/pro…
A lightweight process works well when you have engineers that are all of the following: - experienced - competent - understand their problem domain - actually care
In other words, a team of strong engineers (and a great, accessible product owner).
What I’ve found is that lightweight agile fails without a lot of oversight and frequent checkins, for anything else.
So SCRUM is SE training wheels because it forces a cadence, gets engineers to start breaking down work, and estimate; but the cost is that it holds-back great engineers with all of the (stifling) ceremonies.
I’ve gently nudged my risk adverse tech-lead to consider moving to Kanban now that his team is pretty strong now.
Wildlife photography was fun for a while. If you avoid baiting the animals, it sortof becomes a game, figuring out where they live and how to get close without scaring them off. Making any significant money off it seems unlikely though.
Wildlife photography was fun for a while. If you avoid baiting the animals, it sortof becomes a game, figuring out where they live and how to get close without scaring them off. Making any significant money off it seems unlikely though.
I always wonder why more people don't use wildlife photography as a more challenging alternative to hunting.
Earlier quoted context omitted.
Which in today’s days of remote work, management may actually like. You may have hit on a carrot.
Mentally making the move from writing code to management needs to be a shift in mentality from "I'm making software systems that solve problems" to "I'm building teams that solve problems". Team building is people skills, and it's about finding well springs of motivation, soft skills, getting people talking to each other, making sure people aren't forgetting things. Unfortunately people coming from an engineering/pro…
The way I see it is businesses can have it one of two ways:
They can acknowledge that remote work is fine and allow their teams to work from wherever and figure out timezone differences and async collaboration workflows
Or
They can decide that remote work doesn't work. Then they must stop hiring expensive remote consulting firms and cheap offshore remote teams. They also must stop spreading teams out across multiple regional offices across North America
It is absurd to make people commute to an office building only to have people dialing in to meetings from other office buildings in other countries anyways, and then say remote work doesn't work
I am in my mid-70s now and for the first time in my life I can’t find part time work. I have had three really good leads in the last four or five months but in each case there was no job unless I accepted a full time position. Sadly at my age, I don’t have the energy for full time work, so it is what it is. My wife is happy I am not working, and she literally would not accept it if I tried a full time gig, even just…
However, the company is sliding downhill imo, there have been constant layoffs and eventually I am sure I will be caught in one of them
I'm really not happy about the idea of searching for a new job again, in this new "AI assisted morons" stage of bureaucracy
I'm strongly thinking about trying to pivot to independent consulting. I know it's a tough path to follow and I'm nervous about it, but I have 15 years of experience now and I know I can probably do more with it than most companies will ever let me
I can't get a job, so I start a company. Not sure if it's super backwards.
I never stopped developing. After getting laid off in April 2023 after 13 years as first a full stack then mobile dev, I just started working on things that interested me. I did apply and interview a few times, but I started to realize that pushing 50 and being as cynical as I now am, I'm pretty much unemployable as an IC. So I released my application to the App Store this month, and while savings are dwindling, thin…
I have heard this a few times from different people/places, but why is it the case that at 50+ it is harder to find work? Assuming a regular retirement age, there are still many more years left in the career than a typical tech employment lasts.
I think this begins to be visible even sooner, 38 if you graduated at 23. The majority of the job market requires very very few 15+ years experienced engineers. 5 to 10 years of experience is a sweet spot - you will be easily hired. Everything below and beyond is a struggle, especially for the latter since very few companies need and are willing to pay for those skills.
And that's how you become unemployable with the irony of being at more or less what would be the peak of your technical capabilities. In years later on, people start to lose the drive.
Earlier quoted context omitted.
Mentally making the move from writing code to management needs to be a shift in mentality from "I'm making software systems that solve problems" to "I'm building teams that solve problems". Team building is people skills, and it's about finding well springs of motivation, soft skills, getting people talking to each other, making sure people aren't forgetting things. Unfortunately people coming from an engineering/pro…
> I do think that remote work makes things harder, and I've yet to see a remote team that fires on all cylinders The way I see it is businesses can have it one of two ways: They can acknowledge that remote work is fine and allow their teams to work from wherever and figure out timezone differences and async collaboration workflows Or They can decide that remote work doesn't work. Then they must stop hiring expensive…
But yes, mixing remote and on-premise and expecting it to produce improvements is broken. Or being done for the wrong reasons.
I seem to have landed myself at a job like that just recently, in hopes of sparking joy with in-person collaboration again. I am not happy about it.