Our programming teacher had a surgery on his left eye and will not be able to do the lessons with us. Guess what the subject of the email he sent us was.

"I can't C#."
He made a pun about his fucking health status, alright then.

I want to pay respects to my favourite teacher by far.

I turned up at university as a pretty arrogant person. This was because I had about 6 years of self-taught programming experience, and the classes started from the ansolute basics. I turned up to my first classes and everything was extremely easy. I felt like I wouldn't learn anything for at least a year.

Then, I met one of my lecturers for the first time. He was about 50~60 years old and had been programming for all of his career. He was known by everyone to be really strict and we were told by other lecturers that it could be difficult for some people to be his student.

His classes were awesome. He was friendly, but took absolutely no shit, and told everything as it was. He had great stories from his life, which he used to throw out during the more boring computer science topics. He had extremely strict rules for our programming style, and bloody good reasons for all of them. If we didn't follow a clear rule on an assignment, he'd give us 0%. To prove how well this worked, nobody got 0%.

We eventually learned that he was that way because he used to work on real-time systems for the military, where if something didn't work then people could die.

This was exactly what I needed. In around one semester I went from a capable self-taught kid, to writing code that was clear, maintainable and fast, without being hacky.

I learned so much in just that small time, and I owe it all to him. So often when I write code now I think back to his rules. Even if I disagree with some, I learned to be strict and consistent.

Sadly, during the break between our first and second year, he passed away due to illness. There was so many lessons still to be learned from him, and there's now no teachers with enough knowledge to continue his best modules like compiler writing.

He is greatly missed, I've never had greater respect for a teacher than for him.

At university we had lessons in C++.
First lesson: Make a calculator
Second lesson: Make an application that uses sockets to connect to an FTP-server and downloads a file. No FTP-libraries allowed.

I'm at my seat during the regular morning routine of checking emails, planning the things I need to complete/study when my phone rings.

HR: Good Morning, can you come over to the conference room please ?

Me: Sure

I enter the conference room and on the other side of the table, I see a group of 3 HR Managers (not a very nice feeling), especially when it was 10 months into my first job as a Trainee Software Developer.

HR: The company hasn't been performing as expected. For this reason, we've been told to cut down our staff. We're sorry but we have to let you go. You've been doing a great job all along. Thank you.

Me: ---- (seriously ?!)

The security-in-chief 'escorts' me out of the premises and I hand over the badge. I'm not allowed to return to my desk.

This happened about 16 years ago. But it stuck with me throughout my programming career.

A couple of Lessons Learnt which may help some of the developers today :

- You're not as important as you think, no matter what you do and how well you do it.
- Working hard is one thing, working smart is another. You'll understand the difference when your appraisals comes around each year.
- Focus on your work but always keep an eye on your company's health.
- Be patient with your Manager; if you're having a rough time, its likely he/she is suffering more.
- Programming solo is great fun. However it takes other skills that are not so interesting, to earn a living.
- You may think the Clients sounds stupid, talks silly and demands the stars; ever wonder what they think about you.
- When faced with a tough problem, try to 'fix' the Client first, then look for a solution.
- If you hate making code changes, don't curse the Client or your Manager - we coders collectively created a world of infinite possibilities. No point blaming them.
- Sharing your ideas matter.
- Software Development is a really long chain of ever-growing links that you may grok rather late in your career. But its still worth all the effort if you enjoy it.

I like to think of programming as a pursuit that combines mathematical precision and artistic randomness to create some pretty amazing stuff.

Thanks for reading.

Life lessons..

I turned 40 yesterday. Here are some lessons I've learned, without fluff or BS.

1) Stop waiting for exceptional things to just happen. They rarely do, and they can't be counted on. Greatness is cultivated; it's a gradual process and it won't come without effort.

2) Jealousy is a monster that destroys everything in it's path. It's absolutely useless, except to remind us there's a better way. We can't always control how we feel, but we can choose how we react to those feelings.

When I was younger, jealousy in relationships always led to shit turning out worse than it probably would have otherwise. Even when it was justified, even when a relationship was over, jealousy led me to burn bridges that I wished I hadn't.

3) College isn't for everyone, but you'll rarely be put square in the middle of so much potential experience. You'll meet people you probably wouldn't have otherwise, and as you eventually pursue your major, you'll get to know people who share your passions and dreams. Despite all the bullshit ways in which college sucks, it's still a pretty unique path on the way to adulthood. But on that note...

4) Learn to manage your money. It's way too easy to get into unsustainable debt. It only gets worse, and it makes everything harder. We don't always see the consequence of credit cards and loans when we're young, because the future seems so distant and undecided. But that debt isn't going anywhere... Try not to borrow money that you can't imagine yourself paying back now.

5) Floss every day, not just a couple times per week when you remember, or when you've got something stuck in your teeth. It matters, even if you're in your 20s and you've never had a cavity.

6) You'll always hear about living in the moment, seizing the day... It's tough to actually do. But there's something to be said for looking inward, and trying to recognize when too much of our attention is focused elsewhere. Constantly serving the future won't always pay off, at least not in the ways we think it will when we're young.

This sentiment doesn't have much value when it's put in abstract, existential terms, like it usually is. The best you can do is try to be aware of your own willingness and ability to be open to experiences. Think about ways in which you might be rejecting the here and now, even if it's as seemingly-benign as not going out with some friends because you just saw them, or you already went to that place they're going to. We won't recognize the good old days for what they were until they're already gone. The trick is having as many good days as possible.

7) Don't start smoking; you'll never quit as soon as you'll think you can. If you do start, make yourself quit after a couple years, no matter what. Keep your vices in check; drugs and alcohol in moderation. Use condoms, use birth control.

8) Don't make love wait. Tell your friends and family you love them often, and show them when you can. You're going to lose people, so it's important. Statistically, some of you will die young, yourselves.

When it comes to relationships, don't settle if you can't tell yourself you're in love, and totally believe it. Don't let complacency and familiarity get in the way of pursuing love. Don't be afraid to end relationships because they're comfortable, or because you've already invested so much into them.

Being young is a gift, and it won't last forever. You need to use that gift to experience all the love that you can, at least as a means to finding the person you really want to grow old with, if that's what you want. Regardless, you don't want to miss out on loving someone, and being loved, because of fear. Don't be reckless; just be honest with yourself.

9) Take care of your body. Neglecting it makes everything tougher. That doesn't mean you have to work out every day and eat like a nutritionist, but if you're overweight or you have health issues, do what you can to fix it. Losing weight isn't easy, but it's not as hard as people make it out to be. And it's one of the most important things you can do to invest in a healthy adulthood.

Don't put off nagging health issues because you think you'll be fine, or you don't think you'll be able to afford it, or you're scared of the outcome. There will always be options, until there aren't. Most people never get to the no-options part. Or, they get there because all the other options expired.

10) Few things will haunt you like regret. Making the wrong choice, for example, usually won't hurt as much. I guess you can regret making the wrong choice, but my deepest regrets come from inaction, complacency and indifference.

So how can we avoid regret? I don't know, lol. I don't think it's as simple as just commiting to choices... Choosing to do nothing is still a choice, after all. I think it's more about listening to your gut, as cliche as that sounds.

To thine own self be true, I guess. It's worth a shot, even if you fail. Almost anything is better than regret.

My programming teacher is a freaking degenerate. He spend 7 months teaching us basic stuff like if-clauses, while-loops and stuff like that over and over again - everyone was annoyed but he didn't listen to us because "some people still don't get it". (The reason for this could be their total absence during lessons but who am I to tell.)
Beginning of 2018 he realised we hadn't much time left to prepare for our final exam so he tried self-taught learning. 8 sorting algorithms, recursion, how to write classes and objects in less than a week. And of course there was a classtest about this - needless to say that like nobody passed it. He still has no clue why we are "so lazy and dumb".
One of his favourite code examples is a calculator. I don't know how many i've programmed and they've gotten more and more ridiculous. (Who the hell would want interfaces like IComparer in a calculator?)
He even wanted to convince us that for-loops can't count down (and that things like "i--" doen't exist.)
I could go on and on about this guy and his craziness.

Employee of a customer of my company asked if anyone was available for evening lessons of the basics if linux for his son because he needs this to go to the next year.

I'm going to teach the kid the basics tomorrow for as far as possible and will be paid as well 😊

Assembly: He’s the nerd. He speaks very quickly and uses short sentences. Very few people talk to him. He’s considered to be an autist asperger by a majority of the class because he finishes the exams so quickly it’s insane and he faces a lot of difficulties in speaking with others. He’s at school but already dressed like an engineer.

Ada: She’s a foureyes nerd. When she gets the answer she’s doesn’t make any mistake. Ada often corrects the teacher when she writes a line a little ambiguous. She’s building a rocketship in her backyard and she’s always speaking about this weird hobby.

Python: He’s Mr Popular. He likes skate, brags about all the parties he’s invited to. He’s good in all the subjects taught in class but he’ll do them a bit slower than the others. Everyone loves him because he explainsthings so well, sometimes the teacher herself asks Python to explain some part of the course. He’s dressed with a hoodie, a baggy and glasses on the top of the head ;)

Java: She is one of the toppers of the class and very popular. She’s very good in all the topics. The teacher loves her but she’s a very talkative person.

Scala/Kotlin: They are twin sisters and the best friends of Java. Unfortunately, they are not as popular and it’s often Java who takes the lead in the group. It’s very difficult to distinguish one from another. Both are far less talkative than Java but Scala speaks a bit differently than Kotlin and Java.

C: He’s the topper of the class. He’s so fast in completing the exams that the teacher really thinks he’s copying Assembly’s work. He has a little brother C++ and they share a lot in common together. He’s the chess major and often plays chess with Assembly and his big brother.

Go: He’s the new kid on the bloc. He doesn’t like C++ and his friends and he wants to prove he can do better than them. Of course, he prefers playing Go over Chess.

APL: He’s a lonely guy. No one understands him when he speaks. Even the teacher is surprised when APL shows a correct answer after several lines of incomprehensible pictograms. People think that he was born in a foreign country… or a foreign planet ?

HTML/CSS: These twin brothers are very different. One is dressed in black and white and the other is dressed with everything except black and white. HTML is very talkative and annoying and the CSS is very artistic. CSS is the best student in Art lessons and HTML performs well in written expression.

LaTeX: She’s friend of HTML. The teacher likes her because she has a gift of writing. LaTeX likes the mathematical courses because she can draw fancy greek letters. The teacher knows this well and she is often asked to write a formula on the black board.

VBA: He’s in the back, looking through the windows. Not really interested in the courses taught in class. In the exams, he answers always with a table.

C#: He’s in the back playing yet another game on his smartphone. He likes being next to the windows also.

JavaScript: People often mix up Java and JavaScript because they have a similar name. But they are definitly not the same. Javascript spends a lot of time with HTMLand CSS. He’s as artistic as CSS but he prefers things that move. He likes actions and movies. CSS dreams to be a painter wheras JavaScript wants to be a film-maker.

Haskell: He’s a goth. Dressed up in dark. Doesn’t talk to anyone. He doesn’t understand why others write pages when he can write a couple of lines to answer the same question.

Julia: She’s the newest student here. She doesn’t have any friends yet but her secret aim is to be as popular as Python and as fast as C.

Credit: Thomas jalabert

HE:"Hey I improved my code"

ME:
*opens the file*
*Sees random static allocations*
*Code is as verbose as before*
*Down to 2600 lines from 2800ish*
*Still doesn't do shit properly*

"Uuuh what exactly did you do?"

*Starts noticing the lack of namespaces*

HE: "I used this using namespace std to write a bit less"

ME: "Can I pay you yoga lessons so you can taste your own cock and show your parents how good you are at it?"

It's maddening how few people working with the internet don't know anything about the protocols that make it work. Web work, especially, I spend far too much time explaining how status codes, methods, content-types etc work, how they're used and basic fundamental shit about how to do the job of someone building internet applications and consumable services.

The following has played out at more than one company:

App: "Hey api, I need some data"
API: "200 (plain text response message, content-type application/json, 'internal server error')"
App: *blows the fuck up

*msg service team*

Me: "Getting a 200 with a plaintext response containing an internal server exception"
Team: "Yeah, what's the problem?"
Me: "...200 means success, the message suggests 500. Either way, it should be one of the error codes. We use the status code to determine how the application processes the request. What do the logs say?"
Team: "Log says that the user wasn't signed in. Can you not read the response message and make a decision?"
Me: "That status for that is 401. And no, that would require us to know every message you have verbatim, in this case, it doesn't even deserialize and causes an exception because it's not actually json."
Team: "Why 401?"
Me: "It's the code for unauthorized. It tells us to redirect the user to the sign in experience"
Team: "We can't authorize until the user signs in"
Me: *angermatopoeia* "Just, trust me. If a user isn't logged in, return 401, if they don't have permissions you send 403"
Team: *googles SO* "Internet says we can use 500"
Me: "That's server error, it says something blew up with an unhandled exception on your end. You've already established it was an auth issue in the logs."
Team: "But there's an error, why doesn't that work?"
Me: "It's generic. It's like me messaging you and saying, "your service is broken". It doesn't give us any insight into what went wrong or *how* we should attempt to troubleshoot the error or where it occurred. You already know what's wrong, so just tell me with the status code."
Team: "But it's ok, right, 500? It's an error?"
Me: "It puts all the troubleshooting responsibility on your consumer to investigate the error at every level. A precise error code could potentially prevent us from bothering you at all."
Team: "How so?"
Me: "Send 401, we know that it's a login issue, 403, something is wrong with the request, 404 we're hitting an endpoint that doesn't exist, 503 we know that the service can't be reached for some reason, 504 means the service exists, but timed out at the gateway or service. In the worst case we're able to triage who needs to be involved to solve the issue, make sense?"
Team: "Oh, sounds cool, so how do we do that?"
Me: "That's down to your technology, your team will need to implement it. Most frameworks handle it out of the box for many cases."
Team: "Ah, ok. We'll send a 500, that sound easiest"
Me: *..l.. -__- ..l..* "Ok, let's get into the other 5 problems with this situation..."

Moral of the story: If this is you: learn the protocol you're utilizing, provide metadata, and stop treating your customers like shit.

One of the important lessons I learnt in DevRant.

"You don't choose the free stress ball, the stress ball chooses you."

Going to have to do multiple rants on this one as I've had three awesome teachers.

Number one: Linux teacher.

He was around his 40's to mid 40's I think and he loved talking to people who also had the same passion (linux) about it.

When we had Linux classes which everyone hated, he'd always let me free. He knew I'd be able to finish the 10 weeks' assignments within an hour or so (took me half an hour instead of 10 lessons) so he just said: go do whatever you want.

Aaaaand instead of doing my own thing I ended up saving the whole class.

Yeah he was a very open minded guy who was awesome with linux/the students.

Last teacher rant from me and this one is about: my mentor.

Let's call him Bob.

He was a person who'd always be ready to help you out, did some lessons on bullying and the effects of it, stood by me many times when I'd have hard times with something I'd trouble and one of the most important things, he had a very good sense of humor!

Also, since I always wore a suit (still do), he introduced 'FaF' day, aka, Fancy as Fuck day. Every Wednesday the guys who wanted to would come in suits.

Yup, he got me through loads of stuff, miss that guy :)

So yeah, the name change is done. Me making a joke out of being called a code slut clearly backfired and people just started calling me a slut or inferring I was a slut or something unsavory because of an online username. Lesson learned. A few lessons, in fact.

Anyway thanks for allowing the name change @dfox and @trogus. Now, back to ranting.

On being a woman in tech...

You lads probably have (and my fellow ladies certainly have) heard of "impostor syndrome" and, if you don't experience it, you possibly wonder what living with it is like.

Here's an example from this weekend.

Be me, about 5 years into my career, graduated from a top college, feeling decent but still unsure of skill.

