Aaaaaand burnt out.

:|

Just finished coding/support/putting fires down marathon that lasted 2 weeks.

Basically I launched 2 gaming servers got around 600 online players and had to spend 2 weeks around 12 hours everyday supporting them doing hotfixes and etc. I had no time for life. Ioved the work, debugging, responsibility and making impact. Also made some money.

Now I feel completely drained, sick and tired. I think I hit a burnout. I thought I will enjoy my time off with my gf but I just wanna lie in bed and dont do shit for at least 2-3 days. Extended stress over time did a number on me, I am now a nervous wreck.

How can I bounce back asap after a burnout? I have 2 weeks to rest and will have to launch 2 projects again and deal with christmas/new year bullshit...

Disabling pasting into a password field in 2020 with password managers, is retarded. That's it that's the rant. Doesn't matter if you think password managers are good or not. Its still retarded that there's a 40 something year old dumbfuck manager who told a web designer at EA to disable pasting into a fucking password field because he was dumb enough to think it stopped hackers or some shit like that.

Had to wake four people up at 2 am to fix a crashing service.

10/10 would deploy to production on Friday night again.

How I got better at programming ... Hire people smarter than me. They’ve taught me a lot.

PM: Your code bombs! It’s supposed to put a link to the schedule here!

2 minutes earlier:
PM: *runs code with malformed data and two cancelled schedules*

Always try to work with people more skilled than me.

Back from long weekend... Already want another...

Perhaps I've finally realized the team cannot be saved, work isn't fun anymore, it sucks being the linchpin, and I'm just not having fun anymore...

And for one I think I've even take a pay cut to get onto a new but better managed and 100% senior team

The comments of a tired developer.

I uh.. use arch

#truth

I only develop UIs with react and only ever with functional components

I would actually DIE without my MacBook Pro 16”

I spend roughly 30 minutes a day trimming my beard. I’m a civilized man after all

I only drink Starbucks coffee, and only if it’s a triple pump latte

Ew what’s jQuery? Sounds like something my grandpa used

Omg really? Are you still using PHP in 2020?! Lame!

Gross. Windows is for n00bs and Linux is for nerds. macOS FTW

Post is comprised of quotes from a classmate who annoyed the living hell out of me

Achievement unlocked
Killed production database for 40 minutes

Found this in my spam box...
Warning: Follow link with caution... I still don't know why the hacker spams with the "d" word in the action url:
https://mysp.ac/4fylg/...

When you finally get to use that tensorflow side project you've been working on for a while to solve a real world problem and your boss wants to know how it works.

Good things come out of software engineering.

My best friend supported her husband for several years, financially and emotionally. Her job allowed him to focus on his training, and also allowed her to move with him to the US. Yesterday he got his UFC contract.

I am so incredibly proud of them. As engineers, we rarely get the spotlight, but we have the ability to help our loved ones go very far.

To my ex manager

you left to berlin, and left me to rot

my new lead sucks, i kid you not

it was ok if I slacked off, You used to be chill

But my new lead is uptight, he's on my list to kill

I wanna run errands in work hours, is that so bad?

was doing so for years, now i lost what i had

I cant drive in peace, coz i know he'd call

so i had to cancel plans to go to the mall

its like 10 to 6 is now constant work

I hate my new lead, he is such a jerk

password.trim()

High school. The teacher in IT made some learning platform for the school in PHP. There was a module where you could upload files.

You could just upload a PHP file, and get it to run by accessing it through a direct link.

GOOGLE PUSHES .WEBP

GOOGLE SLIDES: "UNSUPPORTED IMAGE TYPE"

F************

Going through git commit history to figure out when *the programmer fucked up this code.

* I am the only programmer.

There was a time in Windows 95, where during login, you could just press cancel and you were logged in without the need of a password.

- you don't like math
- you don't like study
- you don't read documentation
- you throw out the manual
- you like to punch a clock
- you dislike books and reading
- you don't ever work more than 8 hours
- you can't tolerate the occasional weekend work day
- you fold under pressure
- you aren't good at crunch time
- you can't do on-call without committing seppuku
- you don't have attention to detail
- you aren't interested in technology
- you're not good at explaining things
- you can't deal with change
- you're not excited by the prospect of extreme variety
- you don't have the ability to focus
- you can't deal with ego without resorting to violence
- you can't deal with someone calling your baby ugly
- you can't discriminate between fact and opinion

And many, many more

relately

I tried to mix
relate and lately.
Because lately, I can relate to this.

To be a good developer, you must thrive in chaos, and have an insatiable desire to turn it into order.

All user input, both work tasks and actual application input, is pure fucking chaos.

The only way to turn that input into anything usable, is to interpret, structure and categorize it, to describe the rules for transformation as adequately as you can.

Sometimes companies create semi-helpful roles to assist you with this process. Often, these people are so unaware of the delicacy of the existing chaos, that any decision they make just ripples out in waves leaving nearly irreparable confusion and destruction in its path.

So applications themselves also slowly wear down into chaos under pressure of chaotic steak-holders which never seem to be able to choose between peppercorn or bernaise sauce for their steaks.

Features are added, data is migrated between formats, rules become unclear. Is ketchup even fucking valid, as a steak sauce?

The only way to preserve an application long term, is refactoring chaos into order.

