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 - "taste of reality"
-
Lemon juice
Water
Vodka
Limoncello
Splash of gin (I used Bombay)
Sugar/replacement to taste
Ice
Tastes like traditional lemonade, but this one is a great remedy for burnout/reality.
Highly recommend!random without her effort i couldn’t type hard lemonade done right alcohol helps i’d like to thank autocorrect for this post reality rehab root drinks again root has a reality problem6 -
I want to get your take on an icebreaker I was subjected to recently. For a 9 a.m. Monday morning training last week, the facilitator opened with, “Tell us your name, your team, how long you’ve been with the company, and a ‘scar story’. Pick a scar on your body and tell us how you got it. If you prefer not to talk about a physical scar, you can tell us about an emotional scar.” I am not joking.
As we went around the room, there were lots of blood and guts stories (gross) but people also shared really traumatizing tales, like an infant daughter being diagnosed with leukemia. The whole thing took 30 minutes of a 90-minute session. I was very turned off by the activity in the moment and even more so later after reflecting a bit.
Besides this one being in very bad taste, I find myself turned off by icebreakers in general. They feel forced and never seem to give you a useful introduction to your colleagues. I’m wondering if your readers have ever participated in an icebreaker they think was particularly effective or are these just a reality of office life we need to endure?3 -
Hey guys, first time writing here.
Around 8 months ago I joined a local company, developing enterprise web apps. First time for me working in a "real" programming job: I've been making a living from little freelance projects, personal apps and private programming lessons for the past 10 years, while on the side I chased the indie game dev dream, with little success. Then, one day, realized I needed to confront myself with the reality of 'standard' business, where the majority of people work, or risk growing too old to find a stable job.
I was kinda excited at first, looking forward to learning from experienced professionals in a long-standing company that has been around for decades. In the past years I coded almost 100% solo, so I really wanted to learn some solid team practices, refine my automated testing skills, and so on. Also, good pay, flexible hours and team is cool.
Then... I actually went there.
At first, I thought it was me. I thought I couldn't understand the code because I was used reading only mine.
I thought that it was me, not knowing well enough the quirks of web development to understand how things worked.
I though I was too lazy - it was shocking to see how hard those guys worked: I saw one guy once who was basically coding with one hand, answering a mail with another, all while doing some technical assistance on the phone.
Then I started to realize.
All projects are a disorganized mess, not only the legacy ones - actually the "green" products are quite worse.
Dependency injection hell: it seems like half of the code has been written by a DI fanatic and the other half by an assembly nostalgic who doesn't really like this new hippy thing called "functions".
Architecture is so messed up there are methods several THOUSANDS of lines long, and for the love of god most people on the team don't really even know WHAT those methods are for, but they're so intertwined with the rest of the codebase no one ever dares to touch them.
No automated test whatsoever, and because of the aforementioned DI hell, it's freaking hard to configure a testing environment (I've been trying for two days during my days off, with almost no success).
Of course documentation is completely absent, specifications are spread around hundreds of mails and opaquely named files thrown around personal shared folders, remote archives, etc.
So I rolled my sleeves up and started crunching as the rest of the team. I tried to follow the boy-scout rule, when the time and scope allowed. But god, it's hard. I'm tired as fuck, I miss working on my projects, or at least something that's not a complete madness. And it's unbearable to manually validate everything (hundreds of edge cases) by hand.
And the rest of the team acts like it's all normal. They look so at ease in this mess. It's like seeing someone quietly sitting inside a house on fire doing their stuff like nothing special is going on.
Please tell me it's not this way everywhere. I want out of this. I also feel like I'm "spoiled", and I should just do like the others and accept the depressing reality of working with all of this. But inside me I don't want to. I developed a taste for clean, easy maintainable code and I don't want to give it up.3 -
When your car got empty battery and won't start in a mall parking lot. This is life. I will buy an extra battery next time and study on how to install it myself.