Company gets a 4 week trial of an online learning website. It includes optional assessments, so that you know where in the video lessons to start. Rankings are novice, proficient, expert.

Hear from our QA that he got ranked "proficient." Which is a pretty broad category, but I become super afraid that I'll also be assessed as "proficient" and it will look like I have the same dev skills as a fucking QA (our management overlords can see our scores).

Boyfriend has me do some deep breathing before starting the test, because it's obvious how stressed I am.

Finally take it and get ranked "expert", in the 97th percentile, even though some technical difficulties made me miss four questions in a row. I decide to use my do over, and get ranked "expert" again, this time in the 99th percentile.

You'd think I'd be like, "Lawl, I can't believe I'd get the same score as our QA!" And there is some of that. But there's also the thoughts of, "that test could have been more thorough," "that score wasn't real because I resaw a question and got the right answer the second time," and "99th percentile isn't that great on a platform where new developers are over represented."

And this is all despite the fact that, if you were to ask someone how confident I am, the answer would probably "confident as hell."

Not saying this to start any fights. Figured it could be some interesting insight into a world that some people don't experience! (not that males aren't allowed to have impostor syndrome!)

I grew up poor. First time I saw a computer face to face was when I was 11 years old. Back then any other references to computers came through media. I genuinely believed that hacking was as seen on TV, didn't even question 2 idiots 1 keyboard and thought it was genius to unplug a computer during "an attack"

Fact is I arrived in this country when I was 11. By the time I had my first laptop I was around 13-14, as you can imagine it went really poorly for someone who was just awarded a machine of never-ending stories and entertainment with absolute fear that a single mistake can cause everything to crash and burn. Heck, I remember when I went to Vodafone and someone recommended Firefox, it was such a novelty back then, heh.

I didn't understand computers. My IT lessons were replaced to work on my dialect, but truth be told it was an awful waste of time. I've learned more from forums than I ever learned from any English teacher. I just sat there twidling my thumbs in agitation.

With no concept of what IT industry entitles (my idea of programming was cubicles and call centres), I never had a slightest clue programming could be for me. I always thought of myself closer to engineering or physics type, but that never really drew my interests. So I dwelled in depression thinking I'm broken. Useless. That there was no calling for me.

I'm 22. For the past year I dipped in and out of programming, it still felt like such black magic.vLast month or so the spell dispelled and I finally feel like my eyes have been opened. I've spent the past 3 days sitting in front of my computer learning or actively programming, with occasional dips into DevRant reading your stories, frustrations and victories and I truly feel at home.

In retrospect I feel like I made the right decision for not chasing any mathematical/physics/engineering degrees, while certainly a goal of mine, I feel like I'd be miserable in those communities. They're closer to hobbies, really.

I guess what I wanted to say is thank you. Thank you DevRant for being the spark in my null future and giving me a sense of purpose and belonging. For the first time I feel like I can make it, like there was hope somewhere over the horizon.

DevRant rant:

I am on DevRant for quite a while now and I really enjoy it here. The overall atmosphere is great, as well as the community. (Yes, that includes you!)
Since I came here I've learned some very valuable lessons regarding work (conditions), annoying coworkers and programming itself. I like to think of DevRant as a huge ball of experience by very talented people, as well as a great place for discussions about a topic we all love: code. But lately I am seeing more and more memes on here, with titles like "I think everybody know this", "I think everybody can relate" and "Soo true". Those posts have no value at all and are (most of the time) reposted from 9gag or similar networks. Sometimes those "rants" don't even have anything to do with devs anymore, but are only here to farm ++'es. In the beginning I really enjoyed funny "rants", but now the majority of them just annoy me. It becomes especially annoying when you see the same meme three times in 15 minutes.
I'd be in for some kind of DevFun section, where everybody is able to post his or hers jokes/memes/etc, but the current situation just really gets on my nerves.

I hope that I am not the only one who thinks like that, because I really feel uncomfortable ranting about something I actually love.

end rant

Sooo, in my 5 years of high school, I had 5 different IT teachers...
Now, in Italy Highschool goes from 14 to 19 years old, I started programming some days after becoming 13, and "programming" classes begin on the third year, so I had quite a headstart on my classmates...

Now, for the third year, I had an awesome teacher, he noticed I was ahead and... Bored, so he gave me some extra stuff to study, he's the only teacher I've learnt anything from, it was awesome, very stingy with grades, but getting a perfect score with him was so satisfying.

Fourth year, the new guy was old, very old, at least 70, his lessons were just him talking about how programming was when he was young.

But then... During the second half of the fourth year I changed class due to bullying under a teacher's advice, and HE happened...

My new IT teacher, one of the most ignorant, awful people I ever met...
He's literally the reason I only went back to that school once, because another teacher needed help with a course...
One day I made the HUGE mistake to say that his "while(i <10000000000000);" wasn't very efficient for making a delay, because it didn't free the CPU, and since then:
- I never got more than 7 out of 10 at his tests
- He insulted me in front of the whole class
- He sabotaged the oral part of my final exam, shouting that he hated D'Annunzio when he saw he was in the literature part of my thesis (needed him to connect to WW2, and the Memex, that then allowed me to start talking about PCs and programming, my thesis was about the influence of lisp on modern programming languages), loudly chatting with other teachers when I was trying to keep calm (a teacher who knows me quite well, and was there to see my "performance" thought I was going to snap at some point), distracting the english teacher when I was exposing the english part of my thesis and pressuring the commission to give me 99 instead of 100 out of 100

So yeah, he almost made me hate the only thing I'm good at, undervaluing my work and my skills, undervaluing and humiliating me as a person, and I think that if I meet him again I might spit on his face...

So yeah, my biggest "programmer enemy" was a person that then did everything in his power to make my last year and a half of highschool hell

Now I can gladly say that with the help of my tutoring, some of my university colleagues are starting to appreciate programming, and my engineer friends ask for my help when they need advices about their code, and it's giving me motivation to keep doing it and becoming a better programmer to keep up with their expectations

"Enigma machine kep private the communications done by Nazi. It was a really difficult code to break because it changed each day. There was a man in England, Alan Turing, who broke it. He's nowadays known as one of the fathers of the Computer Science. I will show in the next lessons how you can simulate Enigma coder just with an easy C program of 60-70 lines. In the WW2 this was considered a military-level safe code. Thanks to mathematicians, computer scientist and analyst and thanks to their work in the last 60 year, you have access to a systems of several orders of magnitude more efficient and secure when you buy a videogame online."
That really fucking inspired me.

Hesitated for a while before posting this, as I don't like to whine in public but this should be therapeutical

Beware, it's a #longread

Years ago, I thought about how cool it'd be to have conversation-based interactive fiction on my phone. I remember showing early prototypes to my ex in 2012. It took me over 2 years to build up the courage to make it my priority and to take time off. FictionBurgers.com was born.

A few weeks in, a friend of mine forwarded me a link to Lifeline. I was devastated. I literally spent 2 days cursing my past self for not making a move sooner.

I soldiered on, worked 7 months straight on it. Now the tech is 90-95% finished, content is maybe 60% finished and I just... gave up. Every other week now, similar projects are popping up. I'm under-staffed and under-financed compared to them. Beyond the entertainment space, "conversation-based" is hot stuff in 2016, and I still can't seem to know what to do with what I have.

I feel like I had this fantastic opportunity and squandered it, which makes me miserable.

Anyway, just so you get some cheese with my whine, here are a few lessons I learned the hard way:

Lesson #1 : Don't go it alone. I thought I could hack it, and for over 7 months, I did. But sooner or later, shit gets to you, it's just human. That's when you need someone; just so that their highs compensate your lows and vice versa. Most of the actual writing was done by a freelancer (and he did AMAZING WORK, especially considering that I couldn't pay him much) but it's not the same as a partner, who's invested same as you.

Lesson #1.5 : Complementary skills. Just like my fiction project failed because I was missing a writer partner, my fallback plan of getting into conversational tech hit the skids for lack of a bizdev partner. It's great to stick among devs when ranting, but you need to mingle with a variety of people. Some of them are actually ok, y'know :)

Lesson #2 : Lean Startup, MVP. Google those terms if you're not familiar with them. My mistake here (after MVPing the shit out of the tech) was to let my content goal run amok : what made my app superior to the competition (or so I reasoned) was that it would allow for conversations with multiple characters! So I started plotting a story... with 9 characters. Not 2 or 3. NINE FREAKING CHARACTERS! Branching conversations with 9 characters is the stuff of nightmare -- and is the main reason I gave up.

Lesson #3 : Know your reasons. I wasted some much time early on, zig-zaging between objectives:
"I'm just indulging myself"
"No, I really want it to be a project that pays off"
"Nah, it's just a learning opportunity"
"Damn, why is it bothering me so much that someone else is doing the same thing ?"
"Doesn't matter, I just mine finished"
"What a waste of time !!"
etc etc
And it's still a problem now that I'm trying to figure out what to do!

So anyway, that's my story, thanks for readin'
Check out chatty.im/player/sugar-wars if you want to test the most advance version.

Also, I've also tagged this #startupfail, if any of you fine people want to share the lessons you've dearly paid to learn!

I once reviewed a Pull Request made by a fairly junior developer. They had joined recently, and this was one of the first times they had to touch a bigger part of the code.

Due to a mix of inexperience, new (to them) coding standards and lack of git knowledge, they ended up with a mess of a PR, with a few thousand lines changed, and no way to split it off.
I ended up spending the best part of a day reviewing the whole thing and requesting changes.

Even with the long list of improvements, however, I wasn't sure they would get the magnitude of their fuckup.
So I decided to use a real-world, palpable way to show them what they had done: I went and printed the github diff for that PR. It rendered the glorious amount of 73 pages.

I'll never forget their face, and those of their teammates, when I barged into the room with a thick wad of paper and deposited them on their desk.

At least it worked. I never saw another big, ill-thought pull request from them again.

My second year of high-school, we started having class in computer science. I was really looking forward to it cause I always wanted to learn programming.

On first sight it appeared that the professor which taught the class knew something, he looked like a genuine geek with those dorky glasses, briefcase and pants like Steve Urkel, but after couple of his lessons you could see he had no real dev experience and just basic understanding of programming in theory. He was more reading stuff from the book than he was trying to explain them to students and give some real world examples.

So it was just one these days, everybody got back from vacation, it's hot outside, the guy is just reading sentences from his book, half of students talk with each other and other half doesn't give a fuck about him or his class. Pretty sure I was the only one trying to listen to him and learn something from his recitals.

All of a sudden he notices the atmosphere in the classroom, slams the book shut, gives out couple of F-s to the loudest students and yells out loud "NONE OF YOU IN THIS ROOM WILL EVER ACCOMPLISH ANYTHING IN YOUR LIFE, BARE ALONE IN PROGRAMMING"

At first I felt like shit, but soon after that I started thinking "who the hell are you to tell me what I could or will accomplish in my life". Couple weeks later I've bought myself a first book in programming and started learning C++ late at night since I understood that I won't learn anything about programming in that school. Two years later I was correcting this same professor with his claims on a whiteboard in front of a whole class.

Today, seven years after his words I'm a developer living in foreign country with what I could say somewhat a solid experience and understanding of how both software and web are build, while that same professor still recites to his pupils difference between assembly and object code, while praying nobody asks him where and how these are used. For maybe a quarter of my paycheck. So much about his psychic powers..

Funny story from yesterday at work.
Useful to know for later on, the last sentence of the 'convo' is a sentence from a Dutch movie, it basically translates to 'youre fired, vagina' (we swear with that here but it sounds better in Dutch tbh)

Somehow got to the subject of motorbike lessons:

Colleague (M): so just imagine the motorbike instructor arriving for the first lesson and me doing a wheelie right away 😆
Colleague (B): and then his boss coming around at the same time and seeing that happening
(one of our most silent but always on point colleagues) Colleague (c): je bent ontslagen, kut!

Aaaaaand everyone fucking lost it 😂

I met some guys who were Computer Engineering students who were studying web platform as a hobby aside from IoT lessons at school, they met me at my school's library coding stuff and I noticed one of them messing around with yum

"Is that Fedora?" I said, because I wasn't familiar what are the package managers of every distro.

"No, it's CentOS" the guy replied, he also noticed I was coding in a cloud IDE, so he was amazed. He asked if he can use C# there, can he share his workspace, etc.He also asked what's my course. I replied " i'm jsut a senior high student". And they were out of words.

after that, I always think that my skills are way ahead of my age. I don't know my brain anymore, but I felt badass

I have seen it. They say it doesn't exist; just a story we tell our children so that their innocence does not lead them down into a nightmarish adulthood from which there is no salvation. But the evil lives. So vile that were you to look inside its soul, all you would find is a terrible desperation for suffering. To cause it. To revel in it. To bathe in the tears of those it considers less than human and feed off the emotional detritus.

It was 2009. The financial crisis. I was one of the lucky, having found refuge in a large company right before the jobs dried up. General IT: system administration, documentation, project management, telephony, software training, second level help desk. No software development, but with a two-year-old at home and Ph.D.s lining up outside the local Olive Garden whenever a help wanted sign was posted, I grabbed the health insurance and entered into darkness.

The Thing did not need to hunt it's prey. A manager title with 21 reports brought it new opportunities for fresh meat by the hour. But I was special. I resisted. I needed to know my place.

My first mistake was incomprehension. I did not understand the Thing's lust to be right at all costs. I was reviewing some documentation it had brought forth from its bowels. I mentioned that two spaces were being used between sentences. That proportional type made that unnecessary. It insisted, I was wrong. It insisted that Microsoft itself, the purveyor of all good technical writing, required two spaces. I opened the Microsoft Manual of Style for Technical Publications that it demanded its staff use and showed it that the spec was one space. It was livid. I was a problem.

From that point on my work life became exponentially more wretched. I was given three Outlook calendars to maintain: one with my schedule, one with the team's schedule and one with the Thing's schedule. Every time I had an appointment, I was to triple schedule it. If I was going to be away from my desk for more than 15 minutes triple schedule. Triple schedule my lunch, vacations, phone conferences.

Whenever it held a meeting, I and a colleague would be taken off mission critical IT projects to set tables with name tents and to serve as greeters as attendees arrived.

I was called into its crypt to be told never to say anything in a meeting unless I told the Thing beforehand what I was going to say. Naive, I mentioned that I often don't know what I will say as it is often in reply to someone else. Of course the response was that I should not say anything.

I would get emails 10-20 times a day asking about a single project. I would regularly complete work that was needed to be completed ASAP, only to have the Thing rake me over the coals for not completing it a week later. And upon resending the emails proving I notified it of the work being competed, disparaged at length a second time for not sending repeated notifications of the competed work.

I would have to sit in two-hour meetings to watch it type. Literally watch it try to create cogent thoughts. In silence.

I received horrendous annual reviews. At one, it created a development plan that stated a colleague would begin giving me lessons on the proper ways to socially interact with personnel. I pointed out to HR that this violated privacy concerns and would make the business liable in many areas, not least of which would be placing a help desk person in the role of defining proper business practice. HR made the Thing remove this from my review. She started planning to remove me.

I had given a short technical training to a group of personnel months earlier. Called into its tomb I was informed that feedback surveys on my talk were disturbing. One person stated that they did not think I was funny. Another wrote that I made an offensive statement. That person did not say what the offensive statement was. Just that I had said something he or she didn't like.

The Thing interviewed the training attendees. Gathered facts. Held three inquest-like meetings where multiple directors peppered me with questions trying to get me to confess to my offensiveness. In the end the request to fire me was brought to the man who ran the business at the time. The statement on high: "Humor is a subjective thing. Please tell This to be sensitive to that."

The Thing had failed, but would no doubt redouble its efforts. I had to find a new job. I sent hundreds of resumes. Talked to dozens of recruiters. But there were no jobs. And I had a family. And the wolf was at the door.

