So, in my Country there are people actually selling 40 empty folders for about 3 dollars... As a gift they also send an empty .doc file... And people are buying it!!!

I really, really don't understand people.

Made a post showing gameplay video from my game "Hang in There" - hundreds of like on it, people commenting how original it is, and that they want to play it "now".

Released the game a couple of days later... less than 15 installs - and the freaking game is FREE :/

Here it is, judge it yourself:
https://play.google.com/store/apps/...

Smart AI is a threat to humans.

The world laughed at iPhone when it removed the jack.
Now more companies are doing it, wtf

So i was playing around with terminal apps in node.js a few weeks ago and made a CLI version of devrant. Images get converted to ascii just for fun. This is about was far as it goes for me though - anyone want to take it over? (The code is shit - this was a midnight proof of concept). Currently there's pretty much just the rant listings, the login works too but I think @dfox would need to approve it's use.

Next script I'm writing is going to be a terminal rant posting tool so I can rant from my server 😉

$ rant -m "fml" -f ~/screenshot.jpg -t "lol"

I'm a front end developer who knows Ruby on rails and Node Js, I still call myself a freaking FRONT END DEVELOPER because I don't have enough knowledge of the required concepts to trust my skill in a complex backend project.

How the fuck there are so many full stack developers who lack shit tons of knowledge in both specialties! And worst of those are asp.net "FULLSTACK DEVS" that can't write JavaScript without copying and pasting from SO and don't know that display flex is a thing!

Why does the Python developer have crooked teeth?

Because he doesn't use braces

When you see "Database must be encrypted with SHA1 or SHA2" in software requirements specification....

Ha, accurate.

Human V1.1

Relatable....

alias wow="git status"
alias such="git"
alias very="git"

Result:

$ wow
$ such commit
$ very push

/*
* First anniversary of devRant unofficial for Windows 10 (UWP)!
*
* Let's celebrate by giving me 500 ++'s 😁
*/

Exactly 1 year ago, on 18 May 2016, I released the first public version (v0.9.2.0 BETA) of my client for Windows 10 users.
I found this wonderful community a few days before, on 12 May 2016, thanks to an article on TNW.
The only flaw was the missing Windows 10 Mobile client for my Lumia 950, so I decided to create a simple one on my own that initially allowed you only to see the list of rants, without the ability interact with them.
A few days later, after spamming the app on twitter, I was reached by @dfox, a very kind person, who gave me all necessary tools and help to bring all official features to Windows 10 users.

A project that I created initially just for fun and necessity became the main project I'm working at in a very short time.

I received a lot of positive reviews from users that motivated me to improve and continue it.
It's true, Windows 10/Windows 10 Mobile users are few, but they appreciate your work as no other and with a lot of feedbacks and suggestions help you to improve it making it very satisfying.

I would like to thank @dfox who made this possible, my friend @thmnmlst who helped me a lot with precious advices and created the presentation below, and of course the whole Windows 10 community! 😉

Good Ranting!

P.S.
If you haven't tried it yet: https://microsoft.com/store/apps/...
For all updates follow me on twitter: https://twitter.com/JakubSOfficial

The v2 is coming... sorry for the delay, below a little preview (alpha) to be forgiven. 😋

People with programming languages named after them:

Haskell Curry
Ada Lovelace
Agner Erlang
Blaise Pascal
Taylor Swift

"Oh you're a developer?"

"Yes."

"Hey I've got this awesome app idea. You build it all and you can get 10% of the profits?"

!rant

I made devRant pancakes!
yummy

"You gave us bad code! We ran it and now production is DOWN! Join this bridgeline now and help us fix this!"

So, as the author of the code in question, I join the bridge... And what happens next, I will simply never forget.

First, a little backstory... Another team within our company needed some vendor client software installed and maintained across the enterprise. Multiple OSes (Linux, AIX, Solaris, HPUX, etc.), so packaging and consistent update methods were a a challenge. I wrote an entire set of utilities to install, update and generally maintain the software; intending all the time that this other team would eventually own the process and code. With this in mind, I wrote extensive documentation, and conducted a formal turnover / training season with the other team.

So, fast forward to when the other team now owns my code, has been trained on how to use it, including (perhaps most importantly) how to send out updates when the vendor released upgrades to the agent software.

