9,274 karma · joined July 1, 2021
Filter on years of experience - if you're right that 10 YOE is a useful threshold, it will make your candidate search much easier. I think it would be a really bad approach to hiring though because there are many incompetent people with 10 YOE and many great people with less experience. At the end of the day what you want is a good candidate, not a "true senior".
Senior engineer since when I had less than 5 YOE - I'm not claiming anything, I'm just using the title used by my employer. Nothing good will happen if I remove the "senior" from my title - in some cases it won't make any difference, in others it will actively harm me and make it more difficult to get the attention of certain recruiters and hiring managers. I'm not sure what you expect someone in my situation to do.
It's not every 1.x year, the author is excluding everyone who doesn't spend at least 3 years on a project.
I get why you would have this on your list but I'm not planning on staying at a job that I don't like, or with a company that's underpaying me, or insisting to be stuck on the same project for 3 years just so I can meet someone's arbitrary criteria for a senior. And I'm saying arbitrary because:
> worked in at least 2 companies (or vastly different teams)
> worked on 1 codebase for at least 3 years
so 6 months at job 1, and 3 years at job 2 (without changing codebase) makes you senior but 10 years with 4 jobs of 2.5 years each is not senior?
This why all of this is pointless gatekeeping - you're senior if you have a senior title. And if you do, it doesn't mean all that much and that's okay.
So I would be careful about throwing out all process, you can't just tell people to do the work and leave them alone - that doesn't scale as teams and companies grow. There's an art in hitting the right amount of process.
2. Customizable themes.
3. Some way to indicate responsess to your comments/threads.
> And no, Coursera unfortunately won't make the cut most of the time.
Some of the best universities in the world have computer science materials online (on Coursera and youtube), I don't get how that's inadequate.
> most would hesitate to hire self-taught developers, even in web development positions.
Not true for experienced candidates. If you have no experience, you rely on your degree to get the first job; and if you don't have a degree, it can be difficult to bootstrap that process but the further you get in time from your education, the less relevant it is.
What are these?
Keep in mind that most analytics roles are a move down from most software developer jobs in terms of technical skills required, salary, prestige, job satisfaction. The last part is obviously my personal opinion - my background is in data science and early on in my career I could leaned more towards analytics or more towards software engineering and I very quickly figured out that I strongly prefer the engineering jobs (whether it's ML engineering, or even non-data science- or ML-related software development). Right now I'm data scientist in title, with an MLE job description and responsibilites, and I'd be happy to do either MLE or backend development in my next job. Analytics and data engineering are positions that I actively avoid. But again, that's just me, plenty of people like these roles.
Second, it's a problem solved by a spreadsheet, not by a SAAS solution.
Rust is in a weird place where people are trying to push it in a bunch of places where it doesn't belong naturally (web dev, data science) but then when you complain that it's difficult to use you get told that you're using the wrong language for your use case...
I really want to like Rust - I've read the Rust book, done the Rustling exercises, read Zero to Production in Rust and did the project there, and still it's not clicking - writing Rust is a slog where you have to jump through hoops and spend a lot more time thinking about programming language abstractions than thinking about the problem you're solving.
So I'm not in a rush to rewrite anything written in Python just yet.
My problem with this is that my skills expire and I need to repeat the study and practice time with every interview cycle.
It's pretty obvious that Bard was something Google had to do given the circumstances and there must have been a big push for it from very high up in the company; very unlikely that it's someone's promotion project.