I really don't see the problem here. If you really can go 40 days then why not let people that critically need it have access?
source: my partner has rheumatoid arthritis and takes hydroxychloroquine, and we've been concerned about exactly this sort of thing happening for a while now.
My God. I'd love to learn more about your background. How, if you've worked in web development since 2007, consider yourself a beginner?
As a self-taught, self-employed coder, I can tell you that you can get extraordinarily far without knowing a single fundamental. Just having a willingness to dig in and tinker will put you miles ahead of what most people are willing and able to do, and you can absolutely build a career out of a can-do attitude and google. Over time, however, what seems to end up happening is that many people in this situation (myself included) learn systems without learning technologies.
At my place of employ, we distinguish between Application Developers and Software Developers, and I think that's a thing a lot of large companies do. Both are valuable, but they're fundamentally different. You can have a very advanced Sitecore Application Developer who writes Sitecore code all day, but if you hand him an IDE and ask him to write up a CRUD, he'll flounder, whereas a software engineer can more or less invent something new on the fly from scratch, but isn't going to be particularly fluent in any given third-party system.
I think, overall, these long-term self-taught web developers hit a wall like they do because they're really application devs and not software engineers. Sometimes, it's actual apps (I'm looking at you, WordPress and Drupal), and sometimes it's libraries or frameworks like jQuery and Bootstrap. I certainly did. It's basically the same sort of fluency one often finds in bootcamp grads, just with much more practice.
I managed to get over the hump by basically starting over after 10 years, relearning the basic fundamentals of browser development and really mastering development with vanilla html, css and javascript, learning the fundamentals of node, local automation, and just enough computer science to be dangerous. With that, I took those skills and started working for other people again, as a developer on a team. I can't tell you how valuable it's been to simply have other human developers to compare myself to. This is what I learned:
1: There are a lot more shitty developers with CS degrees out there than I realized. However mediocre I may be, there are loads of my peers out there being just as bad.
2: You'll advance faster than your peers once you enter industry. Junior developers can usually program, but senior devs use old age and treachery to get shit done. You've done the hard part already by gaining experience -- now you just have to catch up with technology.
3: You'll find the software engineers around you are generally more specialized than you are. People who work for themselves for a long time get very good at doing everything all the time and learning new things quickly because clients are needy and think you're good with computers. This is a superpower. This is what tech leads are made out of.
I mean, look, I couldn't re-implement quicksort of you put a gun to my head, I've never written my own compiler, and my networking fundamentals are complete shite. But I can negotiate for the resources my team needs, I can bash a misbehaving legacy codebase in a language I don't know into submission fast, I can sniff out an overengineered solution at 30 paces, I can architect a front end, I can delete code at a furious pace, and I can sit on juniors until they start making simple solutions instead of elegant ones.
I'm 40. I've been doing this for 14 years, and I'm exactly where I should be in my career. That's enough for me.
You're doing the work of a higher order function there. You have my thanks.
I've worked in environments where this type of change has been attempted. It's not easy and does run the risk of running VERY awry.
I keep hearing about gender discrimination, and maybe this is a market segment thing, but everywhere I've worked is actively recruiting female devs. Also the places I've worked as a dev typically require a CS degree though for what that's worth. Many of them even require an MSCS -- I've actually been turned down for one job because even though I have an MS it wasn't an MSCS (gov contracts get very specific).
I am absolutely willing to believe it's a market segment thing. I live in a smaller city full of colleges, so the handful of large companies hiring want all of their jr devs to be right out of college, and that's straight from the recruiter's mouths. I was forced to apply to all the small companies.
And, for what it's worth, my current job and the two before it "required" a degree. From what I can tell, that requirement is to filter people on the low end of years of experience. Old age and treachery counts for a lot more than you may think.
Definitely? As in, you have actual proof? Or even some evidence? Because if you do, that’s illegal, and ought to be reported to the DOL.
Oddly enough, I've never met a single one that was female, though that's only anecdotal of course. The only female devs I know have CS degrees.
The focus on CS is important. Developers who don't have it are generally not educated in how to write good code. Many people do get into the field without the degree, but many of them are very bad at programming. I've had to rewrite O(n!) algorithms written by some of them, and they really didn't even understand why the algorithm was bad even when I broke it down to them.
My CS education absolutely gave me many of the tools I need for a career in software engineering. It didn't give me everything to be sure -- there's a lot of learning that still goes on in the job, but having a solid foundation is crucial to being a good engineer.
Anecdote is not data, and it's only my individual anecdote, but it's my experience that breaking through into the industry to be incredibly hard. Since then I've made up for lost time and advanced faster than a college grad would expect (junior dev in a shitty agency to enterprise lead dev in about four years), and I attribute that to spending so incredibly long as essentially a junior dev freelancer and just being older.
So it can be done, certainly, but I strongly suspect there are several filters working against self-taught developer women making that transition into the industry, and one of them is definitely gender discrimination. And no, aside from sending out resumes with a man's name on them, I don't know how to fix it.
I'm troubled by the top-down nature of what is decided to be beyond debate vs not: it feels like it is leading to a scary kind of authoritarianism I don't want.
For fun, I'll throw you a specific plausible hypothetical. If an app has a gender identity field, and a user enters "Apache Helicopter", should this be treated as valid data or not?