4000 years later, we are back to the same language

Stop building a unicorn, let's build horses!

expectation vs reality

Release.....

It's Friday guys.

Counter strike

refactor...

<shitpost>
<p>Get it? Cuz IE is slow. Hue hue ++ if you laughed like I did!
</p>
</shitpost>

God I'm immature.

i can hack your fb :-D

And we still have to google how to vertically center text with CSS 😅😅

True story 😂

Getting comfortable in one place for too long and stagnating. It can be easy to automate your job until you can just milk it, but sit still too long and your skills will be irrelevant.

People talk about ageism in development... don't let your mind get old and you'll always have job security.

..........

who else had similar problems :/

Correct...

Kenyans lost these great devs in a terror attack. A moment of silence

Saw this one on twitter. lol

Log files ...

This passes all unit tests

The perfect hot line bling gif doesn't exi...

Is it just me or does github default avatar is basically showing the middle finger?

What is "vacation"?

Drunk me coding.
Next day: WTF, dude…?

In a world of password managers that can generate complex passwords of any length, please for the love of God include why my chosen password was rejected.

Don't decide to truncate the password without informing the user because, and this is key, they won't be able to use your service.
Looking at you GoDaddy.

Two kind of programmers

This looks good!

The users will be able to create a sandbox, basically a seperate Kernel for running a lightweight Windows Sandbox using Hypervisor for running/testing .exe files.

https://theverge.com/2018/12/...

So, we are having a SaaS service for people where they can build X stuff. It is all fine as long as you are using basic things there, no complex cases and so on. Even on some complex - it does work just fine.

Here's the rant itself:
The production server throws us errors every 5-10 minutes that something broke and fails to do job X. At first we were all hands on deck fixing it ASAP to make it stable to later realise that most of these cases were users doing stupid shit. Then we began to fix the core issues rather than chasing every single issue there is (costs are important you know) - funny enough, we get few support requests a week and our 1h response time + 24h fix time usually buys us that customer and allows t o leave a great impression.

So all in all, bugles production is good but great support - is way better. Users can deal with issues especially if they are experimenting there but when they need answers - you'd better give it to them.

This baby is coded

Credit imgur.