I thought the author sounded familiar. He's the person who gave this blatantly sexist and offensive presentation, CouchDB: Perform Like A Pr0n Star , at the Golden Gate Ruby Conference in 2009: http://ompldr.org/vZ2I1cA/gogaruco-couchdb-090418194027-phpa...
Engineers suck at finding the right jobs
51–60 of 134 posts
Re: Engineers suck at finding the right jobs
#52> Now is an awesome time to be a software engineer (probably best time ever). I don't agree with this statement at all, as it's getting harder and harder to find low-level work (e.g., C and *asm) and that's the __only__ kind of programming that I enjoy doing. I'll start looking for another career when I have to consider putting words like ``full-stack'' or ``cloud'' on my resume in order to find work.
I work in assembly and C, and like HeyLaughingBoy, I strongly disagree that there's any shortage of such work. If anything there's a significant shortage of good applicants. Where have you been looking? Are you constrained geographically?
Maryland: in and around Howard County.
> Are you constrained geographically?
Yes, as my wife and I are quite settled in our home.
Re: Engineers suck at finding the right jobs
#53The issue of seniority always bugs me. If a 26 year old guy who writes "good enough" code can be a Senior, which I see very often, what's left? Personally I wouldn't feel right with a title including "senior" until I've got at least 10y experience, generated millions in revenue and lead a team of >10. And I'd still prefer not having a title. Unless the only way to increase a salary is by taking the title, which seems…
The issue of seniority always bugs me. If a 26 year old guy who writes "good enough" code can be a Senior, which I see very often, what's left? Some ideas, possibly an answer: http://michaelochurch.wordpress.com/2012/01/26/the-trajector... What companies tend to call "Senior" is usually around 1.4-1.6 in terms of responsibility. That said, most companies don't give you 1.4-level work until you're 1.7-1.8 in ability.…
Intern
Software Engineer
Senior Software Engineer
Staff Engineer
Senior Staff Engineer
Principal Engineer
Distinguished Engineer
Fellow
All of a sudden, "senior" doesn't feel very far up the totem pole.Re: Engineers suck at finding the right jobs
#54The issue of seniority always bugs me. If a 26 year old guy who writes "good enough" code can be a Senior, which I see very often, what's left? Personally I wouldn't feel right with a title including "senior" until I've got at least 10y experience, generated millions in revenue and lead a team of >10. And I'd still prefer not having a title. Unless the only way to increase a salary is by taking the title, which seems…
...what's left? Where do I begin? - Drilling down multiple levels for greater understanding. Being the "anti-poser" by knowing what's really going on under the hood. Sharing this insight with others. Amazing what a difference maker this often is. - Subject matter expertise. Can you stay two steps ahead of your customers by getting behind their eyes and seeing what they need before they do? - Continuous improvement. (…
Re: Engineers suck at finding the right jobs
#55It really is an exciting time for software engineers. I'm a soon-to-graduate student and have gotten so many job offers that I had to pretty much stop talking about it with friends/family. Does anyone else feel awkward admitting how easy we have it in tech right now when there are so many people struggling to find jobs?
As a soon-to-graduate student as well, I am having the same issue. It is a blessing but also a curse, having to figure out what direction to take from so many options.
I get it, it's just idle carping in an HN post but really, it's not a curse.
Re: Engineers suck at finding the right jobs
#56I thought the author sounded familiar. He's the person who gave this blatantly sexist and offensive presentation, CouchDB: Perform Like A Pr0n Star , at the Golden Gate Ruby Conference in 2009: http://ompldr.org/vZ2I1cA/gogaruco-couchdb-090418194027-phpa...
yes it was me and as you just discovered I'm not perfect and made many mistakes in my life ;) Note however, that I try really hard not to make the same mistake twice and this lessons I learned 3 years ago stuck with me. The question is how relevant is your point? Are you trying to help the discussion or attack me personally?
Re: Engineers suck at finding the right jobs
#57If engineers suck at finding the right job, and companies can't find the right people, then this problem is screaming for better solutions. The challenge here I see is that every employer is looking for 'rockstars', even if the actual job responsibilities may not require one. So, if I'm a 'rockstar', its a big hurdle to separate the reality from the marketing pitch of the magic job. What can be used as a signal for f…
I think there should be a developer tier at 250kish (valley prices)
If you can justify that, we'll call you a rockstar.
Then we'll give you status to go with it in the company (as you're making more than your boss), sort of how external consultants often get that and get to recommend TONS more stuff than line engineers do.
If a position says rockstar, and doesn't pay a quarter mil, we pan you on the web as lying about needing a really highly paid, super highly skilled position.
Re: Engineers suck at finding the right jobs
#58Earlier quoted context omitted.
Cracks me up when people cling to titles. Even funnier when I see software developer 3 on a business card!
I was given a title once, and I think it was a 3 (this was... a heck of a long time ago). But... I wasn't told what the 3 meant - is 3 the bottom? The middle? The top? Is "level 1" where people start? Or is it like golf, where a lower number is better? I asked, and ... got the weirdest look, as if I was an idiot for not having some insider knowledge about "corporate titles". I wasn't there very long. And I never actu…
Re: Engineers suck at finding the right jobs
#59Early in my career Steve Bourne gave me useful advice, he said the difference between junior engineers and senior engineers was that senior engineers had an agenda. More specifically they had an execution goal (like write a new file system, or create a product that solves problem 'X') and they worked toward it.
This is a both a hugely motivating and hugely scary thing, its motivating because you don't have to ask "what do I do now?" the direction just falls out of where you are vs where you are trying to go. It is scary because you can find you're goal isn't compatible with any of the company's goals. When you discover that what you want to do can't be done at the company you are working at, you either have to change goals or leave. But its not a 'feel bad about it' leaving it is 'hmm, this isn't going to work out here so lets go somewhere that it could'.
The alternative to having an agenda is "Goofing off and waiting for someone to give you a task." There are a lot of engineers who operate in that mode, do their assigned tasks at an acceptable quality level and without too much schedule slip. They are great to have around because people with agendas and use them to move the agenda forward, but they don't make for very good 'senior' people because they really don't care what they work on, its not their main focus.
It is important to note that you can't "fail" if you're just goofing off, as one of my kids put it, "It isn't procrastination if you don't have anything you need to do." You can however rationalize your low work output by the fact that your management really hasn't given you all that much to do, so whose fault is that? Whereas if you have an agenda, a goal, a destination, you can fail to make it to that destination. "You said you were going to build a game that could crush Farmville, you failed." Reading the blog post from Speck about Glitch shutting down, "we failed to develop an audience." They had a goal, they didn't get there.
Matt's advice that if you don't know what you want, you can't choose reasonably is solid. Start by deciding what you want to do, and pick something that will take a while as early goal achievement has its own problems.
Re: Engineers suck at finding the right jobs
#60It's very hard to understand what opportunities exist for YOU specifically in the employment market. Seeking out potential jobs is laborious and you can't take the time to talk to every recruiter that calls.
What would be better is if you had a good way to safely broadcast what is interesting to you professionally and indicate the types of opportunities you'd like to hear more about. Safely is the key word here. The system breaks down if it puts your current gig at risk.
Check out http://www.mightyspring.com.
We're working on solving this exact problem. Our goal is to help people stay on top of the employment market and be made aware when a really special opportunity presents itself.