(Note: I got a bit carried away while writing this, so the end result is a lot longer than I expected. Apologies for the long post!)

The beginning of my programming journey started with a book.

This was back in 7th grade. I had some basic exposure to BASIC (pun maybe intended?) from our school curriculum, but it was nothing too interesting as our teachers never really treated it as anything important. They would stress a lot on those Microsoft Office chapters (yes, we actually studied Microsoft Office as part of our computer science course at school) and mostly ignore the programming chapters because I dare say many of them struggled with it themselves. So although I had been exposed to *some* programming, it was mostly memorizing the syntax without actually understanding what was going on.

Then one day there was this book fair thing going on at this local Carrefour (for those of you who've no idea, it's a pretty famous hypermarket chain) in this mall, and for some reason my mother and I were in that mall on that day. Now the interesting thing is that this usually never happens -- I usually visit malls with my dad or my friends, this is the only instance I remember where I had actually visited one with just my mom. This turned out to be fortuitous. My father is the kind of person who's generally not amenable to any kind of extraneous shopping requests. My mother, on the other hand, was and remains pliable.

So I basically saw this book -- Sams' Teach Yourself JavaScript in 24 Hours -- being sold at half price. I vaguely remembered having read somewhere that JavaScript is a good introductory programming language (and it helped that this was the time when I was getting into a Google-craze -- I basically saw some photos of Google Zurich and went all HOLY SHIT THAT'S WHERE I NEED TO WORK WHEN I GROW UP (for those of you who haven't seen it, I recommend googling it. That office is the bomb) -- and I'd also read that you need programming skills to join Google). So I begged and begged my mum to buy that book, and thankfully she did.

Back home I returned with my new prize under my arm. Dad took one look at it and scoffed that I'll never actually use it. Pretty much entirely out of spite (to prove him wrong), I attacked the book with a zeal. I still remember how I felt when I wrote my very first JavaScript program (printing the current system date in an h1 tag) and marveling at the output. I guess that was when something struck -- the realization that this was probably what I wanted to do in life.

Fast forward to today, and I've never looked back and wondered what it would be like to have done something else.

PS: for all you beginners out there, JavaScript is a horrible language. Please start with something like Python. Also there are better resources than Sams' Teach Yourself JavaScript in 24 Hours available, that I just didn't know of back then. I'd recommend Eloquent JavaScript any day.

"Hey baby, there's an OverflowException in my pants, care to handle it for me?"

I was 11 or 12 years old, my dad had this policy that only *nix machines are allowed in our home, so I was rocking a Ubuntu pc at that time. I was messing around with it and tweaking some things here and there, but wanted to learn more. My dad showed me how to open python on the command line and gave me some simple tasks to do. Been hooked ever since.

PS. Still going by the same policy, even though I live on my own.

I came to my sister's husband, programmer, and asked him for a book to learn how to program. He gave me a giant tome (probably to scare me out) and I read it page by page doing all the tasks. For me it was like a magic, I couldn't believe that I can write something in the notepad and then see computer do stuff because I told it to do so.

"The server is flooded!"

"With requests? DDoS?"

"No."

CSS can kill you!

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

So this happened last night...

Gf: my favorite bra is not fitting me anymore
Me: get a new one ?
Gf: but it is a C already.
Me: get a c++.

After 5 sec i bursted in laughter, she was confused.

How did I start:

It was 1994. I had been kicked out of school on academic behavior. I was working at as a telemarketer to pay the bills. I got drunk on St. Patrick's day and over slept my shift. My boss was going to fire me but said he wanted to give me a second chance. He asked if I knew anything about computers. I said no. He said if I was willing to learn, our IT guy was burning out and needed help. I said ok. Next thing I know I'm learning how to write SQL and importing data to print call cards. I read the manual for Foxpro and started building small desktop apps as labor saving devices. 6months later in knew more than our IT guy. Later a friend showed me "the Internet". I went back to our IT guy in amazement. He said it was just a fad. He called it the CB Radio of the 90s. Our network we ran was called Lantastic.

I immediately quit went back to school and changed my major. I have been a full stack Java Web developer will the heavy emphasis on UI since 1999.

I have a pen...

I have a paper...

Uh!

...programming!

Guys try installing Termux. Its Linux for Android. It comes with its own version of Apt package manager. Using this opens up alot of possibilities ;)

😂😂😂😂😂

Don't you just hate it when you are writing up a report and this happens.. ugh,the frustration!

My teacher shouted at me - "Go to hell".
What really hurt me was 'goto'.

Creepy..... WTF

You know you have too many tabs open when chrome looks like a mountain range.

I was dressed up as an UDP packet for the Halloween. I don’t think anyone got it, but I couldn’t tell. #humour

Have a great Halloween :)

using my local provider

Just for fun, a home made comic.

Programmers of today are like the monks of the middle ages. We use a language that people don't understand, we spend all our time sitting in a room reading, and people constantly ask us for advice but never really listens to the answer.

Fav function is printf() in C.
Because sometimes, it's the best debugger.

Those naughty monkeys

Today it's my birthday. Yesterday I was woken by my fiancé with breakfast and one gift. She had bought me the Raspberry Pi 3 B.
Now she had decided to give it to me on the Sunday so I could play with it right away instead of having to go to work and wait a whole week before I would have time play.

I Love You, Honey! More than you realize <3

*opening cmd*
"wow, are you Hacking?"
me: "yah, sure. See that lamp? I can hack that."
"really?"
me: "sure".
*lamp flickers"
me: "I did that" 😂

So this is where my bus is heading...

Stop f*cking calling me minority or part of a underrepresented group. Yeah I noticed I am one of the only women on a conference. I DONT CARE, I AM A PROGRAMMER NOT A SPECIAL SNOWFLAKE. Hire me for my work, not because you want you company to be more diverse.

Code as a first year student..

Thanks for the reality check google :(

When you find out your office's bathroom is really active on Github (yep that's my beard and yep I'm a tall guy)

Kindly asking for help