So I didn't say a word to the creature. For six months. Silence. At one group meeting it shrieked at me "what are you smirking at? If you've got something to say then say it!" I just shrugged. For my salvation was revealed. The Thing could not stand to be ignored. And at the end of my penance I was transferred to another group: Software Development.

I am one with the Force. The Force is with me. I am one with the Force. The Force is with me.

Well, some time in the future, i will have to sit a computer science exam with C#. It can't be that bad, right?

Wrong.

To start off, Visual Studio 2013. Why the fuck someone would use this pile of garbage in 2018. I have no fucking clue why any semi-competent IT department would decide to skip TWO fucking releases of the software and decide, that it's okay to just roll with it. It's okay to not have any updates. It's okay to just no care at all.

I literally brought in my laptop with a VM installed since Visual Studio 2017 is really superior to the crap from 5 years ago just to do my coursework most lessons.

-------

Second issue, you know thoes desks where the monitor is literally under the desk and you get a small little window to see the monitor? Yeah, well I will have to take my proper exam in one of these all over the fucking room. Pic related.

Today we had a mini mock - - it went something like this:
- There was glare from the glsss on the desk because of the lights in the room and literally the monitor itself.
- The glass was beyond fucking pig filthy.
- There was neck pain from my back because i was constantly looking down and bending over the see the screen.
- There was eye strain because the document given to us was a tiny piece of paper with tiny writing and the monitor was far away and the paper was close i couldn't focus my eyes.
- Literally every desk was as bad as the next.
- I did fuck all work because i just couldn't focus because of the things above.
You can tell how great that felt.

If i was in a room with a man (or if it was a woman, let's just pretend she has balls), who was the creator of the room i just described, Hitler, my College's IT staff and other really bad people while having infinite ammo, i would continuously shoot the creator in the balls while not giving a shit about anything else.

Forever.

Until heat death.

Thanks for reading.

Let me just delete this symbolic link and leave it copying the folder to the ssd real quick while I go to lunch...

Lessons learned:

1 - don't put a fucking / at the end of `rm -rf /path/to/link`

2 - don't ignore the warning of it being a folder after trying to `rm /path/to/link`

3 - backup your fucking dev database too

4 - don't do stuff hungry

SHIT!! FUCK!!

This spring I was working on a library for an algorithm class at uni with some friends and one of the algorithm was extremely slow, we were using Python to study graphs of roads on a map and a medium example took about 6-7h of commission to finish (I never actually waited for so long, so maybe more).
I got so pissed of for that code that I left the lab and went to eat. Once I got back I rewrote just the god-damned data structure we were using and the time got down to 300ms. Milliseconds!

Lessons learned:
- If you're pissed go take a walk and when you'll come back it will be much easier;
- Don't generalize to much a library, the data structure I write before was optimized for a different kind of usage and complete garbage for that last one;
- Never fucking use frozen sets in Python unless you really need them, they're so fricking slow!

Everyone is posting jokes about GitLab recent incident and how the guys responsible for that must be feeling right now.
Shit happens, sometimes it's you accidentally deleting a branch on your repo and turning that into a major crisis, sometimes is a huge mistake that impacts not only the whole company business, but also it's clients work.

This situation reminds me of a famous quote from Thomas J. Watson (ex lBM CEO):

"Recently, I was asked if I was going to fire an employee who made a mistake that cost the company $600,000. No, I replied, I just spent $600,000 training him. Why would I want somebody to hire his experience"

Those guys at GitLab have probably learned one of the most expensive lessons in IT world and I really wish them to come up with a solution that not only fixes this case, but that helps them preventing future occurrences.

I guess tux knows me very well

Throwback to my first assignment in MATLAB.
Still gives me the heebie-jeebies!

My CTO in the 'good old times', when he still talked to me and shared his wisdom, once told me what I should know about oop and explained me the world of programming and what really matters:

CTO about oop and C#:
"I think this object orientated stuff is overrated and useless. You don't get finished. I write everything in one file. You should do that too. The fastest way is always the best one."

So, dear readers, you might think, he maybe understood, what oop means. I have to disappoint you. He is as FUCKING STUPID as he sounds.
He didn't understand the whole concept of the language C# or oop.
He doesn't use properties, every single method is static void and there is nothing like an object.

Since there is more from where that came from, this will be continued...

After months and months of slaving away, I quit my start-up job and feel completely amazing- here's what happened:

Met a classmate in grad school and he talked about starting his own company and he had full funding and etc. After graduation, moved to the new city where the job was located.

There were all these promises of us being co-workers and working on cool things and many other promises made. Soon after starting the job, most of these promises we're just smoke and mirrors.

Started working day in day out. Worked from 8am-9pm most days and worked on weekends too. Treated me like a I was a dog, talked down to me, gave unrealistic deadlines, pressured me with attitude and threats of losing my job. Hell, they thought they were the smartest person to touch the earth basically- example being that they mixed jQuery with VueJS in our Django template.....who the F*** does that. Another thing being that they had issues with me soft deleting records since they wanted them completely hard deleted and we had gotten into a giant argument about that fml.

What led to me leaving the job was that I had gotten sick one of the weeks, and I still showed up to work. Each day I was gradually getting sicker and sicker. Still tried my best to get work done. Saturday morning I get the most passive aggressive and bitchy text from my co-worker. "if you don't complete blah blah blah by Monday, we are going to have issues. Then on Monday you will work on blah blah blah". They blew the fuse with me. They would always punish me for being sick or taking a vacation. I'm not a dog, not a machine, I'm a f****** person. Went into his office when the work week started and gave my resignation on the spot and felt like it was the best decision I've ever made.

Now I just feel like a giant toxic cloud has disappeared from my life. I did walk away with so much experience and knowledge but now I just feel extremely burnt out from programming. Is this what I even wanna do anymore?

Few lessons I learned along the way:
1. If it sounds too good to be true, it probably is
2. Free lunches aren't worth it
3. Unlimited PTO doesn't really mean unlimited- there's always stipulations
4. Start-up life isnt as cool as they say- don't take TV portrayals as the real thing
5. Your mental health is extremely important
6. It's okay to admit to yourself that you're burnt out
7. Take a break
8. STARTUPS ARE NOT FOR EVERYONE

This is just my experience and what I learned, so telling my story. Phew, feels so good to get that off my chest

Okay so here are a few lessons that I have learned from being an intern to a junior developer (who’s just 2 years out of college).
- every ninja engineer starts off as a noob. There’s nothing to be ashamed of if you don’t know “everything” about coding
- Respect everyone’s opinion (including the one that shouts your design is crap in a meeting). Don’t process them too much.
- leave things that happen at work, in the workplace
- Keep yourself up to date even after you’ve bagged the 100,000$ offer. Never.stop.learning.
- Be polite to your interns (been there). They look up to you and treat their juniors the way you treat them.
- Be honest. Including your tiny scrum updates. If you need more time, tell it. If you’ve screwed up something , own it up.
- Never blame or point fingers.
- Nothing is irreversible.(except things like sudo rm -rf/)
- There’s always a way out(of any mess).
- Respect what came before.
- Respect what comes after (before you push badly written code)
- It’s ok to point out mistakes but Be kind. (Else you’ll end up in someone else’s rant ;-) )

Back in the day, I joined a little agency in Cape Town, small team small office with big projects, projects they weren’t really supposed to take on but hey when the owner of a tech business is not a tech person they do weird things.
A month had passed and it was all good, then came a project from Europe, Poland to be specific. The manager introduced me to the project, it was a big brand - a segment of Lego, built on Umbraco (they should change the name to slowbraco or uhmmm..braco somewhere there) the manager was like so this one is gonna be quite a challenge and I remember you said you are keen on that, I was like hell yeah bring it on (genuinely I got excited) now the challenge was not even about complexity of the problem or code or algorithms etc you get my point… the challenge was that the fucking site was in polish - face palm 1 - so I am like okay code is code, its just content, and I already speak/familiar with 13 human languages so I can’t fail here ill get around it somehow. So I spin up IIS, do the things and boom dev environment is ready for some kick ass McCoding. I start to run through the project to dig into the previous dev’s soul. I could not relate, I could not understand. I could not read, I could not, I could not. - face palm 2 - This dude straight up coded this project in polish variable names in polish, class names in polish, comments in freaking polish. Look, I have no beef with the initial guy, its his language so why not right? sure. But not hey this is my life and now I should learn polish, so screw it, new tab - google translate, new notes, I create a dictionary of variables and class etc 
3 days go by and I am fucking polish bro. Come at me. I get to read the previous devs soul through his comments, what a cool dude, his code wasn’t shit either - huge relief. So I rock on and make the required changes and further functionality. 

The project manager is like really, you did it? I am like yeah dude, there it is. Then I realise I wasn’t the first on this, this dude done tried others and it didn’t go down well, they refused. - face palm 3 -

Anyway, now I am a rock star in the office, and to project managers this win means okay throw him in the deep - they move me to huge project that is already late of course and apparently since I am able to use google translate, I can now defeat time, let the travelling begin. - face palm 4 - I start on the project and they love me on it as they can see major progress however poland was knocking on the door again, they need a whole chunk of work done. I can’t leave the bigger project, so it was decided that the new guy on Monday will start his polish lessons - he has no idea, probably excited to start a new job, meanwhile a shit storm is being prepared for him.

Monday comes, hello x - meet the team, team meets x

Manager - please join our meeting.

I join the meeting, the manager tells me to assist the new dev to get set up.

Me: Sure, did you tell him about he site?

Manager: Yes, I told him you knocked it out the park and now we just need to keep going

Me: in my head (hmm… that’s not what I was asking but cool I guess he will see soon enough -internal face palm 5 - )

New dev is setup, he looks at the project, I am ask him if he is good after like an hour he is like yeah all good. But his face is pink so I figured, no brother man is not okay. But I let him be and give him space.

Lunch time comes, he heads out for lunch. 

1hr 15mins later, project manager is like, is the new dude still at lunch.

We are all like yeah probably. 

2hrs pass 

3hrs pass

Now we are like okay maybe something happened to him, hit by a car? Emergency? Something… 

So I am legit worried now, I ask the manager to maybe give him a ring. 

Manager tries to call. NOTHING, no response. nada.

Next day, 8am, 9am, 10am no sign of the dude. 

I go to the manager, ask him what’s up. 

Manager: he is okay. However he said he is not coming back. 


Hey guys and ladys. I've got another little rant about my teacher.
As some of you may know, i finished my final exams last week, so basically every relevant grade is done. Every teacher except of my special snowflake programming teacher spends the lessons casually talking with us (some even say we dont need to show up anymore).
Little backstory: Grades need to be done on 18th, June and i get my certificate on 22nd.

Back to my rant. Special Snowflake is different. He wants ANOTHER project. This is totally his idea and is nowhere mentioned in our curriculum. It has to be done until next friday, it has to be C# and we need a detailed documentation. This wouldn't be a problem normally - if I wouldn't be moving at the moment. Special Snowflake knows this but doesn't care.
Except from the criteria above he wants it to be:
- fancy
- loved by everyone. Literally we need to make something EVERYBODY wants in their daily life
- good looking
- everyone should want to pay money for this

How am I supposed to come up with an idea and program the shit out of it in less than 2 weeks, which i need to paint my new office and pack some more stuff.

A College Friend of mine has offered last year a free C++ course for everyone who is interested, this year he is doing the same in Rust. This guy can explain and gives a big part of his freetime for this.
He is just amazing.

Thanks to everyone who shares his/her knowledge!

What is with the +1 chasing in here? Votes should be given for good rants and comments, not to climb the count-ladder if that somehow would make you elite community member. Posting a picture you found elsewhere just to earn free stickers or a stress ball, and pollute the incentive the swag were meant for originally.

Stop mass +1'ing some random guys every comment, and earn the votes by contributing with stories, lessons learned, proper rants and supportive comments.

Tl;Dr - It started as an escape, carried on as fun, then as a way to be lazy, and finally as a way of life. Coding has defined and shaped my entire life from the age of nine.

When I was nine I was playing a game on my ZX spectrum and accidentally knocked the keyboard as I reached over to adjust my TV. Incredibly parts of it actually made a little sense to me and got my curiosity. I spent hours reading through that code, afraid to turn the Spectrum off in case I couldn't get back to it. Weeks later I got hold of a book of example code to copy out to do various things like making patterns on the screen. I was amazed by it. You told it what to do, and it did it! (don't you miss the days when coding worked like that?) I was bitten by the coding bug (excuse the pun) and I'd got it bad! I spent many late nights on that thing, escaping from a difficult home life. People (especially adults) were confusing, and in my experience unpredictable. When you did things wrong they shouted at you and threatened to take you away, or ignored you completely. Code never did that. If you did something wrong, it quietly let you know and often told you exactly what was wrong. It wasn't because of shifting expectations or a change of mood or anything like that. It was just clean logic, simple cause and effect.

I get my first computer a year later: an IBM XT that had been discarded by a company and was fitted with a key on the side to turn it on. With the impressive noise it made it really was like starting an engine. Whole most kids would have played with the games, I spent my time playing with batch scripts and writing very simple text adventures. And discovering what "format c:" does. With some abuse and threatened violence I managed to get windows running on it. Windows 2.1 I think it was.

At 12 I got a Gateway 75 running Windows 95. Over the next few years I do covered many amazing games: ROTT, Doom, Hexen, and so on. Aside from the games themselves, I was fascinated by the way computers could be linked together to play together (this was still early days for the Web and computers networked in a home was very unusual). I also got into making levels for Doom, Heretic, and years later Duke Nukem 3D (pretty sure it was heretic; all I remember is the nightmare of trying to write levels entirely by code!). I enjoyed re-scripting some of the weapons and monsters to behave differently. About this time I also got into HTML (I still call this coding, but not programming), C, and java. I had trouble with C as none of the examples and tutorial code seemed to run properly under a Windows environment. Similar for my very short stint with assembly. At some point I got a TI-83 programmable calculator and started rewriting my old batch script games on it, including one "Gangster Lord" game that had the same mechanics as a lot of the Facebook games that appeared later (do things, earn money, spend money to buy stuff to do more things). Worried about upcoming exams, I also made a number of maths helper apps, including a quadratic equation solver that gave the steps, and a fake calculator reset to smuggle them into my exams. When the day came I panicked and did a proper reset for fear of being caught.

At 18 I was convinced I was going to be a professional coder as I started a degree in Computer Science. Three months later I dropped out after a bunch of lectures teaching what input and output devices were and realising we were only going to be taught Java and no C++. I started a job on the call centre of a big company, but was frustrated with many of the boring and repetitive tasks we had to do. So I put my previous knowledge to use, and quickly learned VBA to automate tasks. It wasn't long before I ended up promoted to Business Analyst where I worked on a great team building small systems in Office, SAS, and a few other tools.

I decided to retrain in psychology, so left the job I was in and started another degree. During my work and placements my skills came in use a number of times to simplify and automate tasks. I finished my degree, then took a job as a teaching assistant while I worked out what I wanted to do next and how to pay for it. Three years later I've ended up IT technican at the school, responsible for the website, teaching a number of Computing lessons each week, and unofficial co-coordinator for Computing as a subject. I also run a team of ten year old Digital Leaders who I am training in online safety and as technical experts; I am hoping to inspire them to a future in coding. In September I'll be starting teacher training with a view to becoming a Computing specialist teacher. Oh, and I'm currently doing a course in Android Development in my free time.

And this all started with an accidental knock on the keyboard of a ZX Spectrum.

- hold yourself accountable for your mistakes
- keep track your mistakes and learn from them
- put thought in what you do
- be organised
- become comfortable asking for and offering help
- realise that some problems have no universal solution
- don't just copy what others do, but also think for yourself
- learn to be patient

Recent life lessons:
◆ Do not buy a domain name without obfuscating your contact information, lest you want to be harried by people offering to provide their services to “grow your business”

