Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API

From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "principal"
-
I had an interview yesterday with the CEO of a startup going into Series A for the position of Principal Developer, remote. I've only ever heard of 'tech-bros', but I was unfortunate to meet one in-person. It went something like this:
CEO-bro: Good morning.
Me: Morning.
CEO-bro: It says here on your resume you live in X. That place is a shithole, and I have to look down on you because of that, bro. LoL.
Me: ......
(40 minutes of self-promotion pass)
CEO-bro: Anyway, we don't pay high salaries but offer bonuses for high performing staff instead. I'll ask HR to send you an offer.
Me: Let me think about it.
CEO-bro: One question bro. You have siblings?
Me: One.
CEO-bro: Parents still alive?
Me: No...what?!
CEO-bro: Yeah, me too. People like us don't let anything get in the way.
I wrote them an email this morning withdrawing my application 🤦🏽♂️11 -
Hey Root. Here’s a new ticket for you. It involves lots of things you’ve never seen before, and the only person you can ask is out this week.
Hey Root. Why haven’t you been making good progress every day? Why didn’t you reach out to the guy on FTO? Clearly you can’t communicate. Give me detailed status updates twice a day at specific times, covering <exhaustive list of topics> so I know you’re working. What do you mean “no”!?
Hey Root. Stop working on that ticket, and work on this other ticket. It’s the same thing, but different. High-priority!
Hey Root. You asking questions about that ticket pissed off a legendary golden boy principal dev, and he said it’s a bad idea and that we should have assigned it to a different team, too — you know, the team who usually works on these areas. But we might still have you do it. Please work on the previous ticket that’s in the exact same area until we decide.
Hey Root. Why haven’t you gotten anything done?11 -
## 4 years ago:
- Principal Architect: We are using IO1 storage type. What if we used GP2?
- Perf team: IDK, let's test it!
*we run tests*
- Perf team: results are OK, but we're exhausting Burst IO capacity, effectively hard-limiting number of tests we can run per day
- PArch: ahhh, I see. Then Gp2 is a no-go.
## 3 years ago
*PArch quits. New one is hired*
- PArch2: We are using IO1 storage type. What if we used GP2?
- Perf team: We've already tested that a while ago, results were THIS and THAT
- PArch2: I see. Let's test it again anyway
- Perf team: *wtf???*
*we run the same tests, we get the same results*
- PArch2: I see, so GP2 is a no-go.
- Perf team: *you think....? How did that thought never cross our minds, we wonder...*
## 2 years ago
*new DBA is hired*
- DBA2: We are using IO1 storage type. What if we used GP2?
- Perf team: We've already tested that a while ago, results were THIS and THAT
- PArch2: We've already tested that a while ago, results were THIS and THAT
- DBA2: I see. Let's test it anyways. I've read somewhere that GP2 might be a better bet
- PArch2: you might be right, let's do that
- Perf team: *wtf???*
*we run the same tests, we get the same results*
- DBA2: I see, so GP2 is a no-go.
- Perf team: *you think....? How did that thought never cross our minds, we wonder...*
## 1 year ago
*DBA manager left; new one was hired*
- MGMT_dba2: We are using IO1 storage type. What if we used GP2?
- ........
Should we even bother bringing up the history.....?14 -
I have an interview with a CEO and product owner next week for the position of principal developer. The job ad which got me here stated 'Any additional skills you have will be viewed favorably'.
I've had my ass burned by that crap at least once before. When they ask about private projects, I'm just going to say "I love my job so much, I do it in my free time too!"3 -
Can someone explain to me why non-technical people even work in tech companies ??
I really don't want to sound like an asshole, but can you, for example, imagine that someone who doesn't even know what brick is would work on a construction site ?
Or can you imagine working in bike repair shop not knowing neither how to ride a bike nor how's bike is built ?
Sure, every company (especially large ones) needs bookkeepers/HRs/accountants etc. that don't need to know the inner workings of business.
Those people don't bother me, and they are necessary to keep the circus going.
I'm talking about all those middle management individuals.
All those "Project Managers" , "Business Analysts", "Directors' , "Principal Program Managers " etc etc ..
Such thing thing would be unthinkable in every other industry but somehow, in tech, anyone can work as long as they can throw a sufficient number of acronyms around.9 -
Do you want to know why all the popular open source projects have less-than-optimal, sometimes really dirty code?
It's because their developers ditched all the unnecessary stuff to just get the damn thing done. When I choose an open source dependency, I don't need unfinished stuff. I need a stuff that works and has all the features I need from the very start. If it works, I don't care about code quality in my deps.
This is the reason why dirty, rushed stuff with a great idea behind it gains popularity. PHP, Git, jQuery, the list is quite large.
While you've been busy polishing your files hierarchy, these guys already shipped their product, gained adoption, and their userbase doesn't need your product anymore.
This is applicable only for true open source, not "it's developed by a full-time team of principal developers and the CTO is fucking Kent Beck, it costs $1m per month but yea we have it on github".3