Details
-
Skillsruby, powershell, bash, HTML
-
Locationgermany
Joined devRant on 4/25/2017
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
/*
* 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. 😋35 -
Friend: Hey, can you fix my laptop? The hard drive is almost full.
Me: (Looking through his folders) Maybe it's because of this. Why do you have 3000+ files in your downloads folder? Maybe I should delete some of this.
Friend: No no, please don't touch the downloads folder, I have some very important documents there.
Me: Why don't you move them to a separate folder then? You should organize the ones you actually need and delete the rest. This folder is a complete mess.
Friend: No no, the problem is not the downloads folder, there must be something else. Can't you just uninstall some programs to free up space?
Me: I could, but I don't know which ones you actually use.
Friend: What? You should know!! You studied computer science for this!!
Me: First of all, there is not a single class in the whole 4 years of university called "How to uninstall programs and free up space on 128GB hard drives of shitty €400 computers". Second of all, I don't know why you were expecting me to find a magic button on your laptop that immediately frees up all the space in a hard drive without actually deleting anything. That's not how computers work, you know.
Friend: Hey if you didn't want to help me you could have said so in the first place.
Me: FML18 -
Her: Hey, just heard what John did to you.
Me: Yea. I can't believe he screwed me over like that. I thought he was my friend.
Her: Don't worry. Forget about the bustard. You know #FFF
Me: 🙁 #FFF? What does white got to do with all this.
Her: What???
Me: #FFF. This is white.
Her: Nooooo. It means Fuck Fake Friends. As in the G. Eazy song.
Me: Ohhh😐23 -
I had genuinely forgotten devRant had a light theme until I saw a rant about it. I went into settings and turned it on for about four seconds, screamed "MY EYES" and rejoined the dark side.4
-
I totally agree.
http://m.imgur.com/a/EOt7W
.
.
I still using WhatsApp just because some people I know don't want to switch 😥, anybody is in the same situation? Haha8 -
My very first meeting with a new client:
Client: We need to launch in 6 weeks. Do you think you can hit that deadline?
Me: Do you have a spec for what needs to be done?
Client: No we don't.
Me:3 -
"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.105