Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Get a devDuck
Rubber duck debugging has never been so cute! Get your favorite coding language devDuckBuy Now
Search - "fast-paced"
“Our market leading software company has an urgent need on our agile team for a passionate self starter whom is able to work with minimal supervision in a fast-paced and dynamic environment on cutting edge technology. If you are a rockstar developer, let’s talk. “
All credit to Chris Jones.1
When I switched jobs from a slow-paced media company, to a fast-paced startup and learned what my team leader can accomplish in a day, would take me atleast 3 days... Not to mention doing things I wouldn't dream of thinking about them.
This experience has made me doubt my very own existence, let alone skills.2
So I need some advice from some fellow devs here...
I recently accepted a job offer at a new company and I'll be leaving my place of work for the last 11 years. I'm a senior level dev who comes from a place where software is more of a secondary function and the skills of my peers are very... Atypical of most software developers.
My interview was ok, but I passed the mark barely - in that they recognize I'm rusty and have some gaps to shore up, but have decided to give me an offer anyway. I'm taking a "step down" to enter in as a level below senior to get my foot in the door of a real tech company.
I've got myself convinced I'm setting myself up to fail, despite being told by people that work there that they encourage mistakes and that they wouldn't be offering me a position if they didn't think I'd be successful.
Is it typical to feel inadequate and worried you'll be fired prematurely for underperformance? I've had little to no experience in a fast paced tech job so I have little to refer to. I was a very high performer where I'm coming from, but that's hard to equate to where I'm going. It seems like classic "impostor syndrome".
I've not even started there yet but I'm terrified my anxiety will get the better of me before I even have my first day there. Anyone out there have any advice?
I'm excited for this new opportunity but I can't seem to shake the fear of the unknown.4
'We are a fast paced team where you will have a lot of opportunity for growth'
Do you sponsor conference tickets?
Can I get some programming books?
Do I get chance to goto meet ups?
If you can meet the deadlines and have free time.
... How am I supposed to learn then?
The worst part of being a dev
My social dilemma
In a fast paced world where the average human spends at least 6 hours a day with technology, deriving basic entertainment, pleasures and engaging in various activities.
Here we are the developers that have to engage with technology for longer hours for a living , having to keep up with deadlines, immersing our minds in complicated algorithms and then the endless possibilities of entertainment from the machine in so few human hours a day , you wonder how you’d get off, and to top it up, I personally work from home.
And then the dilemma of overcoming different suggestions from various parties in taking a break off, a break off to what you later ask yourself, thus creating the shadow of doubt, splitting the fragile programmer’s mind , trying to solve this imaginary puzzle, “this bug of the mind”.
Then the challenge often arises in creating a balance, telling yourself, just catching up with people with this same technology takes a whole day, or then again quitting my Job, but from my little experience of life, nobody likes a poor visitor, this is actually worse than a “bug” and as I bask in this quagmire, “a little voice in my head keeps singing keep doing what you love doing”.
Like an infinite loop of crazy, spiralling back to these machines, trying the find and fix the balance of normalcy. Always remembered the cool years of college tho, with so much people around and then again that was college.
An then the thought arises, maybe something else might be worth doing, but after so much time spent in building your skills and the enormous joy of programming even typing without looking at the keyboard is a real pleasure, and yeah sure the days are short with the reality of a constant need to survive, remain sane, compete and make the best of life in such short time.
Then how do we know if we have fallen off the so-called “social track”, when we have only lived so little to really comprehend the most parts of life? with such constant stream of unanswered question, you’d realise you shouldn’t have burdened the mind creating such questions in the first place
But then again maybe it gets better, one of the above, the disturbed mind or the situation as whole and yes I try oh I try, I place calls, do some visiting, no relationship tho but with a good perspective in mind.
In this race of life, you sometimes ask yourself would you rather be in a different position, or maybe already put exactly where we belong. For this illusionary fight with self is a fight with reality as a whole and true bliss comes from actually letting go as time and people pass you by.
And my greatest achievement to date aside family and my work is getting into the 1000 club on devRant.2
Was at a party the other day and was talking to some randoms and they asked me about programming and said it must be fun and fast paced to do it on your own...
All I did was smile and told them I have spent 10 days trying to decide on 16 colour codes for a part of the software the average consumer will never even see...
Game development everybody!4
I need some advice here... This will be a long one, please bear with me.
First, some background:
I'm a senior level developer working in a company that primarily doesn't produce software like most fast paced companies. Lots of legacy code, old processes, etc. It's very slow and bureaucratic to say the least, and much of the management and lead engineering talent subscribes to the very old school way of managing projects (commit up front, fixed budget, deliver or else...), but they let us use agile to run our team, so long as we meet our commitments (!!). We are also largely populated by people who aren't really software engineers but who do software work, so being one myself I'm actually a fish out of water... Our lead engineer is one of these people who doesn't understand software engineering and is very types when it comes to managing a project.
That being said, we have this project we've been working for a while and we've been churning on it for the better part of two years - with multiple changes in mediocre contribution to development along the way (mainly due to development talent being hard to secure from other projects). The application hasn't really been given the chance to have its core architecture developed to be really robust and elegant, in favor of "just making things work" in order to satisfy fake deliverables to give the customer.
This has led us to have to settle for a rickety architecture and sloppy technical debt that we can't take the time to properly fix because it doesn't (in the mind of the lead engineer - who isn't a software engineer mind you) deliver visible value. He's constantly changing his mind on what he wants to see working and functional, he zones out during sprint planning, tries to work stories not on the sprint backlog on the side, and doesn't let our product owner do her job. He's holding us to commitments we made in January and he's not listening when the team says we don't think we can deliver on what's left by the end of the year. He thinks it's reasonable to expect us to deliver and he's brushing us off.
We have a functional product now, but it's not very useful yet and still has some usability issues. It's still missing features, which we're being put under pressure to get implemented (even half-assed) by the end of the year.
Should I stand up for what I know is the right way to write software and push for something more stable sometime next year or settle for a "patch job" that we *might* deliver that will most definitely be buggy and be harder to maintain going forward? I feel like I'm fighting an uphill battle in trying to write good quality code in lieu of faster results and I just can't get behind settling for crap just because.9
Before 2012, I always worked in cubicles and had weekly status meetings. In 2012 I moved to a big city and learnt there was something worse than cubes: the open work plan. Marketed as a way to increase coloration, the open work space is really just the result of real estate prices being expensive in cities and how desks are cheaper than 3-cube walls.
Up until 2013, we'd usually just have the weekly status meeting. Here are your tasks for the week. I'd do them at my own pace. Some days fast, some days slow, but they'd all get done by the end of the week and I'd proudly go down my list of stuff I had done.
Since then, it's all been "agile" and "stand-ups" every. fucking. day. The work is endless. A Product Owner once told me that stand ups weren't suppose to be status meetings; that you were only suppose to say if you're blocked or need help. But in every place I've worked at, they're daily status reports. You have to preform every day.
I really hate IT today more than ever. I miss the cube. I miss the weekly status reports. Today things are so high stress and higher paced and the work is endless. You can't even really pace yourself anymore.2
I just returned from a 1 week vacation and my boss summonned me for a 1 on 1, and said he is not satisfied with my work, as I don't deliver "fast enough" according to him and do not show enough enthusiasm. I just nodded and didn't answer out of shock.
Background: It's my first dev job, and it's in a really fast paced startup. I have no degree, and I'm here for 3 months. I'm 23 years old, he is around 30.
I really don't know how should I feel about this. It's the first time someone tells me stuff like that and I'm kinda depressed. I know I sometimes work slower than my colleagues because I have less experience but I never thought it would come to this.
Interviewing with three companies. First one extended an offer. I'm expecting an offer from at least one, possibly both, of the others (On-site with Second was yesterday and expecting an offer tomorrow or Mon, phone tech interview (they also had a tech screen) with Three was today and I /rocked/ it, expecting an onsite invite for next week).
The problem with being a badass is that the choice paralysis is SO OVERWHELMING. All three have features that I like and how do I choose.
I think I'm being overly influenced by the weekly massage, onsite barista, free nice breakfast/lunch, and ideal location of Second (the domain is finance, they have $$$). Oh and fucking 25 vacation days and amazing 401k matching. I mean how would I say no to an offer? But what if the work is actually beyond me? But they have seriously cranked their benefits package up to 11.
First is an in house product with external clients. The domain I don't find super interesting, but it has amazing Glassdoor reviews, seems like a decent environment, and really seems like a place to progress and grow as a professional. It is also the lowest salary of the three (both others are through Hired, so I know what they are offering).
Third is a consultancy where I'd really get to keep my skills relevant. Seems mad fast paced, which is a bit intimidating, and I don't know how well I'd handle the context switching of being on multiple projects at a time.
I mean, all of this is counting my chickens before they hatch. But I have a really good feeling about my chsnces with Second, though I suppose I still have a chance to botch my onsite with Third.
Ahhhh. Dev Rant, how did you go about choosing between offers that can't be evaluated on a single axis?1
Does anybody else feel a little sad when reading rants or negative comments concerning frameworks you've used a lot or maybe even more in case you're still using them?
In my particular case I just read some comments tackling Angular - and I do not want to say, that those comments aren't justified. We're currently living in a more than ever fast-paced front end framework world and Angular is simply not state of the art anymore.
So I do not want to start a "what's the best framework" discussion here, that's not my intention.
This is more about the feeling you get when you've built a lot of stuff using a framework, maybe you have still projects running on this framework or even contributed.
Either you do not have the time to switch to another framework yet or you're even still somehow satisfied with the way they're working.
However - reading all this negative stuff about such a framework is sometimes not that easy.
..or am I just some kind of strange, sentimental developer guy? ;D12