There's a lotta memes about Google spazzing out whenever you log into a new device, but Fitbit is even worse lol

I not only get a notification that my Fitbit's battery is low, I also get a fucking email about it.

Like y'all chill out. I know it's low.

I'm sure this can be disabled somewhere, but I'mma probably get a new watch soon so I'm too lazy to deal with it

Found the dragon book, second edition, a pretty famous compiler book at the following url:

http://informatik.uni-bremen.de/agb...

Just in case anyone is interested in it. It kinda trips me out that for 1000+ pages its only 4.somethingmb and apparently it comes from the University of Bremen, it was on the top Google results.

I think its clean, not a security expert, so if someone that is more skilled in it that I am wants to go ahead and check it out let me know

😂😂😂🐍🐍🐍

TDD.

I'm a fan of writing tests right after you write every module. I actually think it's doable.

But I'm not a big fan of traditional TDD, which is defined as: first writing the tests, making them fail, writing code until tests don't fail.

My experience with traditional TDD when writing library code is that you start with this very naive idea of what is needed, so you write classes and functions and a lot of times they look like overly simplistic pseudocode.

So what do you do? You scratch that, you delete those classes/functions several times.

I think this discovery process that your code is naive is slowed the fuck down by doing TDD.

I'd rather write a theoretical API in a readme file, then write code, and then write the tests, you can even withhold writing the tests, but never leaving them for another day, just so that you don't waste time writing tests that you're going to scratch.

There's always a time constraint, and most of us can't afford bikeshedding.

Traditional TDD feels like an esoteric thing, it tries to make programming a series of steps, it actually sounds like an infommercial.
"FOLLOW THESE 3 SIMPLE STEPS AND WRITE THE BEST CODE EVER"

Good morning 😅😅😅

Hey @dfox can we have a moving ++ -- button or a button at the end of a post, so i can like(or not) a long post after i read it?

This one project at my study.

We always had to do quite some documentation, even some in a way that works the opposite of how my brain works.

That's all fine if you can agree on doing it differently.

Had this teacher who valued documentation above anything else. The project was 10 weeks, after 9 weeks my documentation got approved (yes, not a single line of code yet) and I could finally program for the remaining 5 days.

Still had quite some bugs at say number five, the day of presentation.

I imagined that'd be okay since I only had 4 full days instead of the 5-8 weeks everyone else had.

Every bug was noted and the application was "unstable" and "not nearly good enough".

At that moment I thought like "if this is the dev life, I'm out of here".

FUUUUUUCK
Spent 3 days trying to find out what I'm doing wrong and why the server cannot send emails in an obsolete project (https://devrant.com/rants/1806850). I started debugging the PHPMailer SMTP library (v2.0.3 since it is the only one that works with PHP4) and found out THIS SHIT.
WHO THE FUCK confuses = for ==

Just accidentally found out that double tapping a comment/post ++s it.

I feel like this feature has been a thing for a long time but I forgot about it

My day

Fellow devs can understand...

So can I request that we keep my ++ like this forever?

The story of the $500,000,000 error.

In 1996, an unmanned Ariane 5 model rocket was launched by the European Space Agency.

Onboard was software written to analyze the horizontal velocity of the spacecraft. A conversion between a 64-bit floating point value and a 16-bit signed integer within this software ultimately caused an overflow error just forty seconds after launch, leading to a catastrophic failure of the spacecraft.

That day, $7 billion of development met it's match: a data type conversion.

Yesterday, my employer promoted me to lead web developer.

I’m still the only web developer.

The codebase I'm currently working on is so fucking damn wrong that I made a folder for screenshots called "facepalm".

Well yeah. He is right!

I’m making a puzzle game! Cool!

Concept - done
Mechanics - done
Art - done
Ui - done
Puzzles - uhhh... this is harder than expected.

Finally decided to give Arch Linux a go on hardware.
I've never had so much fun installing a distro before.
I chose Deepin as the desktop environment, it's fucking beautiful.
(I somehow didn't really take to i3, I prefer a full blown environment like Deepin).
Since it's my first time using Arch and Deepin, do you guys have any advice? How you like to use and maintain Arch? Any tips? Productivity hacks? (Besides a tiling WM)

Some Cable porn...

I was talking with a few people from college recently and we all had a good laugh at the fact, That a lot of job postings for mobile developers state that they are looking for an senior/intermediate android developer that has anywhere from 10 -15 years experience.

I even had an interview and in it they stated that they are heart set on finding someone with 12+ years of experience.

but Android was only release 9 years ago... SO HOW ARE YOU SUPPOSE TO HAVE 10+ YEARS EXPERIENCE

Senior dev : * doesn't use git *
Me: you seriously should use git...
Senior dev: * still doesn't use git *
Senior dev: * overwrites production files with old files from other computer *
Senior dev: * talks to boss *
Boss: * gets angry at me *

!rant

Is there a difference when your rant reach 500's?

Does it start to be called +1's instead of ++'s

Just saw it on https://devrant.com/free-stickers

So there is this girl who was trying to be cute and wrote a mock C code for me :

She wrote :

If(existence=disapointment)
printf("kill self");
else
printf("what else??");

And without hesitating I told her that her code had a fault in it and it would always print "kill self" no matter what the level of disappointment is. And asked her to fix it.
The way she fixed it was probably best described as the situation when you have no idea what you are doing and you don't try to understand either. (or was simply passive aggressive) :

If(existence=disapointment)
printf("kill self");
else
printf("kill self");

Honestly though I hope she was being passive aggressive because boy do I pity people who confuse between '=' and '=='

New senior dev joined the project today.
Senior dev: "There's no way for me to test my changes before I merge this into develop"
Me: "Can you at least run our test suite?"
An hour later the develop branch is fucked and everyone who has merged it locally has pages of red errors splattered across their screens whenever they run any tests.
Start looking into what the fuck is going on.
Notice that all the errors are related to changes the new guy made.
Ask him if he ran the tests..
Senior dev: "Nah they wouldn't catch anything locally "
Stare at the stream of red text running down my screen.
Normally I wouldn't care but we were trying to prepare a release... RUN THE FUCKING TESTS ASSHOLE.

Just shaved my beard and immediately regretted it. I look like a snail now... And my Linux skills are gone...

Someone called me an incapable, arrogant bitch today because I didn't let them test in prod. We had words.

The monologue from Full Metal Jacket went through my head at one point, and I almost didn't mute my phone in time before I said it rather than just thinking it. I'm not sure I would still have a job if I did, but I kind of wish I didn't mute my phone.

So only 28 to go before my fluffy friend can join me, been waiting so long. 🐱

If you open 100 tabs on Chrome using mobile app, you get a smiley

My GitHub repo has a little over 1,000 downloads but only 433 stars does that seem off to anyone? For an employer does GitHub stars on a project even matter?

Don't overload yourself with many projects at the same time. Seriously.