!rant

I'm just about to finish this little project (actually is already done). I just need to add some reducers to change the language of the page.

What do you guys thinks about it?

https://byoigres.com/minutes

At Starbucks today, ordered a lactose free JavaScript Frappucino. The barista turned out to be a computer science student, I'm pretty sure he spat in my cup.

FUCK YOU ACCESS!!! FUCK YOU MICROSOFT!!! FUCK YOU DB PROF FOR FORCING IS TO USE THIS FUCKING PEACE OF CRAPWARE!!!
In the time I spent cursing at Microsofts bullshit I could have done the task twice in MySQL and would already have a nice looking fucking UI for this shit. FUCKING HELL.

Well excuse me for trying to learn Web Dev! WHY MUST YOU JUDGE ME?!

"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.

When you tell your friend to ++ all your rants just so u can unlock more customizations for your avatar 😂😂

STOP IT.
FUCKING STOP.
NO MORE "I SPENT N HOURS SEARCHING A MISSING SEMICOLON"
"I DELETED A SEMICOLON IN MY COLLEGES WORK"
"REWROTE MY CODE BECAUSE MY COLLEAGUE DELETED A SEMICOLON"
OR ANY OTHER SEMICOLON RELATED RANT'S / MEME'S.
Maybe they were funny the first time. But IT'S OVER.
If it should really happen to you, you're using the wrong tools.
If it happens to you even though you're using the right tools, LEARN to use them.
If it does happen to you after that FIND A NEW HOBBY OR JOB, YOU DON'T BELONG HERE.

Thanks for your time - link this rant on any semicolon related rant.

** DOES ALSO APPLY TO MISSING BRACKETS, QUOTES, TABS, SPACES, KIDS, JEHOVAS WITNESSES, MONEY, FLYS, SOCKS, FACIAL HAIR, WINDOWS UPDATES **

if (!rant) Fuck oranges
else
It's about time we make some God fucking damn things fucking God fucking clear. What the fuck does programming have to do with fucking non-programming?

