Newton's fourth law:

For every bug fix, there is an equal and opposite bug creation.

Made me chuckle!

The bar hasn't moved in a while...

Only thing i don't like in home project repositories is i'm the only who commits :(

try {
♥️
}
catch(e) {
🍺
}

#happyvalentinesday

I just wanted some water :(

</2016>
<2017>

😒.

:)) finally a good answer

When one of those "Your windows has been infected, click here to remove virus now" ads slips through the adblocker while I'm on my Linux

A surprisingly honest sales site

CSS can kill you!

"The server is flooded!"

"With requests? DDoS?"

"No."

If we ever colonize Mars or if we even go further I am already feeling sorry for the poor bloke that will have to work on DateTime library.

502 Bad Gateway

#iPhone7

Spotted @LaraconEU - buaha, still loving PHP!

"As you can see, our open-office floor plan really helps with developer productivity"

Made a really cool spinning animation on a button that submits a form...

API Call is too fast to see it

setTimeout

Check out this superb website that I made..

http://localhost:8080

Jaja so true

bono.less

rate my place 1-10

When you are writing a normal query and just realize cached data can save a lot on performance

With all "bug"-posts I can't stop thinking about

About two years ago I get roped into a something when someone was requesting an $8000 laptop to run an "program" that they wrote in Excel to pull data from our mainframe.

In reality they are using our normal application that interacts with the mainframe and screen scrapping it to populate several Excel spreadsheets.

So this guy kept saying that he needed the expensive laptop because he needed the extra RAM and processing power for his application. At the time we only supported 32 bit Windows 7 so even though I told him ten times that the OS wouldn't recognize more than 3.5 GB of RAM he kept saying that increasing the RAM would fix his problem. I also explained that even if we installed the 64 bit OS we didn't have approval for the 64 bit applications.

So we looked at the code and we found that rather than reusing the same workbook he was opening a new instance of a workbook during each iteration of his loop and then not closing or disposing of them. So he was running out of memory due to never disposing of anything.

Even better than all of that, he wanted a faster processor to speed up the processing, but he had about 5 seconds of thread sleeps in each loop so that the place he was screen scrapping from would have time to load. So it wouldn't matter how fast the processor was, in the end there were sleeps and waits in there hard coded to slow down the app. And the guy didn't understand that a faster processor wouldn't have made a difference.

The worst thing is a "dev" that thinks they know what they are doing but they don't have a clue.

@localhost where the magic happens...

The moment you hear that a piece of code you carefully cleaned up (which was 'needed' and took days to fix) is not going be used and better be thrown away... 😠😑😣😒

Well, at least there are no errors...

The moment you know the program is doomed but he insists its perfect