Joined devRant on 5/13/2016
Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
During the course of my career I've stumbled on like 6-7 people I've worked with and it was really great. Every now and then we meet up and chat how it'd be great to form a team again and work on something (we're all in different companies atm).
Lately we've been mentioning that even more and are considering whether to start working on a product/find clients and form an agency/join some other company.
We have experience with both outsource and products. Our profiles range from development, design, marketing, UX, HR, PM.
Any road we take has pros and cons. We're least fit to start on a product because we'd need more profiles, have to figure out finance and would probably have to work alongside our current jobs.
I've been thinking of writing a joint letter when I hear a company is opening up an office in our city. When that happens, usually whole teams are formed and most of the profiles I mentioned are needed.
Do you think that's even possible? Is there another way we're overseeing? Have you heard of or attempted something similar?
Any advice is truly appreciated.2
How to waste money as a dev company, 101:
Give people ton of budget for their education to do whatever they want with it with no oversight at all:
1) Devs go to some shitty confs in places across the world that teaches them nothing (new) so they can visit interesting places on company's money
2) Go to a conf where you learn ton of stuff that can be implemented right away
...Then you come back, no time to do stuff properly, just "make it work" (or make it seem like it works), because of deadlines, poor prioritization, new features, bad planning, vague roadmap and poor client management. And the worst of them all, LGTM code reviews.
Few months later, who the fuck wrote this shit? Oh, dude that left? What about this mess? Oh, he's a goner too. What the fuck should this random undocumented chunk of code do?!
Do that a few times and you've got bunch of pissed off clients with a ton of bug reports nobody can solve without wasting 20x the amount of time it would originally take.. LGTM
I'm so sick and tired of people feeling threatened when improving upon their shitty code! I'm here to do a job and I enjoy my profession.
Don't take that away from me by wasting my time making me say every fucking time that I come from a good place and that I just want to provide a better solution AND not create fucking mess that will have to be rewritten when some ninja bugs occur because of completely unmaintainable crap nobody can understand. Holy shit!
I couldn't care less if you're 10 years in the company. I see that all the good devs left after dealing with your shit every God damn day.
I'm not here to deal with your insecurities and couldn't care less about pointing fingers! I just wanna do better and not write same level of quality over and over again!
You're not getting bonus points from me by sitting on your ass all day and half-assing everything you do with some lame ass excuse.
So no LGTM from me when it's utter error prone shit!
So if you don't wanna help, just get the fuck outta my way and don't waste my time! Jeeez
After a few years at one company, most of the colleagues that take their dev education seriously have left. We had a mini community keeping ourselves up to speed as technology progresses. As time passed, I've noticed that I'm stagnating which is one of the biggest signs, for me, that I should move somewhere.
I'm now at a new company, working on a project that is in a much worse place than any of the project I've worked on previously.
I've done my due diligence and checked the company before joining, of course. And I've asked all the questions I wanted to know so I can know with some level of certainty whether we're the right fit. Sadly, that definitely didn't turn out to be true.
I'm currently working on tasks that any intern/junior can work on, while being paid a senior salary. There are a lot of areas in the project where I can spend my time more efficiently, e.g. stability, performance. But, it turns out that swapping colors, brushing some css here and there is more important to the client than fixing very, very unstable project.
And I'm not the share holder. It's not up to me to decide. The only thing I can comment with certainty is, why just not hire 2 juniors that can do the same work I do right now, instead of wasting my time/energy on meaningless tasks and such boring issues that I've left behind years ago. I've emphasized that being challenged is very important to me, and I'm given breadcrumbs to deal with.
And I'm unsure what to do now. I don't want to be that guy leaving just a few months after joining. Should I wait it out? I already mentioned that I don't think I'm properly utilized to lead dev and PM. I guess I should give them a month or two to see whether something will change?2