Honestly. Fucking fucks pretending to be fucking programmers (probably not you, but fuck off if you're one of those fuckers.) FUCK SUCH PEOPLE FUCK YOU FUCK FUCK fuck FUCK!

There. Now that's out there. Leave fucking programming to the fucking fuckers who fucking know some-fucking-thing fucking ab-fucking-out it. If you're learning, ask questions, without you there'd be no fucking future for good fucking programmers. But if you're a fucking fuck fucking ducks in the fucking park--fuck the God fucking damn the fuck OFF!

// family tech support

Dad: *clicks something*
Dad: *something strange happens*
Dad: Hey son, come over here. What happened?
Son: Hm.. what did u click?
Dad: I don't know. Aren't you supposed to know that? You're our computer genius.

So this happened...

ERRORs are red,
INFOs are blue.
My logs look pretty,
But not as pretty as-
Wait, hold on. Why are there ERRORs in here?
Why is the homepage returning a 5- oh crap.
Can you just... Can you give me a minute?

Linux evangelism is real.

Credit to Reddit and my brother for waking me up at 3am to show me this.

!rant

So this year I had a subject at university called "Linux internal architecture", and for the last assignment I had to write a kernel module and interact with it with a separate program written in C.

Once I had finished and tested the driver, I went on to write the other program, which was supposed to use system calls to read and write data to the module. While debugging this program (~500 lines of code) I reached the level of frustration where you just start printing absurd messages everywhere in your code to see what's wrong. So for example instead of printing "This error happened in this function", my error messages were more like "Fuck this fucking function it doesn't fucking work".

Guess who forgot to delete all those messages before sending the code to the teacher...

Also, if a specific mode is selected, the program enters a while(1) that, apart from doing what it's expected to do, also creates a file in the user's home directory called something like 'motherfucker' and appends the words 'fuck this shit' to it. INFINITELY.

I really really hope this teacher doesn't try to run the program in his own computer, or he's in for a big surprise.

When my teacher says that you have to produce variable lists for each variable in your program, stating the name, type and what they're used for, if you're coding in Java, you know you're fucked with 16 classes of swing GUI...

Knock, Knock

Who is there?

Browserstandards

Browserstandards who?

ThereAreNo Browserstandards

#FuckIE

when the customer says: "we want this but better and cheaper"

For April Fools at a school I worked for, I printed off one of those "Your printer has been upgraded to be voice activated" signs and put it on their fairly new printer, went into the room opposite and waited. I heard far far too many teachers saying "Copy!" repeatedly, getting more and more agitated before 'manually' copying their document. I had to come clean before I left at lunch time because one of the teachers got quite angry at the prospect of a voice activated photocopier and refused to use it that way. The following year April Fools was on a school holiday so I couldn't pull it in the school I was in that day but i fully expect it to work somewhere else.

Best office prank: I was pretty young and naaive. Senior dev comes to me and says that it would be hilarious to slide a note under the women's bathroom door saying, "I know what you're doing in there". He says that the woman in there will think it's hilarious too. We work with her, she's very funny and laid back, so I go along with it, expecting to get a laugh. A few minutes go by and a different older women enters my cube. She's got the note! She works on the other side of the building so I don't know her too well but I can tell from the look on her face that she's pissed. I'm frozen with fear as my career flashes before my eyes.
I apologise perfusely and try to explain but she's not having it. After a while she goes back to her office not having accepted that it wasn't meant for her and that it was just a joke gone wrong. I spend the next two days apologizing every chance I get, hoping she won't go to HR. She remains stone cold until late on the second day. She couldn't take it anymore as her mouth reluctantly begins to crack a smile. At that point she drops the serious expression on her face and busts out laughing.

It turns out that the three of them planned the whole thing and executed flawlessly. I've never felt so relieved to be the butt of a joke.

#CoderLife

!rant

So I'm looking for advice.
I'm 16 and I'd like to eventually work at some sort of tech startup, probably doing something like web development as that's what I've done the most of. I have been teaching myself and practicing programming for years and have experience with HTML, CSS, JS, NodeJS, Socket.io etc. but don't necessarily have a lot of experience with some necessary frameworks such as ReactJS or AngularJS, so I couldn't really apply for any of the job listings I've seen so far. I currently work in retail so it's possible that I could work somewhere such as an Apple Store.

What's the best next step? Is a university course the right option or should I be trying to find something such as work experience?

If you got to the end, thanks for reading my long winded and badly written post. Looking forward to hearing the advice of some fellow devs.

How many Laravel PHP users here?

I'm working on a larger web project for authorities that went live yesterday.
I also trained the staff for the last two days so that everyone knows how to register an account, use the application etc.

Got the first call today: "I can't create an account...the website does not start".

Uh..okay...what the? >_>

Turns out, the user entered the URL in Google Search and wondered why nothing happens and why the website does not load.

Wow... and that was just the first call.

Waiting for my last build to finish before i get loose for the weekend

*Now that's what I call a Hacker*

MOTHER OF ALL AUTOMATIONS

This seems a long post. but you will definitely +1 the post after reading this.

xxx: OK, so, our build engineer has left for another company. The dude was literally living inside the terminal. You know, that type of a guy who loves Vim, creates diagrams in Dot and writes wiki-posts in Markdown... If something - anything - requires more than 90 seconds of his time, he writes a script to automate that.

xxx: So we're sitting here, looking through his, uhm, "legacy"

xxx: You're gonna love this

xxx: smack-my-bitch-up.sh - sends a text message "late at work" to his wife (apparently). Automatically picks reasons from an array of strings, randomly. Runs inside a cron-job. The job fires if there are active SSH-sessions on the server after 9pm with his login.

xxx: kumar-asshole.sh - scans the inbox for emails from "Kumar" (a DBA at our clients). Looks for keywords like "help", "trouble", "sorry" etc. If keywords are found - the script SSHes into the clients server and rolls back the staging database to the latest backup. Then sends a reply "no worries mate, be careful next time".

xxx: hangover.sh - another cron-job that is set to specific dates. Sends automated emails like "not feeling well/gonna work from home" etc. Adds a random "reason" from another predefined array of strings. Fires if there are no interactive sessions on the server at 8:45am.

xxx: (and the oscar goes to) fuckingcoffee.sh - this one waits exactly 17 seconds (!), then opens an SSH session to our coffee-machine (we had no frikin idea the coffee machine is on the network, runs linux and has SSHD up and running) and sends some weird gibberish to it. Looks binary. Turns out this thing starts brewing a mid-sized half-caf latte and waits another 24 (!) seconds before pouring it into a cup. The timing is exactly how long it takes to walk to the machine from the dudes desk.

xxx: holy sh*t I'm keeping those

Credit: http://bit.ly/1jcTuTT

The bash scripts weren't bogus, you can find his scripts on the this github URL:
https://github.com/narkoz/...

Looking for a job as a deveoper be like:

Job title: car driver

Job requirements: professional skills in driving normal- and heavy-freight cars, buses and trucks, trolley buses, trams, subways, tractors, shovel diggers, contemporary light and heavy tanks currently in use by NATO countries.

Skills in rally and extreme driving are obligatory!
Formula-1 driving experience is a plus.

Knowledge and experience in repairing of piston and rotor/Wankel engines, automatic and manual transmissions, ignition systems, board computer, ABS, ABD, GPS and car-audio systems by world-known manufacturers - obligatory!

Experience with car-painting and tinsmith tasks is a plus.

The applicants must have certificates by BMW, General Motors and Bosch, but not older than two years.

Compensation: $15-$20/hour, depends on the interview result.

Education requirements: Bachelor's Degree of Engineering.

!rant

After over 20 years as a Software Engineer, Architect, and Manager, I want to pass along some unsolicited advice to junior developers either because I grew through it, or I've had to deal with developers who behaved poorly:

1) Your ego will hurt you FAR more than your junior coding skills. Nobody expects you to be the best early in your career, so don't act like you are.