Now, this other team had the responsibility of releasing their first update since I gave them the process. Very simple upgrade process, already fully automated. What could have gone so horribly wrong? Did something the vendor supplied break their client?

I asked for the log files from the upgrade process. They sent them, and they looked... wrong. Very, very wrong.

Did you run the code I gave you to do this update?

"Yes, your code is broken - fix it! Production is down! Rabble, rabble, rabble!"

So, I go into our code management tool and review the _actual_ script they ran. Sure enough, it is my code... But something is very wrong.

More than 2/3rds of my code... has been commented out. The code is "there"... but has been commented out so it is not being executed. WT-actual-F?!

I question this on the bridge line. Silence. I insist someone explain what is going on. Is this a joke? Is this some kind of work version of candid camera?
Finally someone breaks the silence and explains.

And this, my friends, is the part I will never forget.

"We wanted to look through your code before we ran the update. When we looked at it, there was some stuff we didn't understand, so we commented that stuff out."

You... you didn't... understand... my some of the code... so you... you didn't ask me about it... you didn't try to actually figure out what it did... you... commented it OUT?!

"Right, we figured it was better to only run the parts we understood... But now we ran it and everything is broken and you need to fix your code."

I cannot repeat the things I said next, even here on devRant. Let's just say that call did not go well.

So, lesson learned? If you don't know what some code does? Just comment that shit out. Then blame the original author when it doesn't work.

You just cannot make this kind of stuff up.

Is it possible to provide feedback on a colleague's code, without him/her getting offended? I haven't figured this out yet..

Yesterday: Senior dev messages out a screenshot of someone using an extension method I wrote (he didn’t know I wrote it)..

SeniorDev: “OMG…that has to be the stupidest thing I ever saw.”
Me: “Stupid? Why?”
SeniorDev: “Why are they having to check the value from the database to see if it’s DBNull and if it is, return null. The database value is already null. So stupid.”
Me: “DBNull is not null, it has a value. When you call the .ToString, it returns an empty string.”
SeniorDev: ”No it doesn’t, it returns null.”
<oh no he didn’t….the smack down begins>
Me: “Really? Are you sure?”
SeniorDev: “Yes! And if the developer bothered to write any unit tests, he would have known.”
Me: “Unit tests? Why do you assume there aren’t any unit tests? Did you look?”
<at this moment, couple other devs take off their head phones and turn around>
SeniorDev:”Well…uh…I just assumed there aren’t because this is an obvious use case. If there was a test, it would have failed.”
Me: “Well, let’s take a look..”
<open up the test project…navigate to the specific use case>
Me: “Yep, there it is. DBNull.Value.ToString does not return a Null value.”
SeniorDev: “Huh? Must be a new feature of C#. Anyway, if the developers wrote their code correctly, they wouldn’t have to use those extension methods. It’s a mess.”
<trying really hard not drop the F-Bomb or two>
Me: “Couple of years ago the DBAs changed the data access standard so any nullable values would always default to null. So no empty strings, zeros, negative values to indicate a non-value. Downside was now the developers couldn’t assume the value returned the expected data type. What they ended up writing was a lot of code to check the value if it was DBNull. Lots of variations of ‘if …’ , ternary operators, some creative lamda expressions, which led to unexpected behavior in the user interface. Developers blamed the DBAs, DBAs blamed the developers. Remember, Tom and DBA-Sam almost got into a fist fight over it.”
SeniorDev: “Oh…yea…but that’s a management problem, not a programming problem.”
Me: “Probably, but since the developers starting using the extension methods, bug tickets related to mis-matched data has nearly disappeared. When was the last time you saw DBA-Sam complain about the developers?”
SeniorDev: “I guess not for a while, but it’s still no excuse.”
Me: “Excuse? Excuse for what?”
<couple of awkward seconds of silence>
SeniorDev: “Hey, did you guys see the video of the guy punching the kangaroo? It’s hilarious…here, check this out.. ”

Pin shoulders the mat…1 2 3….I win.

Accidentally moving a file and reverting the change while the file was in use in Bash for Windows. Now I have a file even the sole Administrator (me) does not have access to delete...