Oh hello baby

Is it possible that nearly every Coder/Programmer has some kind of social anxiety? 😂

Everyday i used to spend an hour in the morning reading emails.

Until i made a script that reads all mails, parses to urgent/priorities/meetings etc. Then shows me a dashboard of everything. 1 hr turned to 20mins max.

Then i made a chatbot out of it and now i just talk to it everytime and gives me the rundown.

Gave me so much time to code instead of reading fucking emails.

Probably the biggest one in my life.
TL:DR at the bottom

A client wanted to create an online retirement calculator, sounds easy enough , i said sure.

Few days later i get an email with an excel file saying the online version has to work exactly like this and they're on a tight deadline

Having a little experience with excel, i thought eh, what could possibly go wrong, if anything i can take off the calculations from the excel file

I WAS WRONG !!!
17 Sheets, Linking each other, Passing data to each sheet to make the calculation
( Sure they had lot of stuff to calculate, like age, gender, financial group etc etc )

First thing i said to my self was, WHAT THE FREAKING FUCK IS THIS ?, WHAT YEAR IS THIS ?

After messing with it for couple of hours just to get one calculation out of it, i gave up

Thought about making a mysql database with the cell data and making the calculations, but NOOOO.
Whoever made it decided to put each cell a excel calculation ( so even if i manage to get it into a database and recode all the calculations it would be wayyy pass the deadline )

Then i had an epiphany

"What if i could just parse the excel file and get the data ?"
Did a bit of research sure enough there's a php project
( But i think it was outdated and takes about 15-25 seconds to parse, and makes a copy of the original file )

But this seemed like the best option at the time.
So downloaded the library, finished the whole thing, wrote a cron job to delete temporary files, and added a loading spinner for that delay, so people know something is happening
( and had few days to spare )

Sent the demo link to client, they were very happy with it, cause it worked same as their cute little excel file and gave the same result,

It's been live on their website for almost a year now, lot of submissions, no complains
I was feeling bit guilty just after finishing it, cause i could've done better, but not anymore

Sorry for making it so long, to understand the whole thing, you need to know the full story

TL:DR - Replicated the functionality of a 17 sheet excel calculator in php hack-ishly.

I JUST DELETED MY LIVE MYSQL SERVER

I DON'T KNOW IF WE HAVE BACKUPS

Epoch Post *I'll walk myself out*

Put it on a poster:

"It's ok to:

say "I don't know"
ask for more clarity
stay at home when you feel ill
say you don't understand
ask what acronyms stand for
ask why, and why not
forget things
introduce yourself
depend on the team
ask for help
not know everything
have quiet days
have loud days,
to talk,
joke and laugh
put your headphones on
say "No" when you're too busy
make mistakes
sing
sigh
not check your email out of hours
not check your email constantly during hours
just Slack it
walk over and ask someone face-to-face
go somewhere else to concentrate
offer feedback on other people's work
challenge things you're not comfortable with
say yes when anyone does a coffee run
prefer tea
snack
have a messy desk
have a tidy desk
work how you like to work
ask the management to fix it
have off-days
have days off

(From UK Government Digital Service: https://gds.blog.gov.uk/2016/05/...)

Tools don't matter. Use what is comfortable and don't listen to all the brand, OS, editor and tabs/spaces crap. They all do the job and you will find the right ones once you really understand what you are doing. "Tools can be just a way to procrastinate". If you become tool agnostic you can do the job no matter the environment.

git reset --hard 2015

When people find out the hard truth

A young guy I work with burst into tears today, I had no idea what happened so I tried to comfort him and ask what was up.

It appears his main client had gone nuts with him because they wanted him to make an internet toolbar (think Ask.com) and he politely informed them toolbars doesn't really exist anymore and it wouldn't work on things like modern browsers or mobile devices.

Being given a polite but honest opinion was obviously something the client wasn't used to and knowing the guy was a young and fairly inexperienced, they started throwing very personal insults and asking him exactly what he knows about things (a lot more than them).

So being the big, bold, handsome senior developer I am, I immediately phoned the client back and told them to either come speak to me face-to-face and apologise to him in person or we'd terminate there contract with immediate effect. They're coming down tomorrow...

So part my rant, part a rant on behalf of a young developer who did nothing wrong and was treated like shit, I think we've all been there.

We'll see how this goes! Who the hell wants a toolbar anyway?!

Programming in a nutshell

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

We've all been there.

Parent threads watching over their children ones

So true

When I accidentally exit f.lux and the whole screen becomes white

Look at how colorful that is :D

Einstein supposedly has a quote attributed to him: "Perfection isn't achieved when there is nothing left to add, but when there is nothing left to remove."

I find that I aggressively refactor code where I can to only what is absolutely required. It does also have the knock on effect of reducing scope of bugs, when the code is smaller there's only so many places bugs can be.

Tesla claimed to have the ability to create designs in his head and only built things once he was satisfied that it worked in theory first, now it's rare I can do that, but I will use a repl to prototype or test modules in isolation before just hacking on the actual code.

Jobs, I mean, I know he didn't code but he was always insisting on designs that looked good and was generally uncompromising in his design centric view.

My friend, she was my Starbucks barista for a while but I've slowly been teaching her code and she's taught me a lot about how to teach others to code, she also happens to be my favourite student.

Well done IKEA

Finally I found a webpage related to my bug.

The page is from 2004.

*keeps reading*

"Yes, yes! This is exactly the problem I'm having"

*Carefully reading each comments*

*Looking at scroll bar with stress*

*Almost coming to end, no signs of solution*

At the end the thread creator say: "Ah finally I've fixed the problem. Thanks everyone for helping"

*moment of silence*

WHY U NO SHARE THE GOD DAMN SOLUTION? YOU FUCKING IDIOT

This should be illegal!

Me: I need a Windows PC to test my code on.
Server dude: We don't have any free, but I can setup an old server for you.
Me: 🤔 .. I'll take it!

How I feel tomorrow is going to go

Wikipedia says that a nerd/geek lacks social skills. They should see this amazing community, thanks DevRant :)

Devs choosing Spaces over Tabs

Documentation

I just wrote "git vomit" instead of "git commit".

That awkward moment when your shower has a better commit streak than you.

!rant
Loving the community here I wish more people I know personally knew about DevRant hence why I just bought myself a stress ball. Hoping that someone at work might notice it!