py_or_dy
Joined 6 years ago
Joined 6 years ago
Oh, but onto your questions. So yes it is frustrating. And as far as feedback. I stopped asking for feedback because it was always maligned. Nobody will really know why you didn't get hired, remember, these companies aren't really hiring unless you are young and cheap. In most cases my feedback sounded like it was almost for someone else. Like "needed more linux experience (I haven't touched a windows or mac OS since 2005). Or my favorite, after talking about a data warehouse I built to house 5TB of data and 15 billion rows, and all the different schemas I migrated through, their reason was they wanted someone with "more database experience".
Curious how you get an offer such as this? I've thought about changing job roles, but I really suck at leet coding so I've never really bothered. I figured that as a 40 year old male, no one would hire me for a role unless I was already experienced. Is that not the case?
You say it is thriving, I say it is not. So who is correct? Every job I applied for was django development with a remote team. Once I'd get rejected, I'd keep an eye on the company's linkedin page and see who got the position instead of me. In two cases it ended up being someone much more senior than I (like 10 years experience in pure django), and in 3 other cases it was someone with less than two years of experience and who recently graduated from a coding bootcamp (and I guarantee they are paid no where near $100k). And in about 10 other cases, the linkedin page has stayed the same, so not sure if they hired anyone at all or what. But I've only really been paying attention to the pages for about 15 different companies versus the 60 or so I interviewed for.
Edit: Oh and about the wage thing... forgot to mention for many of these smaller software shops they are now doing most of their hiring out of South America. Fullstack labs, consumer affairs, just to name a few but the list goes on.
I was in college at the time and couldn't wait to graduate and start rolling in money. I mean, these two programmers didn't even have degrees and I was about to have one. That meant I could do the same thing only charge $100 an hour right?
My first "IT" job out of college I made $54k a year. After three years I got my first promotion to $64k but quit a few months later. Did a couple of 1099 contracts at $50 an hour over a year. Got hired by Apex and sent to AT&T for $35 an hour. Did that for a year and then back to 1099 contracts again. This time at $55 an hour. Moving on up! After 4 years of that, quit cold turkey and figured with 10 years of experience now under my belt that I could easily find some better contracts or full time work.
22 months and 110 interviews later, still nothing.
But on the other end... I've worked with some people that are pretty good at leetcode and very fast coders. But even though they write many pages of code every day and tons of commits, their code is absolutely horrible, full of bugs, impossible to read. They got stuff done, but it was at great cost in the future. That was mostly why I left my original job in the first place (looking for work now for 18+ months). We hired a couple of new people and they were pumping out so much code I couldn't keep up with all their commits. Bugs started rolling in and they were too busy working on the new projects to fix their old crap. Boss had me hunting down and digging through their garbage code while my projects were getting behind and I was the one "under-preforming". I started going insane, unable to get out of bed, staring out the window for 12+ hours a day unable to look at their code. Mostly walked out. Those new people all quit after I left as well but the company's market crashed due to covid so we would have all be laid off anyway.
The interviews were all the same mostly. Do a take home project or do leetcode problems while the interviewer stares at you. Sometimes I did bad, sometimes I did alright, and other times I did great. It didn't seem to matter. The funny thing is as I got more desperate, I started applying to crappier companies and more junior positions for lower pay. As I went down the ladder, the interviews got even more complicated and challenging!
A couple of years ago I got interested in HVAC technology after having my HVAC unit replaced and researching options. As I'd mostly depleted my savings, I started debating on jumping ship to be an HVAC tech. I could cram for an EPA certification test over a couple of weeks and get a refrigeration cert and then be nearly guaranteed a position at a couple of local HVAC shops for $15 an hour. The only reason I haven't done that (yet) is like you said because of my kids. My life story would be I went to tech school out of high school and was an avionics tech for 3 years, followed by 5 years to get through university, followed by 10 years of software developer experience and then 2 years of no work followed by becoming an HVAC tech working with high school drop outs as co-workers. There would be no telling my kids to get an education when this (forced) path I'm on shows how worthless it is. I've never felt so lost and useless in my entire life.
The other reason for not jumping ship (yet) is that I feel so qualified on django/python stacks. You could drop me into any dumpster fire of a django project and I'd be fine. It is extremely insane that the only people getting hired in that space are people with under 2 years of experience or people with over 10 years of django only experience. There is absolutely no middle ground (which is where I fall in).
I'm now debating jumping on a difference language with a smaller community (similar to how perl used to be) like golang or elixir. But there is no guarantee there but I feel like hiring in that space would more likely respect past experience or at least know that if you graduated college and have years of experience that you would be able to "mostly learn anything" and be reliable. Dunno...
I spent the last 5 years quite happy at a simple dev shop. Then they hired a bunch of people, paid them more than me, and allowed them complete free reign to write what ever kind of code on some brand new projects. After a year of this, one person quit mid-project, another died mysteriously (covid?), and then another just recently quit. My boss expected me to just pick up the slack on these three projects that were written in the most arcane and buffoon way possible. I basically just said no, and left. I had already been driven half insane over the year just trying to figure out the crap they were committing.
This was in the spring and I'm still unemployed. I'm mostly Java and some older languages, and was really looking forward to jumping onto python and django. But it's been a struggle really learning django good enough to interview for without any good experience behind me. I have a family and on top of covid issues and this year in general, sitting at home trying to learn a giant web framework is not very motivating when I could be spending it with my family (which were already severely affected by all my time I "wasted" going above and beyond at my last job for 5 years).
I just recently did an interview for a small django shop that didn't even test on django. Instead, I was given a half page of python code and asked to "fix" the problems. No requirements or tips. There was a syntax error, a bug, and a few cosmetic things.. I managed to find 8. All this while being stared at over Zoom. I was informed that "junior" devs can find 10-12 "problems", but they only hire those that "find" more than 18 (apparently 25 is the max).
I still got the code and look at it every now and then. Half a page of code that does nothing but take a list of "item" objects and print out an aggregate of a total price by item type. A loop over nothing but:
total[item.type] += item.cost
Of course there was some random data mangling above and below that, but that is the logic. Find the problems?! Should I raise errors or use a namedtuple or defaultdict? Half a page of code that could have just been a Select/Group by in SQL. No senor dev should be summing data like that. Sadly they said the code was from "production". They have "interviewed" over a hundred people in this year and hired only 1. All this for $45/hr 1099.In the beginning, I briefly thought I could use my savings to start some kind of business, not sure what. But I've blown most of that just paying the bills while I "interview".
I used to love software and would dream and breath it. But I've never been so unmotivated over these last 6 months. I'm debating on just applying at a local small town municipal IT job for $30 an hour. Giving up basically. Just show up at 8am, answer the phone mindlessly for IT "problems" and tell people to try restarting their windows machine (at least 3 times minimum) and screw of playing solitaire the rest of the day. But it seems so pointless and waste of a life. But even that doesn't motivate me, but just makes me more depressed and even slower going.
Perl 6 was finally released in ~2018 but by this time no one cared. The perl 6 team feels because of the name 'perl', people aren't adopting this new language, so they change the name. And now a year later, the small perl 5 team is wanting to take perl into the modern age by breaking backwards compatibility. It makes no sense at all, that was the job of perl 6.
It would no different if I started complaining about python 2 not getting any updates and then making a plan to better improve its parser and object model and break backwards compatibility and bring it into the modern age. Python 3 already did that, so like what the heck are you doing???
And then the comments from the perl 7 supporters... saying things like we can either "fight or die" or doing nothing is "certain death" but the alternative is "uncertain hope". I just don't see the point in fighting for something the original author of gave up on over 20 YEARS ago.
I've stated my points [0] before on how companies that stick with perl 5 do so at their own demise. They get cultured into a train of thought where updating software is seen as bad and unhealthy. And if they are a consultancy, their downstream customers also get cultured in to never having to worry about "updates" and/or paying for updates. So then long term contracts with said customer only take into account the cost of feature enhancements instead of "maintenance". So then it becomes impossible to move either consultancy or customer off of the "perl platform" because going to something like django, while a big cost in its own right, would involve a different long term contract that would require paid support and downtime for future django updates/releases. Never mind that finding devs would be easier (and probably cheaper), and the fact that django gets regular security audits and has a much larger plugin/library support ecosystem.
Anyway, to each their own. And godspeed to the perlings out there, I just don't see how any of this is worth it...