151–160 of 265 posts
Earlier quoted context omitted.
Plastic surgery is another option for onsite jobs.
Sadly, there was an article a while back specifically about tech workers doing just that. Might want to lighten up on down voting given the truth of the statement.
I don't see many old sysadmins in companies I've worked in. Even fewer older developers, I have a slight worry that this career path has an affinity for youth- which I won't have for much longer. So this is disheartening to read.
Of the 3 Linux admins that were above me last decade or so, none are still in the industry. One went into medicine, one went into real estate, and the last I believe became a firearm instructor. None had passion for Linux or sysadmin per se. It was just a job they could get with enough pay and lifestyle (stable location, hours etc) they wanted. When they got older, they simply moved onto different jobs that they thou…
Earlier quoted context omitted.
By that logic people under 30 shouldn't be hired either, because they're more likely to jump ship to another company. TBH, if a single person leaving (for any reason) can tank the company, it's probably doing a person a favor not to hire them. Sounds like a mess.
You are looking at it in black and white terms. Just because there is also a reason younger people might leave unexpectedly doesn't invalidate my assertion. And, having someone leave unexpectedly doesn't have to "tank" the company without still causing damage. Like I said, black and white terms...
Earlier quoted context omitted.
Absolutely nothing wrong with it. But people with families, kids that need help with homework, etc won't be able to do that often if ever. Being young very often also means having fewer commitments.
If you can't play video games with your friend/coworkers from times to times, then your life suck, kids or not.
Earlier quoted context omitted.
Ah, "Grey beard". The term Microsoft used to separate the old from the young at a conference when they first introduced the .NET framework. Classic "old bad, good new" sales. As in, "you Grey Breads remember using C++ and MFC, etc." Yes I remember. Because it was yesterday just before I came to your conference! I still went home and started learning what the hell XML was though. =(
I still can't wrap my head around the fact that we have developers who work on .NET and have never touched either WinForms or WebForms. And I am relatively young.
Business logic and algorithms is what it’s all about.
Earlier quoted context omitted.
WebForms can die in a fire, and thankfully has, for the most part, but WinForms is still plenty good enough for cranking out quick and dirty tools. Maybe I'm old, or it's just because I started out in high school doing VB6 forms applications, but I still prefer it unless I have a good reason, over WPF. WinForms is also a pretty thin layer over Win32 controls, as well, so if you have to switch between .Net and native…
WebForms changed the game. ASP was a sub-subset of VB, but WebForms with C# made websites full-scale eventful and stateful programs for the first time. I had never felt such power and freedom programming for the web. Yes, some people would put humongous data structures in view state, and yes, more-better solutions have arisen, but WebForms deserves your respect!
Earlier quoted context omitted.
And this is why software today is in such a sad state. Managers think it would be great to have an army of young engineers who don't question and just do what they're told. But any leader surrounded by sycophants will eventually fail. Management often doesn't realize that they really need the senior engineer who has the experience and confidence to say "NO". Because that engineer is the one who will prevent the proje…
> Because that engineer is the one who will prevent the project from collapsing under the weight of scope creep and tech debt. That's the shitty thing: there's enough work that doesn't cross the threshold that requires you to pay for technical debt. Otherwise, a lot more managers would be getting burned by it. There's no electric shock when they hit the wrong button. Even if it isn't a "big boom" moment where you can…
Experience is no silver bullet, but it generally goes a lot further than non-technical tea-leaf-reading or junior dev shotgun programming.
I don't see many old sysadmins in companies I've worked in. Even fewer older developers, I have a slight worry that this career path has an affinity for youth- which I won't have for much longer. So this is disheartening to read.
So the opposite exists too...
Earlier quoted context omitted.
That depends on what country you're in. In Japan it's very standard to include date of birth, gender and a photograph on CV's. On the whole I hate the practice, but you have to consider cultural norms when doing the job-hunting dance.
It's also customary in Germany, although I've never had a problem getting a job and I've never attached a photo to my resume.
Earlier quoted context omitted.
That depends on what country you're in. In Japan it's very standard to include date of birth, gender and a photograph on CV's. On the whole I hate the practice, but you have to consider cultural norms when doing the job-hunting dance.
It's also customary in Germany, although I've never had a problem getting a job and I've never attached a photo to my resume.