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
-
Absolute same. Terrifies me to be stuck in my current company, terrifies me to leave. I am given only the most vague requirements, but basically no restrictions. My tests are dog folding and my scrum is my rubber duck.
My code hasn’t considered big O time, and data management is way more important than building data structures. I so rarely have to modify the databases I’ve all but forgotten how the are set up.
But I can probably write code more robust than you can imagine. 4-5 billion USD per year in product flows over this code base. Most of it churned out of like 3 PC’s in an attic.
I die under a stop watch. My brain decided to stall updates when I try to write on a whiteboard. But give me something you want to sell, a vague blurb, and some time and I can give you the masterpiece you didn’t know you wanted. I can take your half baked plan and have it ready for flight quickly and safely.
What do you tell interviewers as a "Senior developer" when they ask you what you do at your current job.
I've been with my current for almost 8 years, since graduating... Few different time but not very well managed (semi/barely agile). Hasn't really provided any skill growth opportunities. Mostly fixing production issues, chasing other teams.
The projects I've worked on are in many different languages either enhancements or some standalone stuff. But nothing that's huge and I don't think I've learned anything from them. I usually apply what I learn and practice outside of work to work.
So to me I can probably list a whole lot of projects but to me their not that amazing, I didn't learn anything from them.
Also about those algorithm questions. I've never used any of this stuff actually at work. Concepts yes but not how do you implement ... And honestly I've never once had a situation that required algorithmic thinking other than maybe writing recursive functions in rare occasions...
But to me I've never once done anything harder or new which I haven't already done on my own....
Sorry for the disorderly rambling this turned into... which is sorta a problem too.
Everytime I think about interviews, I want to give rants about we technical questions are BS, how I probably have enough real experience to tackle any problem and come up with a good plan/solution (in a realistic timeframe, not 20 minutes from design to implementation)
question