◆ Do not change descriptions on your most recent experience that’s set to be ongoing on LinkedIn without making note of the “notify your followers” toggle, lest you wish LinkedIn to post on your behalf a message urging people to congratulate you on your new position. A post which you cannae delete. And lo, if you comment upon it urging well-wishers to not comment upon it or offer congratulations as it is not what it appears, witness the lack of good that doth do. Resort to canned response to DMs explaining the situation and urging the well-wisher to learn from your misfortune. (I find it really difficult to not politely respond to folk. It was a good two days of like 50+ messages.)

◆ If you have a career coach that tells you to connect to as many people as possible on LinkedIn and accept connection requests, perhaps just don’t follow that advice. My second career coach was like “That doesn’t even make sense” “I KNOW!” ... I have so many LinkedIn connections. But I cannae just prune the list because it would take for freaking ever to figure out who was who and who I really still wanted to connect with. *sigh* 900+ is too many. And I have over 100 requests I haven’t even gotten around to looking at.

School sucks.
Paying quiet a lot of money(not having that much) to a private school that used to impress me two years ago.
Now I can see all the hidden crap:
- Project work is graded after written lines

- "Do this project with scrum" Got two hours in the room with scrum board in a whole semester

- Exams are pushed if the teacher is to lazy to deal with bad results. A 3 ( or C ) became best grade.

- They could not find a teacher for OS & Networks. So instead of 1 semester Server architecture we got 5 days.. 1 of them for exam (exam = final grade)

- Guy took part with us during the 5 days. "How did you do that?!? Doesn't work on my PC I think" - half year later he is the new Network teacher

- Surpassingly he sucks at that, being half a week ahead of his lessons by googling shit together. Can't answer a single question beyond that..

Once he created a multiple choice exam. Questions in a word document online, answers on paper. Not just that he never blocked the internet during the exam, he also publicly uploaded the document a week ahead. Securing it with a 5 letter password... Somehow we all passed that one with a pretty good average.

Besides there a some teachers who are actually really good.

The tour provided with Golang is really nice for learning the basics..
Just doing

go get golang.org/x/tour/gotour
go tool tour

starts a local webserver with the tour. The lessons and the exercises at the end of certain chapters are really easily understandable.

I think it might also be a good tool to refresh the knowledge about Golang for those that haven't used it in a while.

You know what really, really sucks about my school? Rant#00

I'm in my last year now and they removed one CS/IT lesson. Now I have two fucking 45min lessons (instead of three) of learning what I'm actually interested in.

Even worse: They don't provide and LK ("Leistungskurs" == advanced course) for CS/IT. Not like for Maths, English, German - okay but LATIN AND SPORT? Wtf
And this school calls themselves a MINT-school (Maths, IT, Natural Sciences, Technology).

EVEN WORSE: The 12th graders now don't even have a basic course CS/IT.

Fuck you school.

Software development lessons are so boring and the teacher is so stupid. He can't swap two variables without a temporary var. He said that he never saw this kind of swaping before. I pay attention sometimes, but I'm just drawing in my exercise book.

While working on my one of the first project in java i ended up using deprecated Calendar API for the date. Since deadline was near i thought it would be a good idea to use the JCalendar API for as date picker (which is a third party API).BAD IDEA. It was the night before the submission round about 11pm when i realized that there is no way to convert JCal object into Calendar and it turned out it is not working as expected you have to subtract a particular number from the year to get date right.

To convert JCal into Calendar i used the toString function to get the date in string sliced it using substring into year,month,day then had to assign date to Calendar object via constructor.
Had to write 70 lines of code just to convert JCal into Calendar...

And then there were other complications related to this problem. Had tu pull an all nighter just to solve date related problems
LESSONS LEARNED :
NEVER USE A DEPRECATED API
NEVER USE THIRD PARTY APIs WITHOUT RESEARCH

!dev

The school I went to didn't have PCs when I first joined (had some RISC OS machines instead). They got Windows 95 PCs eventually and networked them. I had no experience with networking before this, but had a PC at home. We all had mapped drives to resources on the server. The PCs were pretty locked down - no "Run" command etc.

Anyway, one day the head of IT came in to one of the lessons and asked me "how I did it".

What had I done? Well, clearly he had seen something I'd taught one of my friends. I wrote it down for him.

1. Right-click the desktop
2. New shortcut
3. \\nameofserver
4. OK

Such hax, being able to see the file shares on the server.

Shortly after this, all computer areas had signs saying "no shortcuts allowed"...

!Rant

Lessons from this picture:
1. Not all opportunities are to be taken. Some are traps.
2. A person can become so determined to destroy another person that they become blind and end up destroying themselves.
3. You fight best in your natural element and environment. Here the bird has advatange in his natural element.
4. Know your limits, we all have them.
5. Sometimes the best response to provocation is not to fight.
6. Sometimes to accomplish something you need team work, you will not always win alone.
7. Stick to what you do best and don't pursue what will kill you.

👍🏻👍🏻👍🏻

Life lessons.

When I was a graduate I often had to do proof of concepts and one had to be done by the weekend, I'd only been given it on the Wednesday. After a few sleepless nights I had it working or so I thought. On the Friday afternoon the CTO had a look at it and spotted a bug, he told me about it and I stayed in the office until about 10 when I finally managed to get some kind of fix in place. I emailed him told him I thought but was working and shouldn't happen again.

A few hours later no response I get a phone call from him screaming, shouting and swearing calling me useless and a waste of space etc. Etc. To the point I logged in desperately trying to fix the issue in a very hastily written integration and ended up having quite a major panic attack woke up on the floor and immediately went back to work. On the Saturday morning one of the senior Devs logged in and managed to fix it in the database and everything went fine in the end.

I went into work on Monday fully expecting to be fired from the way the CTO was speaking to me, I went to my line manager at the time and he just said don't worry. I left it in his
hands and things went back to normal. That call put a pretty serious dent in my confidence for years, but I learned a few valuable lessons which I stick to today.

Never work on serious shit after 6, use a second mobile for work which is turned off at 5 o'clock, properly test all fixes and always ALWAYS have someone in between graduates and senior management because honestly they can't handle the shit that's flung from above.

Something I ranted about 1 year and 2 days ago just saved my life today. Those lost hours that day saved me a few hours today.

I wonder though: if I hadn't written about it on devRant, would I still remember it today?

Well, I was Always into Computers and Games and stuff and at some point, I started wondering: "why does Computer Go brrr when I Hit this Button?".

It was WinAPI C++ and I was amazed by the tons of work the programmers must have put into all this.

13 year old me was Like: "I can make a Game, cant be too hard."

It was hard.
Turns out I grabbed a Unity Version and tried Things, followed a tutorial and Made a funny jet Fighter Game (which I sadly lost).

Then an article got me into checking out Linux based systems and pentesting.
*Promptly Burns persistent Kali Live to USB Stick"
"Wow zhis koohl".
Had Lots of fun with Metasploit.

Years pass and I wrap my head around Javascript, Node, HTML and CSS, I tried making a Website, worked Out to some extent.

More years pass, we annoy our teacher so long until he opens up an arduino course at school.
He does.

We built weather stations with an ESP32 and C++ via Arduino Software, literally build 3 quadrocopter drones with remote Control and RGB lighting.
Then, Cherry on the top of everything, we win the drone flying Contest everyone gets some nice stuff.

A couple weeks later my class teacher requests me and two of my friends to come along on one of their annual teacher meetings where there are a bunch of teachers from other schools and where they discuss new technology and stuff.

We are allowed to present 3D printing, some of our past programming and some of the tech we've built.

Teachers were amazed, I had huge amounts of fun answering their questions and explaining stuff to them.

Finally done with Realschulabschluss (Middle-grade-graduation) and High school Starts.
It's great, we finally have actual CS lessons, we lesen Java now.
It's fuckton of fun and I ace all of it.
Probably the best grades I ever had in any class.

Then, in my free time, I started writing some simple programs, firstvI extended our crappy Greenfoot Marsrover Project and gave it procedural Landscape Generation (sort of), added a Power system, reactors, Iron and uranium or, refineries, all kinds of cool stuff.

After teaching myself more Java, I start making some actual projects such as "Ranchu's bag of useful and not so useful stuff", namely my OnyxLib library on my GitHub.

More time passes, more Projects are finished, I get addicted to coding, literally.
My days were literally Eat, Code, sleep, repeat.

After breaking that unhealthy cycle I fixed it with Long Breaks and Others activities in between.

