This is how I feel after working, almost exclusively, with PHP over the last 4 years.

I'm going to get message from the NSA for posting this. 😂😂

!rant
Thanks to whoever said you can get a student license for jetbrains products! Just got mine approved today!

I swear I work with mentally deranged lunatics.
Dev is/was using TFS's web api to read some config stuff..

Ralph: "Ugh..this is driving me crazy. I've spent all day trying to read this string from TFS and it is not working"
Me: "Um, reading a string from an web api is pretty easy, what's the problem?"
Ralph: "I'm executing the call in a 'using' statement and cannot return the stream."
Me: "Why do you need to return a stream? Return the object you are looking for."
Ralph: "Its not that easy. You can return anything from TFS. All you get back is a stream. Could be XML, JSON, text file, image, anything."
Me: "What are you trying to return?"
Ralph: "XML config. If I use XDoc, the stream works fine, but when I step into each byte from the stream, I the first three bytes have weird characters. I shouldn't have to skip the first three bytes to get the data. I spent maybe 5 hours yesterday digging around the .Net stream readers used in XDoc trying to figure out how it skips the first few bytes."
Me: "Wow...I would have used XDoc and been done and not worried about that other junk."
Ralph: "But I don't know the stream is XML. That's what I need to figure out."
Me: "What is there to figure out? You do know. Its your request. You are requesting a XML config."
Ralph: "No, the request can be anything. What if Sam requests an image? XDoc isn't going to work."
Me: "Is that a use-case? Sam requesting an image?"
Ralph: "Uh..I don't know...he could"
Me: "Sounds like your spending a lot of time doing premature optimization. You know what your accessing TFS for, if it's XML, return XML. If it's an image, return an image. Something new comes along, modify the code to handle it. Eazy peezy."
<boss walks in from a meeting>
Boss: "Whats up guys?"
Ralph: "You know the problem with TFS and not being able to stream the data I had all day yesterday? I finally figured it out. I need to keep this TFS reader simple. I'll start with the XML configs and if we more readers later, we can add them."
Boss: "Oh yea, always start simple and add complexity only when you need it."

Frack...Frack..Frack...you played some victim complaining to anyone who would listen yesterday (which I mostly ignored) about reading data from TFS was this monumental problem no one could solve, then you start complaining to me, I don't fall for the BS, then tell the boss the solution was your idea?

Lunatic or genius? Wally would be proud.

I think I laught too much about this!

A bug a day keeps ego away.

*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/...

well, how about that ._.

When you have something in your clipboard but then press Ctrl+C instead of Ctrl+V and end up with a blank line.

I just spent 5 minutes trying to fix an error saying that I am missing a ";".

I saw a ; at the end of statement but I kept on getting the error.

After cleaning the monitor the ; disappeared and I was able to see the problem.

Clean your monitor once in a while.

And the most useless function of the year award goes to...

Wife: You never listen to me!
Me: Have you tried port 8080?

Skype emoticon button is sad when you use comic sans as font on windows.

Is it just me or am I the only one who gets pissed if someone checks the expected result of a variable first?

For example:
if(true === $var)

Instead of:
if($var === true)

Dropbox as version controll.

Just released the side project that made me join programming! :) It's been about five months and I learned a lot: PHP, JavaScript, CSS, Handlebars, Jquery, Git (terminal), I even started building a RestAPI. Its been an amazing journey, and I didn't alone! I met other Devs (now good friends) over the Internet and we did it together :) Thanks to everyone on DevRant for being such a great community!
If you want to take a look at the site is: projectgroupie.com
It's a website to find new projects you like and join them! So if you're a developer and you wanna make a blog, you post your project on PG asking for some designer to help you and if someone like it, he can join! :)

I hope you enjoy it and any feedback is welcome!

Here's my piece of advice for new devs out there:

1 - Pick one language to learn first and stick with it, untill you grasp some solid fundamentals. (Variables, functions, classes, namespaces, scope, at least)

2 - Pick an IDE, and stick with it for now. Don't worry about tools yet. Comment everything you're coding. The important thing is to comment why you wrote it, and not what it does. Research git and start using version control, even when coding by yourself alone.

3 - Practice, pratice and pratice. If you got stuck, try reading the language docs first and see if you can figure it out yourself. If all else fails, then go to google and stackoverflow. Avoid copying the solution, type it all and try to understand it.

4 - After you feel you need to go to the next level, research best practices first, and start to apply them to your code. Try to make it modular as it grows. Then learn about tools, preprocessors and frameworks.

5 - Always keep studying. Never give up. We all feel that we have no idea of what we are doing sometimes. That's normal. You will understand eventually. ALWAYS KEEP STUDYING.

Someone apparently broke the spam bot

!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!

This makes me consider changing career paths.

Best part of being a dev? Being paid to fix problems in the code you created yourself.

Every programmers dream convo

Creepy..... WTF

My girlfriend dumped me after I named a class after her. She felt I treated her like an object.

When a hiring manager wants 5+ years experience in Swift.

Swift release date = June 2, 2014

😂👍🖕

I'm new here and this is my very 0th rant.

I'm almost 29 and only have finished high school. I never new what I wanted to do until 7 years ago. Software engineering and development.

It took me a little while an some effort to find a employer who sees my potentials and is willing to invest in me.

Two weeks ago I decided to finally go back to school again (self study). Last week my boss told me he is proud and willing to share the costs.
Today my books arrived.

I am so excited and nervous!! November 5th (also my birthday) will be the first day of school.

Facebook.leave();
devRant.join();
console.log("Hello world");

A trusted-partner of my company obviously opened a dodgy email, as some of my co-workers got emails with a dodgy link from them....

So our Network Admin sent an email to the entire company with a screenshot of the email and a message along the lines of "DO NOT CLICK THE LINK IF YOU'VE RECEIVED THE ORIGINAL EMAIL!"

Company director REPLIES TO ALL and says 'i cant click the link that you sent to us'.
N.A replies directly to him to say its only a screenshot as it could spread a virus.

Director then informs N.A that that he has found the original mail (hurrah!) but the link downloaded an empty .zip file, so he forwarded the file to another director... who also couldn't open.... so they forwarded it to another person who also couldn't open it..... and they in turn forwarded it etc etc.

Currently have 37 power scans running (out of 250 computers) and trying to figure out how the hell these people manage to dress themselves every morning.

Today while i was working on my web project, suddenly my boss put his hands in my pants, jerked me off and then i continued my work like nothing ever happened.

Being your own boss has its own advantages ;)