2) Working independently is a must. It's okay to ask questions, but ask sparingly. Remember, mid and senior level guys need to focus just as much as you do, so before interrupting them, exhaust your resources (Google, Stack Overflow, books, etc..)

3) Working code != good code. You are an author. Write your code so that it can be read. Accept criticism that may seem trivial such as renaming a variable or method. If someone is suggesting it, it's because they didn't know what it did without further investigation.

4) Ask for peer reviews and LISTEN to the critique. Even after 20+ years, I send my code to more junior developers and often get good corrections sent back. (remember the ego thing from tip #1?) Even if they have no critiques for me, sometimes they will see a technique I used and learn from that. Peer reviews are win-win-win.

5) When in doubt, do NOT BS your way out. Refer to someone who knows, or offer to get back to them. Often times, persons other than engineers will take what you said as gospel. If that later turns out to be wrong, a bunch of people will have to get involved to clean up the expectations.

6) Slow down in order to speed up. Always start a task by thinking about the very high level use cases, then slowly work through your logic to achieve that. Rushing to complete, even for senior engineers, usually means less-than-ideal code that somebody will have to maintain.

7) Write documentation, always! Even if your company doesn't take documentation seriously, other engineers will remember how well documented your code is, and they will appreciate you for it/think of you next time that sweet job opens up.

8) Good code is important, but good impressions are better. I have code that is the most embarrassing crap ever still in production to this day. People don't think of me as "that shitty developer who wrote that ugly ass code that one time a decade ago," They think of me as "that developer who was fun to work with and busted his ass." Because of that, I've never been unemployed for more than a day. It's critical to have a good network and good references.

9) Don't shy away from the unknown. It's easy to hope somebody else picks up that task that you don't understand, but you wont learn it if they do. The daunting, unknown tasks are the most rewarding to complete (and trust me, other devs will notice.)

10) Learning is up to you. I can't tell you the number of engineers I passed on hiring because their answer to what they know about PHP7 was: "Nothing. I haven't learned it yet because my current company is still using PHP5." This is YOUR craft. It's not up to your employer to keep you relevant in the job market, it's up to YOU. You don't always need to be a pro at the latest and greatest, but at least read the changelog. Stay abreast of current technology, security threats, etc...

These are just a few quick tips from my experience. Others may chime in with theirs, and some may dispute mine. I wish you all fruitful careers!

Today we'll refactor the API.
Tomorrow we'll celebrate.

My Future Self need never know how bad it once was.

git commit -m "quickfix"

How harmful can it be?

!Rant

Didn't have something to do tonight, and I was kind of thinking to make a multicore brainfuckversion for a while, so tonight I implemented it. I call it multiFuck:
https://github.com/papierbouwer/...