In conclusion I Always wanted to know what goes on beneath the beautiful front end of the computer, found out, and it was the most amazing thing ever.
I always had constant fun while coding (except for when you don't have fun) and really enjoyed it at most times.
I Just really love it.

About a year back now I noticed that I was really quite good at what I was doing and I wanted to continue learning and using my programming.
That's when I knew that shit was made for me.

...fuck that's a long read.

BLESS YOU
- @Root, for everything
- @SortOfTested, for “grass is greener / grass is alive” and everything, too
- @Floydimus, for being so nice to me
- @theabbie, for not cracking under pressure. I admire you and you’re an example to me
- Anonymous members I chatted with over Telegram, for valuable lessons and helping me cope

FUCK YOU
- girl who raped me
- ex who gaslighted me when I was weak
- sadistic psychiatrist who knowingly prescribed wrongful pills
- ex who abused me when I was on a devastating wrongful therapy
- boss guy who touched me without my consent
- each and every cop and military guy I’ve ever talked to, except WWII veterans
- whatever filled my life with nothing but guilt

So, during my Java lessons we had a teacher who had a very special relationship with the language.
During the introduction he used to tell us that interfaces in Java are really poorly designed and that they would not reflect how an interface normally should be implemented. The possibility for a developer to add default methods to an interface or that a class could inherit from multiple interfaces was unacceptable to him.

Due to those reasons, he would hate on Java 8 and tell us to not use it and instead stay with Java 7 - dafuq!

Not sure if this technically counts as all nighter, but when Udacity released their basics Android nanodegree they had a contest where the first 100 worldwide to finish got a scholarship for the advanced Android nanodegree. I followed the uberman sleepy schedule, 20 min nap every 4 hours, around the clock for 6 days. Finished #17. They didn't even have the videos or lessons for the last 3 sections, just a description and a project for each, so they set up a slack channel to let us talk with staff and collaborate with others trying to get it done.

I worked two months for free, 15h per day, including weekends, due a contract trap. On top of that, client was emotionally blackmailing me and I was feeling threatened and helpless.

I even lost weight, skipping meals to save time and money. One day, my body collapsed. I ended up in bed for 10 days, feeling stiffness, pain, weakness, and shakiness. I even had to ask for help to brush my teeth.

I abandoned the project, and didn't receive any payment. The client went crazy and made me feel the worst person in the world for being sick and unable to work. But didn't put his menaces in execution.

I still remember the joy I felt when I was able to walk again.

That was the worst burnout I had, and also one of the biggest lessons about limits and evil people.

So at this startup i was single iOS dude age 34, android had 1.5 dudes, one older, one you ger. That 0.5 younger was tech director, really good, so they churned for two guys. Millenial, nice guy, never making conflict, just being sleazebag.

Nobody explained to boss why iOS was always late with features, even when i complained. So i got help, 10 months later, project was unpolished but stable, codewise. Now i interview and hire a guy, age 27, who was all yeah dude no problem, and that being my first interview, i fell under his friendly appearance. I ignored a fact that he didn’t know 90% of stuff i was asking him, because he was so friendly and outgoing and we will do anything attitude.

The guy knew very little, was childish and irresponisble. He showed at work at noon. He started telling me what to do, his senior collegue who started the project. He argued about everything that i would tell him. So i spent three to four hours a day charting with him, because we were in different cities. He had two uears of experence, but he was below junior level. And he refused any of my advices for learning in free time. No, he said, thats my free time, you will not tell me what to do. Well, how do you plan on being better, i asked. He said, i learn by doing. But, since he was at his job only six hours a day, instead of eight, and since he was productive only for 2, i guess he was lazy.
He would deliver a UI he would make, without business logic, and tell it is done. Then clients would call me and ask why text fields are not saved..

This all took me month to understand. I lost time, i lost trust, and soon he was fired.

But, soon i was fired also, replaced by another two devs who i had interviewd and formed a team. I was discarded as trash, just like that. I have even worked overtime to catch up with android guys, unpaid.

Took me year to recover mentally from this.

Lessons learned: be objective when interviewing. Job is business, not friendship, trust no one, keep neutral on work. Leave honesty for someone else, honesty will be used against you. Never criticize two girls in office who disturb developers by talking about sex and dicks all the time, dressed sexy, they are girlfriends of people ranked above you. Leave code perfection for your projects.

I give math lessons to high school people in my "free" time. One of my guys needs to use calculator to compute sums with 0 and yet he wants to become a programmer 🤦🏻‍♂️🤦🏻‍♂️🤦🏻‍♂️

When you work hard for something and you are sure that you gonna get it, but some ass licking guy who doesn't even know how to code gets it. Yes, it happened to me. I was working for an open source organization called PROBOT. I was working my ass off to get into GSoC with that organization. I created PR(pull request) after PR and solved most of their issues. But later on, I came to know they didn't even saw my single PR. Life surely teaches you some hard lessons but it's you who should not give up I would say. I do not regret working my ass off and writing those code and not getting into GSoC but I cherish those moments where I learnt many new things. And as for that organization, I would say they don't even know how to manage. This was my exact reaction when the result came

My patience limits are huge but our product manager seems that likes to stretch them.

You piece of fuckin shit. You ask for feature A and we agree on the way we will do it. Good. Half way you want to change it's behavior.
Fine, i accept that. Let's move on.
I'm close to finish it and you come and say let's add more on that feature and make it more complicated. I can't say anything, just fine and let me work on it.
Then you and the senior dev that "helps" us don't come to 2 meetings and just communicate via emails.
And then, then you fuckin scums tell me that is unacceptable that i haven't finished it and it doesn't work?
I used my uni time and missed lessons to work on your shitty feature and that you just yell at me?
What about comming to the fuckin meetings so we can discuss what problems occured and how i can overcome them, you sucker?

Just because our boss complained to you that the product is late because of you, that doesn't give you the right to yell at me, you piece of shit.

And the next time you tell me that you pulled the repository and it doesn't work while it does on everyone else i will come and shove your laptop up to your ass.

To long to read. So don’t do it.

I feel disappointed. It’s not about job or stuff. I’m disappointed about world in general. I don’t see my future on this planet anymore.

The world more or less looks like that :

Politics are trying to help you by stealing more money from you. The more you’re lucky the more money you will pay for it.

Media punch you with some family stuff from everywhere, give you young rich and far away, beautiful picture photos of places, people and food that you at most could visit once or twice per year during holidays that are break from work concentration camps.

If you’re lucky you’re rich or got rich or wealthy and infamous so you can walk wherever you want and don’t give a fuck what you wear but again your old friends are not so lucky bastards so you need to find new friends that are probably assholes. At the end most of the days you you’re doing nothing except killing time to meet with people you like during weekends or evenings.

Then there are families and everyone want to tell you that’s important. Family is like herd of assholes, if you’re weak they will sacrifice you and tell that you’re looser behind your back but when you get wealthy they will come back to tell you that when you were young and stupid they played with you so now you have to buy them some stuff or get them a job.

At the end there are people with “I wrote that book” certificate of excellence try to sell you opinions on everything starting from sexual positions ending on how to take a good dump. The problem is that the moment they wrote that book it becomes obsolete. Teachers of useless knowledge from last century that forgot about google or wikipedia.

All of them are playing your emotions, cause impulses and hormones are what makes you weak and people are looking for your weaknesses to take advantage of you. Get your money or get your attention and maybe even both at the same time. Cause views matter you know it. So like and subscribe dumb fucks.

If you’re lucky you find couple of them who aren’t doing that. Who the fuck knows why but this shit happens. It doesn’t matter if they’re family or you met them month ago. Those are only to keep and hardest to find. Unluckily those also can change by other people they meet or when they’re young.

If you can’t find a friend get a dog or cat or whatever animal you like. Their love is unconditional and obvious to read.

Well that’s most of the “I want to be spotted” culture that is all boring as fuck. Personalized ass and glamorous pictures and short movies of everything you don’t need but looks awesome. And as you see it’s still growing with more specialized portals like onlyfans, twitch and tiktok. We all need to look at what everyone else have or want to have cause 99% of time 99% of us are boring and is bored as fuck. Most of us can repeat same small amount set of stories all their life cause we’re not created to entertain.

I don’t feel joy looking at this shit fucked full of shit people arguing who’s dick is bigger. Who can post most dumb thing. I think I need a break but how to break from everything ? How to break from culture of money where to live on your country land you need to pay property tax ?

That’s all fucked up. Life’s fucked up.

I was laid off. The reason? Well, they didn't really want to say but they were clear it wasn't due to performance. (Thankfully, I got severence pay.) From my perspective it really came out of nowhere, no warnings or even hints that this was coming, which has me spinning. 😵 If I'm doing well at my job and the company is doing well, how in the seven hells could I get laid off??

What they said was partly the reason didn't seem true, or not the whole truth. They essentially stated that "they talked with everyone I worked with" (probably not true based on their decision, but who knows) and came to the conclusion I wasn't suitable to work on large teams, and that's the direction they are moving in. As if it wasn't something that could be improved on 🤔

I'll be the first to admit I'm not the best communicator face-to-face, mainly due to my social anxiety but also because I have too many thoughts. It can be difficult to condense them down for other people in the heat of the moment. (I'm an INTP, if that helps you to understand what I mean.) However, I know I'm a pretty good communicator overall since I listen and pay special attention to phrasing and word choice. So most people I worked with there seemed quite satisfied with communication with me. There were only 2-3 out of more than 12 who I had any difficulty working with.

So why did I have trouble properly working with a couple people? I hesitate to say this but, like other jobs I've had, well... they didn't have either the experience or knowledge to understand me. Basically, they were stupid. I was pretty frustrated working with such inadequately prepared people on a complex project with ludicrously short deadlines, and had no desire to work overtime so I could educate or guide them.

To give perspective, one React developer didn't understand how object properties work with JavaScript. 🤦‍♀️ (They are references, by the way. And yes you can have an object reference inside another object!) Another React developer thought it was okay to have side effects during the render lifestyle because they didn't affect the component itself, even if it was a state change in a parent component. 🤦‍♀️🤦‍♀️

So what is the real reason I lost my job, if not performance? Could be I pissed off the stupid (and loud) ones which hurt my reputation. My main theory, however, is that I was raising the cost of the company's healthcare. I had a diseased organ so I did miss some work or worked from home more than I should have, and used my very good health insurance to the fullest extent I could. Of course, if they say that's the reason then they can get sued.

Huge bummer, whatever the case. I definitely learned some lessons from this situation that others in a similar position could find useful. I can write that up if anyone expresses interest.

Honestly though, this is a good thing in the end, because I was already planning to leave in a month or 2 once I found a better job. I was waiting for the right time for the project I was on and for my own financial stability. So I'm trying hard not to let this affect my self-esteem and think of it as an opportunity to get my dream job, which is working with a remote-first company that is focused on improving the human condition.

Being unemployed isn't ideal, but at least I didn't have to quit! And I get to have a bit of a vacation of a sort.

Lessons I've learnt so far on programming

-- Your best written code today can be your worst tomorrow (Focus more on optimisation than style).
-- Having zero knowledge of a language then watching video tutorials is like purchasing an arsenal before knowing what a gun is (Read the docs instead).
-- It's works on my machine! Yes, because you built on Lenovo G-force but never considered the testers running on Intel Pentium 0.001 (Always consider low end devices).
-- "Programming" is you telling a story and without adding "comments" you just wrote a whole novel having no punctuation marks (Always add comments, you will thank yourself later for it I promise).
-- In programming there is nothing like "done"! You only have "in progress" or "abandoned" (Deploy progressively).
-- If at this point you still don't know how to make an asynchronous call in your favourite language, then you are still a rookie! take that from me. (Asynchronous operation is a key feature in programming that every coder should know).
-- If it's more than two conditions use "Switch... case" else stick with "If... else" (Readability should never be under-rated).
-- Code editors can MAKE YOU and BREAK YOU. They have great impact on your coding style and delivery time (Choose editors wisely).
-- Always resist the temptation of writing the whole project from scratch unless needs be (Favor patching to re-creation).
-- Helper methods reduces code redundancy by a large chunk (Always have a class in your project with helper methods).
-- There is something called git (Always make backups).
-- If you don't feel the soothing joy that comes in fixing a bug then "programming" is a no-no (Coding is fun only when it works).
-- Get angry with the bugs not the testers they're only noble messengers (Bugs are your true enemy).
-- You would learn more than a lot reading the codes of others and I mean a lot! (Code review promotes optimisation and let's you know when you are writing macaroni).
-- If you can do it without a framework you have yourself a big fat plus (Frameworks make you entirely dependent).
-- Treat your code like your pet, stop taking care of it and it dies! (Codes are fragile and needs regular updates to stay relevant).

Programming is nothing but fun and I've learnt that a long time ago.

Rant!

Been working on 'MVP' features of a new product for the past 14 months. Customer has no f**king clue on how to design for performance. An uncomfortable amount of faith was placed on the ORM (ORMs are not bad as long as you know what you are doing) and the magic that the current framework provides. (Again, magic is good so long as you understand what happens behind the smoke and mirrors - but f**k all that... coz hey, productivity, right?). Customer was so focussed on features that no one ever thought of giving any attention to subtler things like 'hey, my transaction is doing a gazillion joins across trizillion tables while making a million calls to the db - maybe I should put more f**king thought into my design.' We foresaw performance and concurrency issues and raised them way ahead of the release. How did the customer respond? By hiring a performance tester. Fair enough - but what did that translate into? Nothing. Nada. Zilch. Hiring a perf tester doesn't automagically fix issues. The perf tester did not have a stable environment, a stable build or anything that is required to do a test with meaningful results. As the release date approached, the customer launched a pilot and things started failing spectacularly with the system not able to support more than 15 concurrent users. WTF! (My 'I told you so' moment) Emails started flying in all directions and the hunt for the scapegoat was on (I'm a sucker for CYA so I was covered). People started pointing in all directions but no one bothered to take a step back and understand what was causing the issues. Numero uno reason for transaction failure was deadlocks. We were using a proprietary DB with kickass tooling. No one bothered to use the tooling to understand what was the resource in contention let alone how to fix the contention. Absolute panic - its like they just froze. Debugging shit and doing the same thing again and again just so that management knew they were upto something. Most of the indexes had a fragmentation of 99.8% - I shit you not. Anywho, we now have a 'war room' where the perf tester needs to script the entire project by tonight and come up with some numbers that will amount to nothing while we stay up and keep profiling the shit out of the application under load.

Lessons learnt - When you foresee a problem make a LOT of noise to get people to act upon it and not wait till it comes back and bites you in the ass. Better yet, try not to get into a team where people can't understand the implications of shitty design choices. War room my ass!

Bugs in code are like heartbreaks in humans. They suck, but they also teach you some important lessons 🤷‍♂️

I need lessons on how to be a developer and have a girlfriend

I'm not going to have a lot of new friends here but I am fed up with all those guys complaining about CSS on devRant.

CSS is damn easy. Get over it. Take some lessons, learn it the right way and shut your mouth.

I'd prefer you share your enlighten opinion on CSS in JS with React Native or CSS compositing with ReactJS which are both huge pain in the ass.

Plain CSS isn't the cause of all your pain. You are.

#1 Take French language lessons to revive my long time ago knowledge.

#2 Read as many as I can books on dev topics

#3 Do more outdoor activities (sports)

#4 Liquidate my fucking bank loan

#5 Buy some nice wheels for my car

#6 Try to socialize more

#7 Be part of aiding childrens in need / abandoned ones

We should start with demystifying tech...
For most people, modern phones, tablets and pcs are magical rectangles...
The law of Clarke says, that every sufficiently advanced technology is indistinguishable from magic.
And we have to tackle that.
In geography, we should talk about gps and glosnas
In English or foreign language lessons, we should speak about translator bots and language patters/abstractions
In physics, we have to understand the measurement devices
In politics, we have to speak about licenses of use, we have to speak about netneutrality as a political concept, we have to speak about snowden, shadow brokers, the vault, all the laws some shady imperial beauroticians pipe into our life.
Trojans used by the government and so on...
In cs concepts of operating systems, abstractions and networking should be taught, instead of using excel.
That could be done in math...
Well... No one should have to work with excel.
In maths they could use Wolfram alpha, rlang and gnupolt for example

Today in development: discovered that it's possible via combination of keys to rename a database in SQL Server Management Studio without as much as a dialog box to confirm.

Shout out to the 2000ish users in production that discovered this delightful nugget of info with me.

Lessons learned:

A) Don't trust Microsoft to create software that makes you confirm potentially catastrophic actions

B) Make sure your user hasn't been granted ALTER DATABASE permissions without your knowledge before you start using it.

In my school, eleventh grade (so nearly "Abitur", A levels), we got the task to create a program which will be running on every computer here which should replace the Classbook (like a book where homework and lessons and stuff is written down).
Now, the class before mine already did a part of that, a program to share who is ill/not at school, with a mark whether it is excused or not.
So far so good. They all seemed not that bad when they were presenting it to us. Then, the first thing: they didn't know what git is. Well, okay I thought.
Next, there was this password field to access the program. One of them entered the password and clicked enter. That seemed suspiciously fast for an actual secure login. So fast, the password could have been in the Code...
Yesterday I copied that program and put it into a decompiler.
And... I was right.
There were the login credentials in plain text. Also, haven't thought of it but, IP address + username + password + database name were there in plain text, too.
Guess I am going to rewrite this program down to the core

Don't start with Java but something simple like Python or Ruby or anything that doesn't need that much blob too run a Hello World! program. That was what confused me the most. And by 'start' I mean like the first few lessons, just to get started.

I have a guy sitting next to me in class. We were working on the same project. It's about rewriting a functioning mergesort algorithm in C and doing a presentation about that topic.

Now... the thing is that I was ill on that specific day when we got that project assigned. And he didn't tell me it either. I asked the whole class.
They just said that there was nothing special about that day. These fuckers.

Anyway...
Thé following week we had the same lesson again. Actually there were more than both of us. We were a group of 5 dudes.
3 of them barely have anything to do with programming at all. They just learn for the exams and have bad grades in programming.

Luckily, they already wrote the functioning sorting algorithm.
Since that is the case, I chose to review it to get deeper into that topic.

There were comments in English (we live in Germany) and these comments were written in a different style. My classmates would never comment in such a way.
It was a modified version copied from the internet. The whole source code.
The variables had names like j,k,b,u and so on. It was perfectly obfuscated.

Yesterday, I wasn't at college either.
I had to show up to a given time at a government bureau. They have been working on that project that day. So, I decided to ask them via a messenger, if they can give me the newest presentation files after 1 pm.

They said that they barely have anything to present. They would like to improvise they said.

"Fuck you all" I thought.
I'm done with these fucking illiterate humans.
I hope they all die in hell with satan having a ride on them. Stabbing them from behind right into their assholes and eating their ball sacks (if they have any).

Today is the presentation.
That's when I decided not to drive there during these specific lessons.

Most Incompetent co-worker. It was me during my first job. Not humble bragging or some shit. I was straight out fucking incompetent during my first job.
Hear me out.
I graduated my diploma course specialising in networks(from computer to cellular/telecom networks) but I did a few programming courses and my internship was at a lab - did iOT stuffs with raspi and arduinos. I am a A+ student so was giving priority to choose a better internship place. Fun time. So I fell in love with programming. As soon as i graduated I applied for a Java job. Got a job at a domain name reseller/hosting company using java EE. Remember my programming = very basic/OOP concepts/basic SQL knowledge. That's it.
I am that little childish fucker who thought he knew everything and I kept interrupting my coworkers with stupid questions.
Same time, I was under the darkest moments of my life with some family drama/tension headaches.
2 months into the job, one coworker really got pissed off with my interruptions and bluntly told me "*my name,you are stupid aren't you"
The manager was a really nice guy. I will forever thanks him for his advices. He knew I was struggling with family shits and gave me another 3 months probation period to redeem myself. But I gave up. That was back in 2015.
It was a great place I fucked it up. But I learnt precious life lessons. I was young,stupid and didn't know how to handle stress.
I thanks myself for not quitting programming after that experience.

Boss wanted me to make changes in company's website which was based on wordpres s.

I knew it could be done by tweaking some JS code, but I have very less experience with wordpress

But wordpress is easy man(Internet told me).

Give me 5 minutes, you will see the changes in production.
Being lazy af I directly logged in to ftp, checked out some files, updated some code, I was good to go.

