I’m so stupid for not starting a Youtube channel or buying Bitcoin.

CC - Code Credit 🤣😜

Do you wanna be a software engineer at Google?

Go to AlgoExpert.io. Pick a question. Read the prompt. Write some code…

JUST FUCKING STOP

Fucking shitty ad popping up every time I watch anything even remotely related to tech or science.

Me: Codes a really cool website animation in javascript for 2 days.

*Opens youtube, random tutorial for the same animation in CSS in 30 min.*

Me: * Cries in the corner. T-T *

I have found the ugliest company logo in existence.

My CSS — flawless

Your CSS:

True shit...

I uh.. use arch

#truth

Imagine this in virtual meetings 😁

It's painful.

My brain at 5:00 AM

Read the error message before closing it and/or asking for help.

There's no such thing as an expert programmer. With time you just get different kinda errors. As long as you're not getting same error, you're making progress.

1. You don't code to add a feature or whatever. You do it to solve Users' problems. It's a User-centric system.
2. You read more code than you write. So help yourself and write code intended to be read.
3. If people don't know you did something, you did nothing!
4. Never answer a call at 3 am if you're not paid to be on night call-duty. You'll become the guy who answers at 3 am.
5. Remember the big difference between you and me is that I failed to do stuff more times than you have tried to do.
6. When you start shaving the yak, stop!

Juniors are a fun bunch to work with.
Over confident, hero complex of that fresh graduate high, and then thrown in to the real world! Where there hopes and dreams are crushed in minutes when they see what monolithic applications really look like!!

But don't let that overwhelm you, your not going to be changing all of it any time soon, hell some of this code hasn't been touched in 5+ years and still works without fail.

Don't stress about the work load, you can only write 1 line of code at a time anyway, and hell, even seniors make mistakes.

The key about being able to manage this beast is simple, break it! Because the more you break it, the more you'll understand how a project is put together, for better or worse. Learn from the examples in front of you, and learn what not to do in the future 😎

But more importantly, plan your changes, whiteboard the high level logic of what it is you want to add, then whiteboard in the current codebase and determine where to slice this bitch up, then when it all looks well and good, take out your scalpel and slice and dice time.
Don't worry, your changes aren't going to production anytime soon, hell, you'll be lucky to get past the first pull request with this working 100% the first time, and that's a good thing, learn from tour short comings and improve your own knowledge for the next time!

Don’t work here.

- There are no stupid questions. Please feel free to ask.
- You don't have to memorize, but try to understand.
- Document so you never have to remember.
- Teach so you will master and never forget.
- Even if we have different responsibilities do not ping pong issues because overall the client only sees one company name so we work as one.
- Do not disturb while on vacation leave unless it's life or death.
- Relax, sleep and have a happy weekend.

Don’t write documentation for other people, write it for yourself! It may all seem obvious today, but six weeks from now you’re not going to remember what you were thinking or why you wrote the code the way you did.

* KISS (keep it super simple)
* don’t try solve a problem you don’t already have
* admit if you messed up. We can solve a problem early and minimise the damage. People should never be scared to admit when they mess up. No one is perfect.
* voice your opinion. You’d be surprised how helpful this can be to your team, as we need to look at things from all angles.
* help your team. If you see something wrong, make the team aware of it.
* ask if unsure, don’t assume

Comment your code, you'll thank me for that next week.

Reinvent the wheel, then throw it away.
Best way to understand a concept

Happy Halloween :)

Just used a laptop without an SSD. I almost died.

I found that being a (good) software engineer and a girl is such an effective way to piss off a lot of people. I could never pass on an opportunity like that.

I was told there's gonna be:
- good salaries
- informal company setups with benefits
- lots of jobs available
- non-dev people look at you in amazement
- get to work on really interesting stuff

What I'm actually doing:
- carrying a team of people in uni because you're the only one who knows how to code
- deal with shitty uncommented legacy code at work
- be reminded that if you don't do something super-sophisticated you're easily replaceable
- spend unpaid overtime hours because you're the only one at your job that is on the issue (I see a pattern of being alone in a problem here)
- requestion all my career decisions
- cry and be stressed
- hate every minute of work, yet be stuck in it because it's a source of income that is flexible enough for me to be able to study full-time

So dunno man, I'm still waiting on what I've been told, people say there's lotsa money and satisfaction waiting for me after grinding through 5 years of high education, it'd better be worth it

ctrl+z has saved everyone's lives at least once I guess

Dark theme enabled calculator

The face they make when they find out that instead of

a,
b,
c

I go

a
,b
,c

Totally worth it.

Me: Why isn't this working?!
Normal languages: You screwed up over here.
Me: oh thanks

Me: Why isn't this working?
Javascript: 🙂
Me: Please I beg you tell me.
Javascript: 🙂