But... the ocean of chaos will never end.

You must learn to swim in it.

All you can hope to do is create little pools of clarity where new creative ideas can freely spawn.

Ideas which will no doubt end up polluting their own environment, but that's a problem for tomorrow.

So you must learn to deal with the infinite stream of perplexed reactions from those who can't attach screenshots to issue reports.

You must deflect dragging conversations from those who never quite manage to translate gut feeling into rational sentences.

You must learn to deal with the fact that in reality there are no true microservice backends. There are no clean React frontends. There are no normalized databases. Full test coverage, well-executed retrospectives, finished sprints -- they are all as real as spherical cows in a vacuum.

There is no such thing as clean code.

There is only "relatively cleaner code", and even then there are arguments as to why it would be "subjectively relatively cleaner code".

Every repository, every product, every team and every company is an amalgamation of half-implemented ideals, well-intended tug of war games, and brilliantly shattered dreams.

You will encounter fragmented shards of perfect APIs, miles of tangled barbed documentation, beheaded validator classes, bloody mangled corpses of analytical dashboards, crumbled concrete databases.

You must be able to breathe in those thick toxic clouds of rotting technical and procedural debt, look at your reflection in the locker room mirror while you struggle yourself into a hazmat suit, and think:

"Fuck yes, I was born for this job".

Whoever decided to put a "No to all" button in Notepad++, I wish you and your family a healthy and wealthy life. I hope you will get a pay rise and be successful in your career.

- Windows OS user after a long while. Closing a lot of files was a nightmare back then.

Ah yes, progress...
Why do SJWs have to infiltrate everything and project their own racist views of the world onto non-problematic terms?
Slavery has existed for as long as humanity and abolishing the terms will definitely not solve slavery and opression.
I am not against Git changing the default name but I am against them doing it in the name of "inclusivity". The technical world exists by merit and not inclusivity. Why make everything about color, race or slavery level?

I lost my sanity and googled ”FUCK YOU XCODE YOU FUCKING PIECE OF SHIT”...

That's how I found devRant.

Found some ancient pdfs.

Hey everyone,

We have a few pieces of news we're very excited to share with everyone today. Apologies for the long post, but there's a lot to cover!

First, as some of you might have already seen, we just launched the "subscribed" tab in the devRant app on iOS and Android. This feature shows you a feed of the most recent rant posts, likes, and comments from all of the people you subscribe to. This activity feed is updated in real-time (although you have to manually refresh it right now), so you can quickly see the latest activity. Additionally, the feed also shows recommended users (based on your tastes) that you might want to subscribe to. We think both of these aspects of the feed will greatly improve the devRant content discovery experience.

This new feature leads directly into this next announcement. Tim (@trogus) and I just launched a public SaaS API service that powers the features above (and can power many more use-cases across recommendations and activity feeds, with more to come). The service is called Pipeless (https://pipeless.io) and it is currently live (beta), and we encourage everyone to check it out. All feedback is greatly appreciated. It is called Pipeless because it removes the need to create complicated pipelines to power features/algorithms, by instead utilizing the flexibility of graph databases.

Pipeless was born out of the years of experience Tim and I have had working on devRant and from the desire we've seen from the community to have more insight into our technology. One of my favorite (and earliest) devRant memories is from around when we launched, and we instantly had many questions from the community about what tech stack we were using. That interest is what encouraged us to create the "about" page in the app that gives an overview of what technologies we use for devRant.

Since launch, the biggest technology powering devRant has always been our graph database. It's been fun discussing that technology with many of you. Now, we're excited to bring this technology to everyone in the form of a very simple REST API that you can use to quickly build projects that include real-time recommendations and activity feeds. Tim and I are really looking forward to hopefully seeing members of the community make really cool and unique things with the API.

Pipeless has a free plan where you get 75,000 API calls/month and 75,000 items stored. We think this is a solid amount of calls/storage to test out and even build cool projects/features with the API. Additionally, as a thanks for continued support, for devRant++ subscribers who were subscribed before this announcement was posted, we will give some bonus calls/data storage. If you'd like that special bonus, you can just let me know in the comments (as long as your devRant email is the same as Pipeless account email) or feel free to email me (david@hexicallabs.com).

Lastly, and also related, we think Pipeless is going to help us fulfill one of the biggest pieces of feedback we’ve heard from the community. Now, it is going to be our goal to open source the various components of devRant. Although there’s been a few reasons stated in the past for why we haven’t done that, one of the biggest reasons was always the highly proprietary and complicated nature of our backend storage systems. But now, with Pipeless, it will allow us to start moving data there, and then everyone has access to the same system/technology that is powering the devRant backend. The first step for this transition was building the new “subscribed” feed completely on top of Pipeless. We will be following up with more details about this open sourcing effort soon, and we’re very excited for it and we think the community will be too.

Anyway, thank you for reading this and we are really looking forward to everyone’s feedback and seeing what members of the community create with the service. If you’re looking for a very simple way to get started, we have a full sample dataset (1 click to import!) with a tutorial that Tim put together (https://docs.pipeless.io/docs/...) and a full dev portal/documentation (https://docs.pipeless.io).

Let us know if you have any questions and thanks everyone!
- David & Tim (@dfox & @trogus)