Before pushing it, I opened the website and it was GONE ٩(๑´0`๑)۶

Now there was no public_html in the root.
I was fucked. I have accidentally deleted the website that had no backup.

And the best part I was on leave from
next day.

I was looking everywhere for backups, looked into google cache to get the contents. I have to recreate the complete site now.

Just when I was asking questions on choice of my profession and simultaneously looking here and there in FTP for backups,
I found the jewel "public_html".

It happens out that I have accidentally moved the folder to some other directory.

Phewww.

Moved it back to root. Site was up and running.

Reassured myself that I deserve to be a dev.

Backed up complete site, made the changes.

Uploaded it.

And the best part, amount of wordpress I learned in those three hours was way more than I could have learnt in many weeks.

Lessons Learnt :

A) ALWAYS keep backups.
B) You SHOULD NOT make changes on prod directly
C) You become superhuman when your brain know you are going to be fucked 😂

Blue Robotics

This company makes underwater thrusters for submarine applications. With their first thruster they made it easy to make a homemade submarine. The motor was powerful, the thruster just worked. They even had a promotional where they created an automated surfboard that made it from hawaii to somewhere in california with one of their thrusters pushing it there the entire way. It was a great product.

Then they created the next version. This was the same thruster, but it had an ESC(Electronic Speed Controller) sealed in an aluminum puck on top of the motor. This ESC could be controlled by servo controls, or by plugging it into an i2c bus. You could pull different stats off of the motor over i2c it sounded great. So my robotics team trusted this company and bought 8 motors at $220 - $250 bucks each. We lightly tested them since we had not even finished the robot yet. One week before the competition our robot got completely put together and we did our first few tests.

Long story short, Us and 22 other teams did roughly the same thing. We bought these motors expecting them to work, but instead the potted aluminum ESCs were found defective. Water somehow got into the completely resin sealed aluminum puck and destroyed the ESC. We didn't qualify that year due to trusting a competition sponsor to deliver a good product. I will admit that it was our fault for not testing them before going to the competition. Lessons were learned and an inherent distrust of every product I come across was developed.

PC survival lessons
1. Tape acts as a protection from extreme animals like humans bashing you up and falling apart into pieces
2. Repeat lesson 1 for eternity

I recently finished one year in the industry as a Software Engineer for a solutions development startup. Here are my top 10 learnings:

1. It's okay not to know everything, as long as you're willing to learn passionately.

2. Focusing on the customer experience is the number one priority in software design.

3. Imposter syndrome and fear of failure are real, but a little bit of toughness is all you need.

4. Lack of work is more frustrating than the excess of work. No two days are similar.

5. Working at a startup has taught me more than what my friends at tech giants have learned.

6. The feeling of recognition and appreciation will set your trajectory to constant improvement.

7. Asking for help is completely normal, only if you've exhausted all your research and online resources.

8. Mentoring or generously giving back to the community is super underrated.

9. Taking ownership and responsibility of failures is equally important as for successes.

10. Taking up tasks that interest you - outside your job description - is never a bad idea.

Built my own IoC container for C#. This taught me way too much about SOLID principles and dependency injection that i could give lessons now 😂

I'm still using my own IoC in my projects... It's great 🤘

Don't be a dumbass and use your 2.4Ghz WiFi and airpods at the same time.

Lessons stux learns at 4am.

I gotta say, I actually admire the work that content creators must go thru to make quality content.

So as I stated before I’m working on YouTube channel, under the name “TheSoftwareSage” ... to create tutorials and a way of me teaching software the way I believe it should be taught, not how the mainstream methods of today are.

Bottom up approach rather than top down

(Must start with a firm understanding of the foundation.. and build upon the knowledge as we go thru the layers of abstraction but the key concepts must be understood first)

Anyway, I’m working on this in my spare time and I was not aware of how much effort I would actually need todo this right haha. At first I figured I’d just screencast a monitor and have a ppt or text editor or terminal open and that stuff and just do it.

As In person with my interns I never have “planned” lessons or content is all impromptu based on the need at the time and I just go with it, with their computers and a whiteboard lol.

I was wrong for video recording lol... maybe it’s OCD... or perfectionism, I’ll make a video, review it like 5times and then be like shit I forgot to mention this or that or I didn’t like how I explained this or that
OR
I keep worrying too much about colors, and sound levels and quality and transitions and video angles and all this other shit.
And then post editing fuck.... I’m about ready to say fuck it and “do it live .. one shot” and just upload the end result.

I guess this would be in the content world similar to our “paralysis analysis” notion.

Today was my last piano lesson with my jazzy teacher. I'll miss him. He teached me a lot and I nearly always looked forward to piano lessons.

I brought wine (Mosel life) and 5 songs - 3 jazz classics (It don't mean a Thing, Take Five and Fly me to the Moon), his favorite from the Daft Punk album I borrowed him and one of his own songs (surprise) and we improvised on these songs. I was a little nervous.. or sad but I didn't play as good as yesterday eve. He asked me why I never did that before. He'd love to practice improvising with me because I suck at reading sheet music (I said that and I'm a lazy learner with sheets).

R.I.P. Monday afternoon.

When I was studying computer science at university (second year). There was a girl, I'm not sure if she was crying or angry after this, but I didn't expect that.

Just to put some context, this girl was still asking "what's the meaning of i++?" in second year. And during a re-sit exam, the teacher who was asked the previous question, was the one who monitored the students.

And the girl made a mistake (it was something usual though) . She asked the teacher something that she didn't understand. Which means that she wanted the teacher to help her with the exam, but I'm not even sure that she realised that. And the teacher said : "You still can't do that? I gave you this exact problem during lessons and also at the first exam! Well don't worry... I'll give you the same next year :) "

Not really nice for the girl, but hopefully I didn't hear it directly or I would have laugh a little too much x)

So I finally got around to rewriting the Java course that my school has. It took me 6 lessons to get "Hello, World!" into the course. Well it looks like its going to be a long course.

So last week I really fucked up

I had this new implementation that was supposedly to be integrating smoothly into the rest of the service. It depended on a serialized model made by a data scientist. I test it in local, in QA environment: no problem.

So, Friday, 4pm, I decide to deploy to production. I check once from the app: the service throw an error. Panic attack, my chief is at my desk, we triy to understand what went wrong. I make calls with cUrls: no problem. Everything seems fine. I recheck from the app again: no problem.
We dedice to let it in prod, as the feature work. I go get some beers with the guys, to celebrate the deploy.

Fast-forward the next morning, 11am, my phone ring: it's a colleague of my chief. "Please check Slack, a client is trying to use the feature, it's broken"

FUUUUUUUUUUUUCK!!!

Panic attack again. I go to the computer, check the errors: two types of errors. One I can fix, the other from a missing package on the machine that the data guy used.

Needless to say, I had a fairly good weekend.

Lessons learned:
- make sure Dev, QA and Prod are exactly the same (use Ansible or Container)
- never deploy on a Friday afternoon if you don't have a quick way to revert

My first dev job is my current job, but I'm leaving it tomorrow to go on on an internship overseas, then return my focus to completing my Computer Science bachelor's degree and getting into a Master's program.

Before this job, I was an office assistant at a small company that sold cosmetics products and fragrances. I had just returned to college after a 1.5 year hiatus and was tired of that job. I wanted to get into the field, even though my experience was limited to freelance web design and a few personal programming projects of which I no longer had any proof, and I still didn't have a degree, but I wasn't confident that someone would contact me. Yet I decided to update my resume and upload it to Indeed.com. I was already getting interviewed at a call center when this local tech startup called, and 2 weeks later, I had the job. We were 3 employees and I was, not only the first woman in the team, but also the first person to ever get hired by the directors without a college degree. Today​, I still hold those two titles and the team is 3 times bigger.

It was a very bumpy ride, and tomorrow I move on to other adventures, but I'll always be grateful for the opportunity, all the lessons, and the best team mates I could ever have. Without their wisdom and guidance, I wouldn't have half the blessings I have today. I will miss them dearly, but I know we'll stay friends.

Here's to better things and to a college degree! <3

A while ago I stumbled upon this cheap vps provider called dedistation (lowest was $15/year), so I end up buying a one year subscription and transferred all of my personal sites to it. Fast forward six month later, uptime robot notified me that my vps is down. No problem, I'll just submit a ticket. Few days go by and I yet to receive a response. Not a problem, I'll just try and login via the serial interface and get my shit, no luck there either.
Seems like these motherfuckers just packed up and went offline without a shit given.
No response, no notification untill today! How more twat a company could be?
Lessons learned the hard way
- always backup regularly
- check and transfer nameserver or no emails for days.
- you get what u pay for (haven't learned this fully yet. Went again with a cheap legit-ish provider (arubacloud)

My lessons both come from my current side project (I will share it with you in a week or two, the website isn't finished yet):
1. Every project comes to the point where it hurts to continue. Keep pushing, the result is worth it.
2. You aren't as good as you thought you were when you started, but you'll be better than you ever were when you finish.
3. Sometimes, there's more points to a list than you'd expect.
4. One hour per day is easier than five hours a week.

How?
Well. I started out my project knowing some C#, but Jack shit about unity. I know most of what I might build will end up being shit I'm gonna regret, refactor and recycle later. But I don't give a fuck. Doing it is better than planning it.

It sometimes hurts to get rid of a carefully planned algorithm that took hours to build because it fails in practice. But it's the right thing to do.

Never plan too much. If I'd have planned this project out, I wouldn't even have started with what I'm good at: write code, break shit and experiment.

It's easier to progress slowly but steady. Look at some awesome games that have been worked on for ages while the public had their say (RimWorld, Project Zomboid, Dwarf Fortress...) as opposed to those that are developed behind closed doors and rushed to the market before Christmas or some other major event (Mafia 3, Fallout 76, Fallout 4 VR...). Progress slowly, deploy early, push often. And the one hour per day approach is a good way to do this.

Shortlisted hackathon apps:
1. Transmit strings between two phones using sound.
Why the fuck? Why are we reinventing the wheel?
2. Offline payment services app. Sounds cool but is no way feasible in the real world.

The judge of the hackathon was some old PhD college professor who was yawning at the begining of the presentation who didn't understand what was heroku and didn't even bother to listen.
Lessons learnt:
1. Stick to corporate hacakathons
2. Query regarding the judges of the hackathon

Jared wtf were you thinking! He is a wild man 😊 Final 5 minutes thru rolling credits was very cool.
Lot of communication and usability lessons to be learned during the episode.

Season finale next week. Can't wait!

Life lessons learned from programming?

1. Always put things where you look for them
2. You may know better than some people but you never know better than all the people
3. Fuckups happen. Deal with them and move on
4. Take responsibility for your fuckups
5. There is no nice way to tell someone their baby is ugly or that their code is unreadable

How to program in 4 easy steps

In the first two years at my school, I'm gonna do much stuff in the programming lessons that I already know. That's going to be boring. Very boring.

to;dr: school, raspi, spoofing, public status screen, funny pictured.

So. At school we had these huge ass 2/3 TVs displaying some information such as which teacher is ill, which lessons won't take place and some school related news. Standard stuff.

They worked using a raspberry pi attached to the TV fetching a website over http every now and then.

Using nmap I discovered that these pi's were in the same network as the pupils devices: Sweeeet.

After trying some standard passwords at the ssh port and not succeeding I came up with something different: A spoofing attack.

I would relay all traffic from those pi's through my device, would replace all images with a trollface picture (I know I know) and flip all text upside down.

Chaos, annoyed faces and laughter.
It was beautiful.

Ascended Anime Nerd

Got started with Dragonball Z when it first came stateside. Brother was borrowing fansubs of the Cell and Buu sagas back when people were wondering if Goku would ever finish Snake Road.

Around that time I started noticing some serious discrepancies between the broadcast translations and the fansubs, and so I decided to cut out the middleman—after all, how hard can it be to learn Japanese?—and did a search on AltaVista for a “kanji course”, turning up a course hosted by Rice University that taught basic Japanese using Magic Knight Rayearth and YuuYuu Hakusho.

Turns out the answer to the difficulty question is that anything van be simple to learn, if you don’t know it’s supposed to be hard. Especially if you embrace the parts everyone else dreads (falling in love with kanji, in my case).

Over the next nine months I ditched my Spanish class—and all my other classes, for that matter—to study Japanese in the computer lab. I was reviewing the lessons, playing JRPGs on SNES9X (stored on a ZIP disk, since every computer in the lab had a ZIP drive), and transcribing the scripts so I could transliterate and translate them thereafter. In a lab that went so far as to uninstall Minesweeper and Solitaire to discourage playing games on school computers, I had free reign to do so openly because the one time I got confronted for playing a game I had 150+ leaves of handwritten transcriptions to show them.

Long story short, by the time I took Japanese 101 9 months later it was like Hermione in Snape’s potions class, since I had already taught myself about 2 years’ worth of material. I then transferred out to a college that did a one-class-per-month “modular” system that basically allowed me to take 8 more Japanese classes full-time for the following year. By the time my exchange trip came up I was sofar ahead of the curriculum I was taking classes alongside the native Japanese students.

Running out of linguistic topics, I did an independent study on classical Japanese literature in its original, unmodernized grammar and orthography. A topic I’m still fairly active with 15 years later.

Hi everyone, long time no see. Hope you're all doing fine! 💙

Here's an actual rant: I don't know if I chose the right university course, anymore.
I chose "Informatics", but there are so many subjects that aren't even related to Informatics, and still I have to do them because that's how it is. I just wanna do programming, because I like the creative aspect of it.
I'm getting sick of this to be honest... I'm at my second year, now, and I feel like maybe... I should've just studied programming on my own, and seek a job without going through university.
Though, that being said, I may just be temporarily having a bad time. I don't know, ok?

It seemed I did okay, in my first year, I completed 4 exams out of 7, but now I don't know anymore.
The exams for this semester's subjects are coming up in a couple months, and I haven't exactly learned much, y'know...? I couldn't follow most of what the professors said in the lessons, for whatever reason (some professors talk too quietly, some don't explain well, etc.).

What was your experience with university, if you ever went there? Did you find it helpful, or was it a waste of your time?

Thank you for reading. I hope my next post will be more joyful, sorry for being like this. Love you all! 💙

Day 1 of a new semester in college. Our 50 yr old H.O.D is a guest lecturer of this new subject called "Industrial Management" (why its included in the syllabus of CSE degree i wonder) . As there were only 6 students , the guy went on like a drunkard telling life lessons :

1) only 20% of the people in a company are only working. Rest 80% of them are just using sugar coated words at the right place ; doing politics and taking credits of the others .

2) those 80% getting benefits are usually the bosses (and in his example, the senior deans and H.O.Ds buttering the administrative dept and director ) and the hardworking 20% are the Juniors or the new joiners ( and in his example, the latest recruited ,honest teachers. Makes sense why we have shitty teachers :/ ). They altogether make sucesses to the company(although its just those 20%hardworkers doing the actual job) . But at the time of salary everybody gets the benfit.

3) Its always perfect to throw blames at senior or junior. (explaining how a parent complaining about the poor study environment to director is made to think that it's only the fault of his own child. blames going from director to dean to HOD to teachers to your own child's mistakes.)

4) Being your boss's favourite is super important. He gave example as : 2 teachers meets him with 100% results and 100% reviews. One of them is a known asshole with 0 knowledge, who makes jokes and sexist comments during the class, gives free attendence and question papers before the exam{therefore 100%reviews} . But he is dean's great ass-licker . The other one is honest hard-working teacher with real reviews and results. So he says he shows their combine results to the director along with his own buttering and ass licking, gets a hike himself and permit to give hije to one junior teacher. And who would it give hike to? The ass licking asshole, because that's how it works. What about the honest teacher?what reply would he get? Simply, appreciations and sugar coated words : "thank you for working so hard. But you did not do anything new. You were only hired to DO hardwork and give good results"

( and i was like fuck? Like seriously? Because that is something resonating with what i once heard in my internship :"yeah you are developing nice and all good, but that's what you are expected to do. You were only hired to achieve results, and you did nothing new". So that's what we are missing? Ass licking?-_- )

5) He believed its important to "look working" than being "actually working" . Quoting an example from his days as a dev, he told a story about how he once worked on a project with deadline of 1 month . He was young and worked hard and in 2 days completed the complete project and accidentally reported success to boss instead of his seniors. The boss simply congratulated his team(seniors and him) and assigned them another project. Later that day , he got an ass-wipe scolding from his seniors that if he had kept his mouth shut, they would have simply watched movies and relax for next 15 days, and submit the project during the salary time to gain bonus attention.
He even gave his short mantra or principle for such situation "kaam ki fickar kar, fickar ka zickar kar, par kaam mat kar " (get worried and tensed about the work. Display your tention and worries to the world (esp bosses) . But don't work.)

And there were many other short stories like that.

Mann, i was about to shout " you corrupt asshole ", but one thing He just told us about the importance of being in boss's good books made me stop ( nd he is a fucking HOD, senior to teachers)

But hell he told some relatable truths. Make me sad about the job life.

Bloody Office politics :|

Best: discovering devRant and meeting lots of cool people, switching to Linux as well

Worst: the programming lessons in school

It's over.

I've been working on you for months, and thinking about you for near a year.
I built you with a shitty language first and some crappy ideas. I obviously got bad results, but I didn't lose courage and I continued you.
Got near the obsession to improve you. Every time. Switched to a fast but hard language. Got into my first low-level fuss. All for you.

Now I reached the end with no more improvements and tweaks I could imagine, I can tell that:

I had a lot of expectations from you.

But turns out you were nothing more than a nasty brain fart pretending to be a good idea.

The core of the concept was rotten. Blinded by my lust for success (perhaps cupidity ?) I didn't see you just couldn't work.
I'm utterly disgusted, of course. Who wouldn't, after working so hard on something that looks right but is completely useless ?

But even though this was all in vain, you taught me some great lessons down the road.
Efficiency matters over facility.
Get sure you're using the right tools, and stay open for changes of such.

But some others were harsher, though just as important.
There's times you just have to admit defeat.
Putting a lot of efforts into something doesn't always bring a reward.
If after a long time you can't get the thing right, then stop. Your time is precious. Don't waste your time or time will waste you (Thanks Muse, I love this sentence).

And the most important: next time I got some "grand" idea that is not about improving some random software, I'll bang my head to my desk enough times to forget about it.

So now the time has come.

Goodbye, project "hpym". You put me in grief, but I know I matured a lot in my concepts of development because of you.
Now take place into the project graveyard among the other clunky half-assed shit I got rid off.

Finally getting my first certificate in Udacity , which is a website where you can have courses in coding 🚶🏻‍♀️💕...
In order to get it I had to first learn the lessons there and then do a final project which involves all the things I learned which was HTML and CSS in making and designing websites in browsers 🍃

I can’t say it’s the most painful but it’s one of my recent painful lessons.

So I’m learning C and in my project I was trying to make a copy of a 2D array and I kept getting seg faults up the ass every time I tried to allocate one of the inner arrays and after a long day of debugging I realized that I was trying to allocate memory within an array that doesn’t exist so I had to create the first array then allocate memory for each inner array after.

***ILLEGAL***
so its IPL(cricket) season in india, there is a OTT service called hotstar (its like netflix of india), the cricket streams exclusively on hotstar..
so a quick google search reveals literally thousands of emails & passwords, found a pastebin containing 500 emails&passwords ...but those are leaked last year most of passwords are changed & many of them enabled 2FA.. after looking through them we can find some passwords are similar to their emails , some contains birth year like 1975,1997 etc, some passwords end with 123 ..so after trying a few different versions of the passwords like
1) password123 -> password@123, password1234
2) passwordyear -> password@year
2) for passwords similar to emails, we can add 123 ,1234, @ etc
created a quick python script for sending login requests

so after like 30-40 mins of work, i have 7 working accounts

*for those who have basic idea of security practices you can skip this part

lessons learnt
1) enable 2FA
2) use strong passwords, if you change your password , new password should be very different from the old one

there are several thousands of leaked plaintext passwords for services like netflix,spotify, hulu etc, are easily available using simple google search,
after looking through & analysing thousands of them you can find many common passwords , common patterns
they may not be as obvious as password ,password123 but they are easily guessable.
mainly this is because these type of entertainment services are used by the average joe, they dont care about strong passwords, 2FA etc

We were a small startup with only 5-6 developers. I had to design the UI and develop most of the Android frontend, It was quite an easy and fun job for me because I don't get to see people rant about the design that needed to be implemented so, usually I design something that can be easily implemented.
We got 2 projects with a tight deadline and I took care of both project's design part and after completing the design I took the entire frontend of one project and rest of em started working with the other one. Usually we were a strong team and was able to deliver things real quick because we were expert in our intrested fields, I had a fast start in my project where the other project lagged a lot because of the desifn which was hard to implement by them, and the frontend was bo where near to get completed by the deadline and I couldn't help them out because it was all messed up shit handling both projects together.

Finally we were in a situation where none of our project are ready and the deadline was about to hit within a week, so we halted the other project and asked them to join me to complete the project am Working on, I had built most of the Android part and these fellows had a hard time figuring out stuff I made up (yeah, documentation was shit while you go agile), and finally things messed up and I had to work 2 continuous day and night without any sleep just to get the app ready 10 minutes before the official proto presentation.

The best part is I couldn't even get up from my chair and had a headache, fainted instantly when I took a few steps, but the product launch went good.

We fucked uo the code and both the projects just because we weren't available for each other considering the size of the team. Anyway we completed the project but It was a huge failure for us being first time to manage a startup.

Learned a lot of lessons,
Always make a team with people who are good at each of the aspect of development and never divide it to get shit done faster.

!rant

I think that one of the most useful things programming has taught me is how to use Google.

Several years ago, I heard from a friend who was doing assignments for students on the side. Quite a hustle. His story began when he wanted to figure out why can't these students be able to draw their own database tables, relationships, UML, etc. That's what school has to be teaching them and then he was told that they were learning through MS Access. He goes and tell me that even though this is a lame way of teaching database design, its definitely easier to explain through hands-on and less typing mistakes, as according to the lecturer he met. Making the explanation more visually appealing and helpful for understanding.

OK I get it, but somehow that taught them the wrong way of database design from the beginning. I'd prefer getting them to start writing SQL commands from day 1 and play em at some DB VM. Keep em as real as it gets.

Now I have my own students asking for help in their assignment and also asked for tutoring lessons in web development. So I gave them the crash course in HTML, CSS and Javascript. I've asked them if they've used anything of what I taught them in school. They go and tell me that they've been taught web development through Wordpress. Oh WTF!? I havn't talked to their lecturer yet but it better be a really good explanation to teach these youngsters in a flawed and bloated PHP CMS framework for "web development".

10 years as a developer and I still struggle to set up that fucking maven thing because those crazy college professors all use Java for lessons like "read a file and create an array with its contents". A shitload of boilerplate that I could've done with 3 or 4 lines of js, python or whatever else. Decided to skip all of them and focus on the tests to compensate the missing grades.

RDBMS class: I have to fucking attend every class even though our lecturer just reads slides from Oracle to us.

In order to pass that module, we have to take the exams on their shitty website full of stupid questions, I.e. "Oracle academy is beautiful? a) true b) false" (I put false and they obviously marked it as wrong, ffs).

Multi-user operative systems: I was the one teaching our lecturer stuff on Linux.

WHY THE FUCK I CANNOT STAY AT HOME AND BE FUCKIN PRODUCTIVE INSTEAD?!

The only fucking interesting class is Data Structures & Algorithms and they pretend that we also attend every other useless class. FUCK YOU!

PS: I know the 90% of the stuff they are trying to teach us because I actually want to learn something and I know how to use Google, but no, I have to waste 2 hours on the bus every single day I have lessons.

you know when you start with computer at 9 years old... and you hate calligraphy class and typing feels the same and thus you skip it and now you are hitting a wall because you are not using enough fingers to be more productive at the keyboard!! 😡

I right now have a rag over my hands at the keyboard and am taking typing lessons... and my brain is not happy about it!

Lessons learned

I'm working as a tutor for two classes. Students are 11th graders, smart and curious as hell.

We get to the OS part of the course and they have to use WinAPI for now. The explanations in the lessons are vague and they are forced to use MSDN which also has either super-high-level or super-simplistic explanations. Don't know how to give them motivation for this crap.

Also, where is WinAPI really used? For writing drivers? Viruses? Relatively low-level software?

Coding for me has been such a heartache and a relief at the same time. Having an outlet for my brain activities has improved my mental and emotional health significantly.

It also thought me a couple of valuable lessons:

1. With enough efford you can accomplish pretty much anything

2. You're not the only one struggling with issues, life or code related.

3. Moronic people can be found everywhere you look.

4. Patience is key to grow as a human being.

When you're programming teacher manages to make the lessons so boring and long winded that every student with the slightest interest in programming loses it 😰

Lessons learned:

use tmux, screen or at least nohup with an unstable internet connection, when doing filesystem repairs... FS survived, but anyways

I thought the “works on my machine” from sysadmins is mostly a joke...

But no. I’m attending the Polish high school and I have a lessons via the Internet. I wasn’t able to hear the voice of the teacher on Linux 4.18 and Chromium browser, so I sent the mail to support to report it. Of course it “works on their machines”...

I want to kick this stupid kids ass!

So I'm on a Slack channel for live help for people who are learning JavaScript and I stick around and help people just while I'm by my computer. This kid is on there is constantly asking questions, which I don't mind but I mean I think part of programming is looking up the freakin info to figure it out occasionally. Anyways-

So in each lesson you watch a video ~10-15 mins long and then do an assignment. Well this kid constantly dm's me and asks me for help so I help him. Then as soon as he is done with that lesson quiz, 30 secs later I see him post a question from the NEXT lesson on the Slack channel. I'm like look you dumbass kid, you are going to have to learn this stuff. I mean for shit's sake! He is just on there asking questions for answers to the damn questions and not even watching the freakin lesson videos.

What a waste of my freakin time and effort to help this idiot. Plus there's a test at the end which no one can offer help on. So this dumbass is going to finish the lessons and then not know a damn thing in order to pass the test. I'm pissed that he doesn't even try and I'm over here helping him like an idiot. NERD RAGE!

Over the summer I was recruited to be a supplement instructor for a data structures course. As a result of that I was asked (separately by the professor) to be a grader for the course. Because of pay limitations I've mostly been grading homework project assignments. In any case, it's a great job to get my foot into the department and get recognized.

Over the course of the semester I've had this one person, OSX, named after their operating system of choice, who has been giving me awkward submissions. On the first assignment they asked the professor for extra time for some reason or the other, and that's perfectly fine.

So I finally receive OSX's submission, and it's a .py file as per course of the course. So I pop up a terminal in the working directory and type "python OSX_hw1.py". Get some error spit out about the file not being the right encoding. I know that I can tell python to read it in a different encoding, so I open it up in a text editor. To my surprise it's totally not a text file, but rather a .zip file!

I've seen weirder things done before, so no big deal. I rename the file extension, and open it up to extract the files when I see that there's no python files. "Okay, what's goin on here OSX..." I think to myself.

Poking around in the files it appears to be some sort of meta-data. To what, I had no clue, but what I did find was picture files containing what appeared to be some auto-generated screenshots of incomplete code. Since I'm one to give people the benefit of doubt even when they've long exhausted other peoples', I thought that it must be some fluke, and emailed OSX along with the professor detailing my issue.

I got back a rather standard reply, one of which was so un-notable I could not remember it if my life depended on it. However, that also meant I didn't have to worry about that anymore. Which when you're juggling 50 bazillion things is quite a relief. Tragically, this relief was short lived with the introduction of assignment 2.

Assignment 2 comes around, and I get the same type of submission from OSX. At this time I also notice that all their submissions are *very* close to the due time of 11:59pm (which I don't care about as long as it's in before people start waking up the next morning). I email OSX and the professor again, and receive a similar response. I also get an email from OSX worried about points being deducted. I reply, "No issue. You know what's wrong. Go and submit the right file on $CentralGradingCenter. Just submit over your old assignment".

To my frustration OSX claimed to not know how to do this. I write up a quick response explaining the process, and email it. In response OSX then asks if I can show them if they comes to my supplemental lesson. I tell OSX that if they are the only person, sure, otherwise no because it would not be a fair use of time to the other students.

OSX ends up showing up before anyone else, so I guide them through the process. It's pretty easy, so I'm surprised that they were having issues. Another person then shows up, so I go through relevant material and ask them if they have any questions about recent material in class. That said, afterwards OSX was being somewhat awkward and pushy trying to shake my hand a lot to the point of making me uncomfortable and telling them that there's no reason to be so formal.

Despite that chat, I still did not see a resubmission of either of those two assignments, and assignment 3 began to show it's head. Obviously, this time, as one might expect after all those conversations, I get another broken submission in the same format. Finally pissed off, I document exactly how everything looks on my end, how the file fails to run, how it's actually a zip file, etc, all with screenshots. That then gets emailed to the professor and OSX.

In response, I get an email from OSX panicking asking me how to submit it right, etc, etc. However, they also removed the professor from the CC field. In response I state that I do not know how to use whatever editor they are using, and that they should refer to the documentation in order to get a proper runnable file. I also re-CC the professor, making sure OSX's email to me is included in my reply.

OSX then shows up for one of my lessons, and since no one had shown up yet, I reiterate through what I had sent in the email. OSX's response was astonished that they could ever screw up that bad, but also admits that they had yet to install python(!!!). Obviously, the next thing that comes from my mouth is asking OSX how they write their code. Their response was that they use a website that lets them run python code.

At this point I'm honestly baffled and explain that a lot of websites like those can have limitations which might make code run differently then it should (maybe it's a simple interpreter written on JavaScript, or maybe it is real python, but how are you supposed to do file I/O?) .

After that I finally get a submission for assignment 1!

The school I went to, and this was really the only benefit of the school, gave all it students lifetime memberships to digital tutors, which was bought out by pluralsight, which then bought code School. So I basically got free membership to three different sites, all of which have a good amount of technical training with videos, guides, and work along lessons on them.

For what school cost to me, it will have paid for itself as long as I live for another Thousand Years.

Lessons learned with #reactnative
Easy to start...
Hard to finish!!!

Found this book amongst other 7 grade school books...
Fuck, kids are learning the basis for every technical job this days, in my time even chemistry was only theory... Let alone practical lessons

At math lessons I was like: "WTF is this shit, I don´t need that." Well I figured out that coding is not "copy&paste" from SO. :)

TL:DR Company partner screws up and doesnt do job. I start new company and now able to make ends meet.

My friend and me started this company together. Our roles were defined. I would manage the development of stuff and he would manage getting the clients. I did my job. About a year into the company. He goes ahead and partners in another company. Normally I wouldnt bother, but this is when he stops getting clients for us. Our business drops 50% in the second year. He doesn't work but expects to be paid the same salary as me. I'm doing all the work for the clients while he wastes his time with the other company. He manages to make money doing stuff and buys a BMW, while I'm struggling to make rent.
Finally in Dec last year, I plan to start my own company. And i suddenly have lots of work which pays decently well. I'm looking to hire and am not as stressed with work any more.
Moral of the story: if you must partner, make sure your partner is fully invented in growing your company.

Today something pretty bad happened (as always at school)
and I'm gonna rant about it to
1) get your expertly opinion on it
2) relieve from it

SOOOOO
today I entered class to paretake in the writing of the much anticipated class test (kappa).

The teacher gives everybody a sheet with the exercises - let alone me.

I tell him to give me a sheet too.

"Put a book between you and xy"

so I do. I ask him again to give me the exam paper. No response.

Again, and he looks at me with a disrespectful look. I look back. And get thrown out of the room - not getting a chance to paretake in the writing of the test yet getting the worst grade one could possibly get in the modest german education system (=> 6)

Now I'm going to pursue any possible legal action against him (I dont care about him. After the lesson I wanted to talk with him; yet he declined my offer for reconsiliation, then he called my parents, even though he had time to think about what he did {any sane person would agree that what he did was wrong <yet my classmates dont agree>}. Also, he is that type of teacher who gives unusually unnessecary homework - which I personally see as punition, since I already know 97% of the stuff thought in [english] classes)

See why I am despising school so much?

It drains my last bit of energy until I am an empty shell with the sole goal to finish education asap in order to be able to fucking work.

BTW: I tried using my best english in this rant to demonstrate my abilities in order for you to be able to see that I honestly dont those "basic" english lessons.

Second big school project. Designed for at least 2 people. Quite a lot of work for the given time but not impossible to do, as I thought. Oh boy was I wrong.

My partner and I chose a networking project which included setting up a ESXi-Server, a VM (with Windows Server 2008 R2) and a router. We are both not unknowledged so I thought this would be easy-going.
I quickly recognised that my partner liked to spend his time at home rather than actually doing something so I ended up doing nearly everything.
When it came to documenting everything he tried to write something, but it had so many mistakes i had to correct it over and over again.
I asked him multiple times, if we should split and he denied every time and promised to work harder.
End of that story was him being expelled from school because of to many missed lessons and me finishing the project alone. Got a B+ for it.

NAS.

New PSU. ( After careful research to choose the least troublesome model.. )

3 days pass . . .

Fire...

Smoke alarm = 1ft from NAS..

NAS data on HD, slightly inaccessible...

Everyone told me, I shouldn't being using an old laptop with HD's hanging off it, just because its so easy to get the data off when the laptop dies..

A NAS is better..

Until it dies..

Also, first PSU I had catch fire..

Fuse in the plug did nothing, fuse in the UPS did nothing, short circuit protection in the PSU did nothing, it just sat there melting, on fire, producing sparks and smoke, until I unplugged it.

It also nearly melted through a nearby network cable, but luckily only singed the outer protection layer.

Luckily most of the PSU / wiring was on top of some stones I'd left on the shelf..

Today's lessons, put them PSU's and wiring on concrete paving slabs, so they can't burn though shit so easily !

Maybe a, turn power off if smoke detector goes off gadget.. ( Are those available off the shelf to plug into plug sockets ? )

Just a beginner here, but it looks to me like the wiring in the adaptor part was too thin, and maybe the connectors are not good enough.
( At the time, I couldn't find a model without that.. )

Killed the NAS MB too, or maybe the NAS MB killed the PSU..

Or rather, it killed the wiring, the PSU still puts out 12v DC, but its little light doesn't work anymore..

Hopefully others can learn from my experience !

So far on average, I've had one electrical item per decade go bang with sparks/flames/etc. come out of it.

One reason I like second hand units, they already been through that testing phase. :-)

So, any lessons for me next time ?

After a while of functioning as a dev, I've learned one of many lessons:

The amount of experience you have does not correlate with your expertise, but it in fact correlates with the amount of absolutely broken shit you've seen and your ability deal with it.

For me side projects have been things I'll make to do something that others will use. Some people call it innovation, some call it side business. But that's how i look at side projects. So the points below are more to do with entrepreneurial experiences.

1. If there are more people involved, ensure that there is work for everybody (also level of commitment is tested by how much they put in). Also have as varied set of skills as possible. So that areas are well defined in terms of scope of work and areas of expertise.
2. Put in some money. Money is super glue. It will ensure that you're committed to the thing. Things change when decent amount of money is involved. You're invested, as may be others.
3. Learn something as an intention. This has nothing to do with the learnings you'll get on the way. This one seems obvious, but nevertheless needs to be said.
4. Set timelines and deadlines. Ask someone else to check on whether you're keeping on to your deadlines or not.
5. Don't go live without proper testing.
6. Make something you feel strongly about. The path will be exciting and clear.
7. Talk to people to get their feedback on everything. You may not like what's told to you. Listen dispassionately. Absorb everything. Feel miserable. But listen and think about it after sleeping over it.
8. Continuation of above point. Talk to varied set of people in terms of backgrounds. You would be surprised as to how differently people think.
9. Ask for help when stuck. Kill your ego and be vulnerable.
10. Check out what's already available. What value are you adding. And make it!

Side projects are one of the biggest battery booster you can have.

For me it's common to get burnt out with fixing a bug or refactoring some pretty old logic, and working in side projects is a nice break to recharge the batteries without necessarily getting your mind totally out of programming. It doesn't matter if they are yours our someone else's, they can do wonders.

(Also, it's good to learn different stuff from what you are used to, like frontend developer working on some back-end logic in a side project)

This is the reason I will never be with IT: I recently got hired as an IT assistant at my college. I was in charge of solving issues in an entire building actually. I was so excited to be able to go around to resolve and troubleshoot problems with people's computers. The responsibility and pay were good, but the fact that people had next to no problems, but I had to be in the same room with students during virtual tests and lessons just in case. I had to stand in the same spot for 2.5 hours watching people take a test. Whenever they DID have a problem, they just had to refresh the page! People gotta learn that I don't have to be in the room in order for people to decide basic troubleshooting. Extremely boring and tiring. No challenges and barely any problem-solving. This is why I'm on Devrant and not Fixrant.

I was asked to make a system in visual basic which, from a database, could output a ridiculously complex summary page, and dynamically created pages for each record in excel. The system was originally completely self contained using tables, but it "wasn't presentable enough".

Lessons learned: Excel in VB is a pain in the backside. Avoid if at all possible.

1 week and too many lines of code and cups of tea later, I became the "excel guy"

Also, another one is when I was asked to use unhashed, unencrypted passwords and store them just as they were for the company's main management system. The password were also appalling. No surprise there.

So there you have it. Bad practices and tricky excel.

After going through the regular process of talking to HR/Recruitment and passing the casual interview with a team-mate for cultural compatibility, I got the task of grilling a candidate on some technical matters. This being a PHP job, we got to talking about PSRs (PHP Standards Recommendations).

As he seemed to take pride in his knowledge of PSRs, I decided to focus more closely on that.

So we got to a recomendation regarding dependency injection containers. Nothing special, and he seemed to know his stuff. At that point, he made a statement that parts of that recommendation were a bit stupid.

Now, I hate to put people in their place, but his statement did not match what that specific PSR stated. So I gently tried to correct him. The candidate, being on fire thus far, pointed out that I should trust him on this, as he clearly knew his stuff.

Again, I didn't like having to do this, but I also did not like him having a misconception about a topic he was, otherwise, really on top of...

So I asked him to trust *me*, as I was one of the writers who contributed to the standard.

The true test here, of course, wasn't if he knew all the minutia of every standard but how he would react to being corrected.

We, as developers, are wrong all the time. Its how we learn and evolve. So being able to accept that is vital.

Sadly, he did not respond too well and sunk into a bit of a sullen silence. At first I though maybe I'd scared him or that he was afraid of having made a gaff but it soon turned out he genuinly did not like being wrong.

Sadly, I had to advise against hiring him.

When I was in School we had one Computer room where the PC's were the school used to 'teach stuff about pcs' (mostly office and some Maya). These where connected to another via the network and reset to a predefined state Everytime they were rebooted.

Since we were somehow able to get into the room during breaks between the lessons we obviously abused the room and played Minecraft in there but since the machines reset each reboot there was not much progress. Also there was no Java installed, so we needed to install that as well (that can take ages on old, school machines.).

Since the machines were connected via the school network I found out how to reboot or shutdown the other machines remotely. That was really funny for me and a friend who quickly found that Minecraft is too boring. We were just constantly rebooting the PC's the others were just launching Minecraft on and thus resetting the whole Java and Minecraft installation.

Got a lot of angry curses but nothing serious happened afterwards. Was the first I felt really badass on the computer tho.

I was thinking about the problems one of our clients faced with the launch of their project the other day, because things were rushed, stuff was omitted and in the end they could not meet the launch date, and I started making a list of hard lessons I learned over the years that would have helped them avoid this situation.

Feel free to add yours in the comments.

- Never deploy on Friday
- Never make infrastructure changes right before a launch
- Always have backups. Always!
- Version control is never optional
- A missed deadline is better than a failed launch
- If everything is urgent, nothing is important
- Fast and cheap, cheap and quality, quality and fast. Only one pair at a time can be achieved
- Never rush the start or the end of a project
- Stability is always better that speed
- Make technical decisions based on the needs of the project two years from now
- Code like you will be the only maintainor of the project two years from now. You probably will...
- Always test before you deploy
- You can never have too many backups (see above)
- Code without documentation is a tool without instructions
- Free or famous does not necessarily mean useful or good
- If you need multiple sentences to explain a method, you should probably refactor
- If your logic is checked beforehand, writing the code becomes way easier
- Never assume you understand a request the first time around. Always follow up and confirm

There are many more that should be on this list, but this is what came to mind now.

I love learning by doing.

Building MVPs and prototypes is the best way. Even better if you have a chance to show and share them in front of an audience (peer pressure can be good!).

Share the lessons you've learned and what you've done wrong, it will help many more people than just yourself.

I've been working for an eLearning company for the last 4 years (CloudAcademy.com) and I'm in love with the idea of learning something new every day. And not just coding. Code is "only" a tool to solve problems, and learning something about those problems and fields will make you a better developer.

When elastic search teaches you life lessons

Budgie isn't my best match, but I'm not gonna go back to deepin either. It broke my heart and now I'm done so it can choke on my non-existant dick. *inset darth vader joke*

Can someone pleeeeeeeaaaaaase make some DE that looks pleasant (take lessons from kde/deepin/budgie/mac/whatever) and runs on arch? Please please pretty please?

Other peoples' code... (in C++)
I am finding what some people consider good code is not as described. I found a class that provides strings. Great it gives me paths and stuff. I incorporated it in a new project.

segfaults

Hmmm, it must have an init function... It does, but not in the class. It has a friended init function:
friend init_function(). If this function is not created and called external to the class then the class will segfault...

okay...

I implement this. I use code from another project that implements this correctly. The friend class allows the private constructor to be called to create the main instance of the class. So its a fucking cryptic ass singleton. I look at this class. It uses a macro to decide what to function call in the class. The class already has function names for each call it needs to make. The class is literally a string lookup table. I vow to redo this shitty code, someday...

I start to wonder what other fragile code I will find. Not long later I keep getting errors on malloc. Like any malloc that is called results in a segfault. The malloc is not at fault though. I run valgrind and find a websocket library is returning an object a different size than the header file describes.

WTF...

Somebody has left an old ass highly modified definition of the websocket header in a location in that I include headers (partly my fault). I eliminate that from my include path. All is well, everything behaves. I will be making sure this fucking header is not used and it is going to die. Wasted a bunch of time.

Lessons learned: some code is just fucked and don't leave old ass shit you tried laying around.

I'm currently in France and after watching my first YouTube video here, I learnt to import lessons: 1. You can't escape from the udemy ads 2. The French seem to pronounce python (as in the language, obviously) like a French word...

Tbh this is more about education in general... Introduce the same system i had, no fixed lessons just a project and a time frame. Eg : create your own MVC framework and a site to show it off

Time frame : 5 weeks

(dont expect fully fletched frameworks but a site that uses the MVC data flow and the code is reusable)

probably around 12hrs, back in my Uni days when a project needed to be handed to someone else for completion in the morning. I slept about 2,5hrs after I finished and then went to lessons.

I used to be hungry of learning, studying in university, watching premium video lessons online, being curious and deepening all the least known argument of a technology and getting started with a lot of personal projects.

Now I'm looking for a job and I discovered that working 1 year in daddy's company, without motivation and doing always the same stuff, worth more than all this

Being a programmer or dev is a lot like being a chef: (I've done both)
Sure it's something anyone can just jump in on with minimal experience, and probably make a little thing that kinda looks cool to the layman, but it takes experience and hard lessons to make something that will impress the judges.

Wrote a PLSQL exam yesterday.
Had to do it on a sheet of paper instead of using Eclipse (which we normally use in lessons)

My brain :
kernel panic - not syncing

It was the worst exam I’ve ever taken😅

#TIL that you can navigate part of your Linux commands with CTRL like CTRL+A gets you to the beginning of the typed command, CTRL+D deletes the forward command and CTRL+E gets you to the end of the typed command.

NONE OF THIS WAS FOUND IN ANY LINUX-FU LESSONS! THESE WERE WAY EASIER TO USE THAN USING THE ARROW KEYS GODDAMMIT!

I have sort of an embarrassing question...

I never learned touch typing, hated it as much as I hated my calligraphy lessons in elementary. Forward a couple of years, I'm a developer and trying to dig deeper into vim seems to require learning touch typing... it has been a struggle to say the least and lowered my speed to a frustrating rate. 😥

I know the arguments for putting the work and learning proper technique but, are there any other arguments out there? I mean, as a developer I find myself using a lot of numbers and symbols which are not totally covered in touch typing curricula, together with a bunch of key combinations...

Idk, maybe I'm just asking for encouragement or different perspectives or unknown advantages about learning touch typing even when you feel fast and confident without it... Thank you guys!

Whan you are borded at web development lessons...

My best teacher was with me for C++ in high school and in college. He had the most relaxed, laid back style while managing to both make the lessons fun.

Perhaps my favorite lesson was around C++ and Pointers. Lessons generally we mixed with long ramblings about the military and live coding examples. He was talking about object references and Navy ships when he told a student to "give me the USS Wisconsin". Perplexed, my classmate said he wasn't sure he could do that without a lot of help. So this teacher drew an arrow on a piece of paper, showed it to the class and then found the general direction he wanted it to aim for and taped it to a pole next to the stage. He called that a Pointer to a USS Wisconsin and then asked the student to give him the USS Wisconsin again.

I understand pointers today because of that lesson.

During my undergraduate studies I had a Numerical analysis course. The lecturer is an old professor who was the dean of the faculty at the time, during all lessons he'd talk about his grand children and how the course is important to us the engineers. Not for a moment did he speak of the material it self... Came the test - 10 fucking questions of prove and solve in 3 hours. Had to learn the course from Indian fellows on YouTube...

Lesson 1 of developing a project with managers: never make it known that solutions to some bugs are simple. Managers will assume that all bugs are simple and require little thought and effort. Then, when there is a bug for which you have no idea what the solution is just by looking at the issue, they will become upset.

Have you ever tried to share your very simple project on FB groups which you just learned how to build? I got a lot of cheerful remarks and 2 to 3 haters. I don't know why they're trying to hate on but I'm just sharing my work and code. How do u not get a bad day and continue to improve yourself with this type of situation?

I dunno if any of my choices have been "bad". Humans are great at explaining things to themselves to feel better. Narratives is our strength and we love them.

In hindsight everything seems to be a correct choice and kinda makes sense. For everything else is just a lesson to learn from.

If there's something I fucking hate with all my goddamned soul is when you post something online and people get in their fucking high horse and judge you or tell you what to do

Like I understand if you're talking shit about people in the same community, then if someone tells you you're an idiot, I get it.

But if you're ranting about someone off site, then why judge this person? What's the damage being caused to you or the site?

For example, let's say I rant about my wife and the things that annoy me about her, and I use some colorful language to get it off my chest.

There's always one motherfucker, one stupid piece of shit that says something out of line.

In general it's one of these things:

* "wow, you need to calm down, you clearly treat her like shit, she is better than you*

YOU IGNORANT PIECE OF DOGSHIT. DO YOU HAVE CAMERAS IN MY HOUSE AS TO ASSUME THAT I TALK TO HER IN THE SAME MANNER AS I DID IN THIS POST?

YOU GULLIBLE SHIT EATER.

OF FUCKING COURSE I DON'T TALK TO HER LIKE THIS. I'M NOT AN ASSHOLE OR A MONSTER. I AM JUST R-A-N-T-I-N-G.

AND I RANT IN THIS MANNER SO AS TO GET IT OFF MY CHEST AND NOT FIGHT WITH HER. AND IT TENDS TO WORK. DOES IT REALLY NEED TO BE EXPLAINED?

Jaysus fucking christ. These people actually have the imagination of a fish, they can't fucking connect the dots.

Judging someone online is an egotistical thing. People like to judge others because of that morality high. It's the snack of the morally lazy.

Repeat with me: "I am flawed too, I have problems too. I should never judge others easily, let alone without full fucking context".

* "op, you should do <terrible advice>"

these ones are better, because they are trying to help, but still annoying as fuck.

they come in two forms:
old smug and condescending washed up idiots who overrate their life lessons and think they are applicable to every person A PRIORI.

yeah, fuck case by case analysis, these dinosaurs think they're the wise elders of the village.

Age does not immediately mean your advices are valid, your advices are valid on the sole merit of being valid by themselves.

I don't give 2 fucks if you're 60 or 120. If your advices are bullshit, please spare me the idiocy and the lack of case analysis.

I had old people tell me "trust me kid, happy wife, happy life" wtf is that shit? MY WIFE IS NOT YOUR WIFE.

YOU DON'T KNOW MY WIFE. MY WIFE IS ACTUALLY COOL, BUT SHE COULD BE AN ACTUAL PSYCHO AND I COULD BE OMITTING THAT FROM MY POST.

THEREFORE, HAPPY WIFE HAPPY LIFE IS A TERRIBLE THING TO SAY.

JUST STFU.

This reminds of that disgusting reddit post where a father asked advice on /r/relationships about her wife, and people told him "dude, duh, divorce her".

Guess what, she ends up murdering both of her children.

You would think such post would serve a lesson as to be careful giving advice online. But no, people think they're fucking dr phil or something with EXTREMELY LITTLE case knowledge.

People need to talk a bit less and listen a whole lot more.

You want to know how to help a person who is expressing problems?
You want to know how to be REALLY conpassionate?

Just listen. You can give minimal advice, but listening is the most important, with some occasional "i feel you man".

Everytime a journalist asks a suicide disuader what do they do, they always say the same " i just listen to their problems".

ITS NOT FUCKING ROCKET SCIENCE FOLKS. YOU WANT TO KNOW HOW TO BE A GOOD PERSON? CLOSE THE MOUTH AND TAKE THE WAX OUTTA YA EARS.

There's also the younger ones who think they can help when they don't even have no experience at all.

This is being naive, but I Iike that more than the smugness of old people.