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
-
!rant
Office invested in a new coffee machine. With actual coffee beans.
It also makes hot chocolate.7 -
Running an Alpaca farm in rural Finland, next to some mountain creek with an oldschool water mill so I can grind flour and coffee beans.
I hated people so I tried to find solace as a nerd in technology, but tech is also fucking awful so I feel like retiring in a tranquil forest with some equally grumpy wooly animals.
If I get eaten by a bear because I'm a skimpy city boy that's OK, more epic than being found decomposing slumped over on a keyboard in the boring grey suburbs.
All of this is probably pandemic-me talking though. So sick of this concrete city with the farting cars and fat obnoxious shoppers.
I need some trees around me, and some mammals with a higher IQ than my current neighbors.8 -
Not entirely dev related.
Just wondering if I'm the only one on here who actually EATS coffee beans regularly?
😐42 -
1. Slack. Pretty good chat app for dev companies, I use it to prevent people standing next to my desk 40 times a day.
2. Unit testing tools, especially when fully automated using a git master branch hook, something like codeship/jenkins, and a deployment service.
3. Jetbrains IDEs. I love Vim, but Jetbrains makes theming, autocompleting & code style checks with mixed templating languages a breeze.
4. Urxvt terminal. It's a bit of work at the start, but so extremely fast and customizable.
5. Cinnamon or i3. Not really dev tools, but both make it easy to organize many windows.
6. A smart production bug logger. I tend to use Bugsnag, Rollbar or Sentry.
7. A good coffee machine. Preferably some high pressure espresso maker which costs more than the CEO's car, using organic fairtrade hipster beans with a picture of a laughing south american farmer. And don't you dare fuck it up with sugar.
8. Some high quality bars of chocolate. Not to consume yourself, but to offer to coworkers while they wait for you to fix a broken deploy. The importance of office politics is not to be underestimated.1 -
"As a team, we have the shared responsibility to ___".
(replace with ALL of the following: resolve bugs, do junior's code reviews, clean up dead code, keep the kitchen clean, improve test coverage, write documentation, order coffee beans, etc)
NO. JUST FUCKING STOP RIGHT THERE. Shared responsibilities do not exist. A single person is responsible, and can optionally delegate tasks.
EITHER I DO IT AND I'LL BE FUCKING AWESOME AT IT, OR SOMEONE ELSE DOES — BUT I'LL SLAP SLACKERS IN THE GENITALS WITH MY KEYBOARD.
Fucking startup hipsters with their community driven attitude, this way no shit gets done, ever.7 -
Purple, Ahh yes, the nice colour purple... dont you love looking at something and thinking, "Wow, thats some nice purple"
well, I fucking dont, fuck that piece of shit colour, I FUCKING HATE PURPLE, why?
BECAUSE IT DOESNT FUCKING EXIST! FUCK PURPLE, FUCK IT, ITS FUCKING BLUE! THERE IS NO FUCKING PURPLE!
WAKE THE FUCK UP PEOPLE! IT DOESNT FUCKING EXIST! THERE IS BLUE AND RED, BUT. THERE. IS. NO. FUCKING. PURPLE!
And dont get me started on brown, that nice brown chocolate, these coffee beans...
IF IT WOULDNT LOOK LIKE DARK-GREEN I WOULDNT FUCKING HATE IT! WHY DOES IT EVEN EXIST!
(if your wondering, yes. I have a red-green colour deficiency)25 -
When there is no coffee beans in the office and/or the different ways of making coffee is not working that day.4
-
The new CTO promised us better coffee in his introduction meeting. Honestly felt pretty trivial and part of his used car salesman pitch to us.
A month goes buy and he replaces our shitty drip Starbucks breakfast blend coffee with ... Starbucks coffee machines. I shit you not these things have touch screens on them. So I tried two cups of each bean type and ... this stuff is really really bad. It's literally worse than the drip brew. It's so fucking terrible I have trouble finishing a cup.
God damn it!8 -
New coffee machines at work. Real beans! What's the equivalent of the Ballmer Peak for Caffeine? Posting this at 4.04am, lying awake in bed and not coding, I'm probably past it.. sleep not found2
-
Putting mobile phone to DnD.
Putting on Bluetooth headsets with ANC, blasting some good shit music.
Violently cooking or desperately ordering food at the good restaurants.
While waiting, grinding some coffee beans, making fresh coffee or some nice tea with milk.
Laying on the sofa in a food induced coma, turning on any streaming service with the real bad shitty movies.
Hentai Kamen, The Machine Girl, ...
Anything thats either pure groteske bullshit or that doesn't require more than a braincell cause it appeals either to the violent or complete nonsense side of my brain.
Last but not least, a few cold beers.
ANC headset stays on, just switching from music to tv - shutting out all the outside noise. -
Let
y="coffee beans"
Then (for devs)
y'="coffee powder"
y''="cup of coffee"
y'''="code"
"bug in production which requires urgent fix"=y''''1 -
i had an epiphany today, in a discussion with the software architect of our new project.
i'm having the epic job to design & implement a prototype for a C++ library in a new software project and collected some inspiration in our "old" software, where i'm maintaining the module that fulfills the same functionality (i thought). i've been maintaining this module for around a year now. i analyzed the different features and stuff to consider and created a partial model of the new library.
when i showed it to the architect today, he was like "oh my god, no no no, you don't need all this functionality, this shall not be part of the new library!"
this was the moment when i realized how deeply fucked up the code base of the old module is.
imagine it like this:
you want to automate the process of making yourself a good ol' cup of coffee.
the reasonable thing would be to have
- a smart water boiler where you set parameters water temperature and amount of water to be fetched from the water supply
- a smart coffee bean grinder where you can set type of beans, amount of beans and grinding fineness
- a component where water and ground coffee are joined to brew the coffee, where parameters like duration, pressure etc. are set
- a milk tank where amount of milk, desired temperature and duration / speed of foaming can be set
- a sugar dispenser where amount of applied sugar can be set
- optionally, additional modules with spices, syrup, ice cubes, whatever for your very personal coffee experience
on requesting a coffee, you would then configure and orchestrate all components to your wishes to make you a fine cup of coffee. you can also add routines like "makeCappucchino()", "makeEspresso()", or whatever.
our software is not like this.
it is like this:
- a smart water boiler consisting of submodules that know how to cook water for e.g. "cappucchino with sugar" or for "espresso without sugar, but with milk and ice cubes"
- 5 smart bean grinders that know how to grind beans for e.g. cappucchino, espresso, latte macchiato and for 73ml of water preheated to 82°C
- a very smart sugar dispenser that knows how to add sugar to 95, 98 and 100°C coffee and to coffee made of BOTH coffee arabica AND coffee robusta beans.
etc. etc., i think you're getting the gist.
when i realized this, it was like, right in front of my eyes, this terrible pattern emerged like a foul, corrupted caleidoscope of chaos, through the whole code base of this module.
i've already known how rotten from the core this code base is, but today i've actually identified a really bad pattern that i hadn't realized before. the whole architecture is so bloated that it is hard to have an overview of the whole thing. and it would require a LOT of refactoring to repair this pattern.
but i guess it would also be infinitely satisfying because i could probably reduce the code base for 30% or something...
but unfortunately, this is never going to happen, because screw refactoring.
it's a great feeling to start this new library from scratch, tho...6
Top Tags
Weekly Rant
View