Something is incorrect.

The rant starts here

Don't tell them to run "rm -rf /" as root. That's too nice. There might be inodes left on the hard drive.

MAKE IT WORSE:

"cat /dev/zero > /dev/sda" as root.

LEAVE NOTHING.

Me: Let's grab something for dinner!
GF: Sure, but let's go somewhere safe
Me:

!Rant

The Collab idea sounds awesome! Can't wait to see it implemented.

True...

The week before project deadline...

"sudo !!" Will rerun your last command with sudo privileges in a Linux environment.

You're welcome.

CSS can kill you!

Childhood ruined

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

Here's a funny joke

A man walks into a bar and asks for a beer. The bartender says "okay but only if you tell me a meta joke". So the man says a man walks into a bar and asks for a beer. The bartender says "okay but only if you tell me a meta joke". So the man says  man walks into a bar and asks for a beer. The bartender gives him a beer. The bartender gives him a beer. The bartender gives him a beer.

This is going to be interesting.

I don't know who, or where you are. But want to let you know the test was successful.

One of the many joys in a programmers life

What only relying on JavaScript for HTML form input validation looks like

Tonight, I had the pleasure of being challenged to make a virus for a VM over at the awesome "virus aquarium": computernewb.com

I present to you the Eevee fork/bomb.
Tonight, was the first night where I've ever sat down and programmed in VBS. I had a lot of fun doing it too. Right now I'm aiming at corrupting taskkill, tskill, and shutdown for good measure. These are a few of the things that my buddy has pulled on me that has made it difficult for me to continue moving forward.

The other part is to create seperate .exe files that would run my the necessary script. Each of these .exe files will be unique such that it's more difficult to shut all of them down at once.

Despite the fact that this thing will quite literally break your computer, it's fun being challenged to think outside of the box. Quite literally. I've always been careful about what things I touched on a PC, but tonight was fun because I was basically unchained and allowed to run rampant.

As a computer geek I think it's good to let out your inner demon and see what havoc one could wreak.

Question: Does using cookies for user session handling hinder the scalability of your backend because all the API's have to live on the same domain. Basically if one API starts to get a lot of request and you want to add another server to off balance the load you would have to add an entire webserver rather than just a small micro webserver with the API running on it mainly because cookies are used to authenticate user request and cookies don't survive CORS request. Am I right or don't know what the hell i'm talking about lol need some opinions I suggested we make all API's micro services and use JWT for user sessions

So there was an inspection from government for our bank's IT security. I gave a tour to our server and security systems. I threw all possible acronyms as much as I could remember. Inspector nodded and noted down never uttered a word.

Finally, he breaks his silence, looking at a device he points out and says "What's that ?"

I look at the device then stare at his face back again at the device and to his face I reply "That's AC, Air Conditioner".