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.

The intern learned a great lesson today...

Dear me,

We have noticed you uploaded files to a public github with your API keys in plaintext.

Please proceed to bang head against desk until you have learned your lesson.

Sincerely me.

11 kids in Sydney recreated Martin Shkreli's drug for just $2. The moral of the story? When you do cool shit like this, it's ok if you don't wear pants!

"Don't waste your time writing code. Browse on github looking for pieces of code, they're all well written over there."

... during a Javascript exercise lesson.

Boss: Who knows VB?
Me: I once wrote a calculator
Boss: Good enough! You will edit the companies biggest VB Application.

Lesson learned. When your Boss asks if you know a programming language you do not really know, you are like John Snow: Know nothing

Lesson 1: Valid HTML Tags

Lesson #2731 - A backup on the same device is not a backup.

Friend: Can you teach me to code??

Me: Hell yes, bout time you came to your senses.

Friend pulls out iPad: Okay, lesson one!

Me: Did you actually just pull out an iPad? Get a fucking computer or laptop!

So I've started my Python adventure and made an app that lets me know what's my next lesson in school. It shows lesson, subject and time.

I just sent an automated email titled "Gary is a Dinosaur!" to a lot of humourless clients because the ancient application I was testing assumed I was in the production environment. 🙃

Lesson to self: stop using bogus names in testing.

Still, it could've been a lot worse... 😂

What is AI?
CS student: Artificial intelligence
Graphics Designer: Adobe Illustrator
Biology student: Anthro Insertion
Pervert: Anal Intercourse

Lesson: be careful with your abbreviations

This is what I've been up to in my free lesson @ school yesterday ^^

Had to wake four people up at 2 am to fix a crashing service.

10/10 would deploy to production on Friday night again.

Saying yes to people who want a website for $100.

I've learned my lesson, all brand new websites now start at $1000.

Lesson learned: Ask the company to see a sample of their code before accepting the position.

Life lesson learned:

If your girlfriend asks you what SO means, it's "Significant Other",

NOT StackOverflow.

A few years ago:

In the process of transferring MySQL data to a new disk, I accidentally rm'ed the actual MySQL directory, instead of the symlink that I had previously set up for it.

My guts felt like dropping through to the floor.

In a panic, I asked my colleague: "What did those databases contain?"

C: "Raw data of load tests that were made last week."

Me: "Oh.. does that mean that they aren't needed anymore?"

C: "They already got the results, but might need to refer to the raw data later... why?"

Me: "Uh, I accidentally deleted all the MySQL files... I'm in Big Trouble, aren't I?"

C: "Hmm... with any luck, they might forget that the data even exists. I got your back on this one, just in case."

Luck was indeed on my side, as nobody ever asked about the data again.

I used to use Firefox few years ago, but people around me called me fool and told me that Chrome was much better.
Now I use Chrome and you devRanters are making me feel like fool again.
Lesson Learnt: Stand straight on your decisions

!rant source: LinkedIn;
Yesterday I met with a potential client who wanted a website. I gave him a quote of X. He said, do this work for X/2 as I have lots of projects and I can keep you engaged for months.

If it was 2 years ago, I'd have happily accepted his proposal. But in the past 2 years I have learned this lesson hard way. Don't work for clients who don't pay well, because when a developer is not paid enough, the quality of work degrades. Hence the portfolio is degraded and so the future projects are also of low budget.

And before you know it, you will be surrounded by low paying clients who see you as a Skilled Labour.

Today, I don't negotiate, not even a single dollar. To justify my cost I make sure that no stones are left unturned while delivery.

It's better to work for 10 hours a week for 40$/hr then to work 40 hours a week for 10$/hr.

Lesson of the day: Never ever force push to fucking master.

"How to name your variables and functions so they can be understood by other humans" should be a mandatory lesson right after someone writes their first ever computer program.

Lesson learnt :
Never ever do "rm -rf <pattern>" without doing "ls <pattern>" first.
I had to delete all the contents of my current directory.
I did "rm -rf /*" instead of "rm -rf ./*".

How long is it ok to wait before telling my colleague that the Windows Update-screen he's been watching for the last 25 mins is just me giving him a lesson in "Win+L"? (He's actually just watching fakeupdate.net)

<rant>
when you're in a iOS programming class and for the 3rd week in a row we aren't coding. I don't give a flying fuck about steve jobs or apple as a company or their philosophy. Im here to code, not for a fucking history lesson.
</rant>

That's Microsofts lesson: How to count to ten?

When I was 10 my younger brother saved over my fully completed pokedex in Pokemon blue.

First big data loss taught me a good life lesson. Now I backup everything on a local server.

In a couple of years:

Lesson 1 of any computer course:
"Install devRant. You're going to need it."

At work for a bank, I changed the target SQL Server in my SSIS project and arbitrarily, all my custom-coded scripts were erased!!

I didn't take backups and I spent a week coding them! Fuuuuuuuuuckkkkk 😠

Ended up rewriting them.

I learned my lesson... 😥

When you write code and forget to comment it, and then you come back and try to figure out why the heck you wrote certain parts of it.

Let this be a lesson for future me.

Things I have learned:

-NEVER trust a group of people not to reply all to a large email
-NEVER trust a group of people not to reply to a group text

Screenshot is from yesterday, and violates my second lesson learned (Not my group text, not my fault)

Lesson learned from wk111:

We gotta get out of the fucking house more guys and girls!

Go code on a fucking beach or a park or something. Drink some beers and wine. Smoke a couple of joints with good friends.

Me in 2018 : I'll code xLearno.com all on my own!
.
.
.
Me in 2019 : xLearno.com is a team of 5 🎉
.
.
.
Just a quick lesson that I learned in my entrepreneurship career, "You want to go fast, go alone! You want to go far, go together 😍"

I'll keep it short:
My nastiest freelancing horror stories contain shitty clients who dont pay, the nastiest fucking legacy code you can imagine, and expectations as high as trump thinks of himself.

The lesson is simple: Choose your freelancing clients wisely and always expect partial payment in advance. Even from family or firends!

never mess with GRUB!
lesson learnt -.-"

My relatives: "Can you fix my computer/ipad/etc..."
Me: "Sure why not. I'l take a look when I have the time"
Lesson: Don't be so arrogant.

Lesson of the day:

If you're really into a YT video on your laptop while eating noodles and your phone is on vibrate and you know you get scared very easily, keep the bowl away from it. I repeat: keep it away from it.

Boss: Can you modify the prototype, so that I can show it off to the customers who will visit?
Me: Sure, when do you need it?
Boss: In two hours.
Lesson learned: Always have a branch in your git with a working demo.

FUCKING WAITING FOR PEOPLE FUCKED ME OVER AGAIN. WHO WOULD HAVE FUCKING GUESSED?!

I think I have accidentally invented the term 'noteporn' the moment a colleague saw my lesson notes taken in LaTeX and said: "Wow, your notes are so beautiful one could fap on those!"

When you are learning about beer on electronic lesson...

Starting a third year computer science course. Lesson 1 of web API production. Git. Lecturer tells us to do a different branch for every commit so it's easy to roll back.

Nice.

#1 life lesson I learned from coding?

Maybe not coding specifically, but I learned the difference between problem solving and solution finding.
Its helped me in a lot of areas of my life. Made friends and made enemies.

Today I learned the hard way that losing your app's key store means no more updating , bug fixing , performance boosting , features adding ...
The app had like 5k downloads on the play store ..
Lost the key when one of my hard drives burned ..
Lesson of the day : keep your keys safe .
*trying to stay strong*

Yesterday I spent some time on the meta site for dba.stackexchange.com and found this one guy with 1 rep raging about how his questions aren't getting answered and how is answers are the best etc...

"I have 17 years of experience as a dba, blah, blah, blah, my answers are correct, blah, blah"

He got pretty destroyed by the mods and other users about how shit his answers were and how they weren't factually correct etc...

This just continues to show that no matter how much experience you have you won't always be right.

Same goes for my senior at work, he has 10 years more experience than me (I have 2) and he still asks for my point of view and help without being a dick about it.

I hope we'll all keep being nice people unlike that Stackexchange guy...

Lesson Learned

!rant
I just attended a meet up yesterday and I learnt a life lesson by the speaker: "Never share two things is life. Toothbrush and database" 😂

Introduction to graphics

Lecturer says "this is a very practical course. In fact I think we should have a practical exam"

All students agree. He would sort out that matter.

Meanwhile he taught us how to making shapes in java, then a house, then a game...

And the exam was for us to make a building where a user can walk through the building using the arrow keys...

What fun we had. We got out marks...and everybody did well!!!!

For security purposes, it should be good practice to lock your pc when you walk away. At my office, we practice harmless pranks when someone forgets, to "teach them a lesson". Usually just involves reversing/inverting displays, reversing mouse buttons, or changing the desktop background like this (because everyone is a closet bronie apparently)

Programming lesson #5
When logic becomes too complex to solve mentally while coding, writing the requirements and inputs on paper and coming up with pseudocode is a good approach.

I hardly use Windows, but had to book tickets using my friend's laptop who only had Windows.
So I switch on my mobile data, and the stupid shit just ate up all my data in updating Windows without even asking for permission 😣
Learnt my lesson

Sometimes I am so motivated .Today I tried coding in car .(I was in backseat)
20 min: Damn,my eyes hurt😞
40 min: Why do I feel dizzy😵
50 min : Oooh...I feel like puking.🤢
51 min : Dad......Stop the caaa....
Nothing I'm done
Lesson learned

Men. Live with it.

(Stupid mistakes that kept me from sleeping.. 🤦🏻‍♂️ Lesson learned: Sleep.)

Using a copyrighted image on a website not knowing it was copyrighted. That was stupid and humbling. So caught up in the roots lost sight of the leaves.

Lesson learned: Assume nothing, question everything.

So this is how they "teach" us in school...As a part time dev I was completely shocked when I saw this in our materials. What do you think? Should I drop the teachers tables to give him a lesson?

So one day on tech huddle my tech lead got frustrated, don't know why and told me - "the tasks you're doing can be done by interns"

I felt bad. Ofcourse I was putting my 100%.

That day I decided to put the resignation. I didn't discussed with anyone about it and sent the resignation email directly.

After serving 2 months of notice period I was able to land a better job successfully!

I called the lead on the last working day in that company and shared him the news about my offer letter and a little about the company.
His first question was - "Did you cleared all the interview process?"
In my mind - "That's only why I'm sharing the news here with you man! Stop thinking of me as a noob."
I replied with - "yes, if needed/the new company try to get feedback about me then please be honest atleast there by keeping your ego aside."

You shouldn't pull someone's leg if you aren't able to climb higher!!

Lesson I learnt;
DON'T STAY AT A PLACE WHERE THERE'S NO VALUE OF YOUR WORK AND THE DEDICATION TOWARDS IT!

Working in a startup isn't that easy, mostly for those where there's no work life balance.

lesson of the day:
if you enter the office toilet while chewing gum, the simultaneous smell of shit and jaw movement will lead your brain to think you're eating shit

Hard lesson:
Don’t update your OS while a project is still not finished, or at least on critical state of a project

Wrote for-loop without learning it in school-lesson.

Teacher says I have a gift...

Expecting your client to be nice with you just because you are nice to them is like expecting lion not to eat you, because you don't eat lions.

Pro tip:

Make sure you can RECOVER from your backups.

It's all well and good backing this and that up, but make sure that when the shit really hits the fan you can recover.

I've now 4 days into recovering a raspberry pi that ran:
Pi-hole
Snort
DHCP
VSFTP
Logwatch
Splunk forwarder
Grafana

And serveral other things... I've learnt my lesson

Am I the only one who's slightly annoyed that the first lesson in the Swift Playground app is not a "Hello World" program?

When you ask an older dev a question, and instead of an answer, you get a history lesson. 😒

!rant
... so... maybe not that much of a thing, but i think it is:

a gal (27 years old) i started teaching programming two weeks ago, who had literally no previous experience with programming, algoritmization nor c#...
... just now, after 3 lessons of 6 hours altogether, and after yesterday when i explained to her what arrays are and reminded her what loops do...

... invented bubble sort. on her own. no googling. on paper. no "trial and error code typing and running".

i'm actually pretty proud of her :)

... putting the algo concept into actual code will still be a bit of a struggle, but yeah, hell, can't help thinking that she's actually pretty smart :)

(p. s. fist lesson was i drew uml of a fibonacci algo and forced her to understand what it does, second lesson was i explained the minimum required c# syntax for her to be able to implement it and forced her to write it (with as little help as i could), third lesson was the concept of array and "okay, now here's array of numbers, make a function that will sort them")

looking forward to what will happen when i explain recursion and nudge her towards quicksort O:-)

First day as teacher - ok guys we're going to learn good lesson today, open up your terminals and write the next command sudo rm -rf /

-I just visited my nephew, I wasn't their teacher

Fucking brilliant. Paused my Ubuntu VM in VMWare. Unpaused it, the whole file system is corrupted.

There goes my 2 hours of customization. Lesson learned.

Mining-Noob-Exp. #1

Just received some ordered ASIC miner from Bitmain. I'm very excited wether I'll reach the ROI or just bought some expensive heaters.

Lesson learned: Don't forget about possible (high) import taxes and fees in your calculations. 😐

Time to piss of my landlord who is paying the electricity bill. 👺

Life lesson #32767: Don't review code commits before your first cup of coffee.

You’re always telling people the importance of backing up important files, but do they listen? Of course not. Sometimes you have to simply sit back and wait for natural consequences to teach them that lesson.

Lesson of the day: If Visual Studio starts acting up (doing inexplicable and illogical shit that literally makes me question life), just delete the .vs folder. In fact, don't delete it. Fucking shred it with a file shredder. Or even better, write it to a CD and burn the CD.

I once thought about tweaking the JS files and replacing ";" with a similar Unicode character just to teach a lesson to the guy that refuses to use Git.

#1 life lesson learned from coding:
Don't work on projects for the government or any authority EVER!

Top lesson? Once you go Vim, you never go back.

I'm not knowledgeable when it's about Linux, so when I want to do some stuff I always have to take a f*cking lesson and a half. Could someone please explain to me what Docker is?

Getting out of this business. I had my first flying lesson yesterday. Luckily I held on to my breakfast during the flight... A couple hundred more hours behind the yoke, and I'll be uninstalling all my developer tools... Can't wait

Me: *give my reviewer about Unix in our Operating Systems lesson for the quiz*

The friend who I gave it:

I absolutely hate my math class....

But... what's this!!!? You're using an old ass website that uses a JSON API to send my lesson scores to my school's grading website?

Well damn... wouldn't it be a shame if someone were to somehow tap into that API and override the grades for each assignment?

For fuck sake Facebook test your shit before you update!
Lesson learned, never update Facebook pods ... or even better never use Faceshit!

1) Remove kernel linux
2) Change kernel to linux-zen
3) Make init ramdisk
4) Everythings great -> hit reboot
5) Stuck at Grub
Me: Fuck.. Forgot to update grub config.
(Lesson : RTFM first.)

Worst fight?

Stubborner against stubbornest.

About a focking fact that was trivially true or false. Fun fact: it didn't matter anyway.

Boy, did we raise our voices and attract the attention of everybody in the room. Lesson learned.

How to be polite?
Lesson 01: Always put the trash in the can. 🤔

Today a teacher asked us about our hobbys. A classmate said 'programming' and after the lesson I asked him which languages he uses. He answered:
"Languages? What languages? I used that software you can program shortcuts with."

So, it's time to fucking rant!

Location: A small startup where direct contact with C-Level members is frequent.

A while back we had a customer using our SaaS product who had gripes about the way it worked.

He contacted our CEO and made a bunch of claims based on bad assumptions.

In the end, he wanted all images removed from his site. I was pulled aside by the CEO and asked if I could handle this for him and make a new screen for them without images.

So I did. I tried to discuss and get deeper into the problem by saying "this seems like a symptom of a problem and not the actual problem. What do you think?" He responded with "That was his request so it must be the problem if it won't take long then let's fix it for him.

- a week later

The problem is fixed and in the wild. No more images. Now he has another request :/

He does not like the pagination on his site. He says " I shouldn't have to click a button when I scroll so I want the be able to scroll and see all my products!"

This time the CEO asks me if this can easily be done and I take him aside and say "no, this will be a big change to our system and will need to be discussed with the team."

The main point I make is that we should go down and spend some time with this customer to find out what the real problem is.

After a half hour of discussion about the real issue he decided to bring in the CTO.

In the end, we implemented infinite scroll, dropping our current product building tasks to service one customer (yeah, it's a bad scene). But we got infinite scroll built and shipped.

- 2 Weeks later

This time he demands that infinite scroll isn't good enough. "If I scroll fast then I have to wait for them to load, they should all load at once!"

This time I have had enough. I can see the CEO is coming over to me to as me how much work is in this. I tell him there are 3 things I have to say...

1. I'm going to implement exactly what he asked by the end of the day.
2. We will only release it to him because it is going to be a shit-show loading everything at once, the load times will be mental!
3. We should fire this customer, right now.

So, I built it. Customer hated it (of course, who the fuck wants to wait 30s for loading. That's basically a lifetime). We changed it back and he was still mad.

- 2 weeks later

Customer leaves. Good riddance.

- sometime later

I am in the customer's store on a road trip. I get a feel for how their store works and they have a different system for making things operate.

It turns out that they did not know what the real problem was. They actually needed a completely different system (from a UX perspective) for accessing their data.

To top it all off, the system would have taken less time to build than the shitty fixes we made over weeks of work. FFS

I guess the moral of the rant is to find the problem, not a symptom of the problem.

Life lesson:

The first run is always the slowest.

Lesson learned: if you're going to derive a class in c++, make sure to declare a virtual destructor on the base class!

I just fixed (one of...) the massive memory leaks in my damn project.

Pictured: the strings in a derived class actually getting freed!

My cat decided to jump on the PC at 5 AM.

Lesson learned: Never going to put my PC on the desk again.

Finish html lesson 😊

Regarding my last rant: I AM FUCKING DUMB!

When I receive data from the master Arduino, a hardware interrupt runs and oversteps my main loop stuff!

Lesson? NEVER WRITE HARDWARE LATCHES ON THE MAIN LOOP WITH A HARDWARE INTERRUPT WHICH IS MOST OF YOUR FUCKING CODE!!

A lesson I learned. Clients can't separate design from functionality. They will piss and main about a feature not working right when what they really mean is the aesthetic is not to their liking.

A lesson from a former UX Designer to DevOps

READ THE FUCKING JOB DESCRIPTION WHEN APPLYING FOR A JOB. COMPANIES DON'T EVEN FUCKING KNOW WHAT THESE JOB TITLES ARE AND JUST MAKE IT FANCY

Lesson learned: never drink during programming

This morning... Five hours of theoretical lesson of informatics, systems and networks!! :)
Let's Go! 💪

Biggest hurdle I have overcome is <b>myself</b>.

All my expectations, worries, fears, and doubts definitely caused major hurdles I had to crash through, trip and fall into, or they downright exploded into balls of fire as I would stand dumbfounded and burned by flames of regret.

Learning I was the blocker to greater achievement, success and ultimately happiness was a very hard lesson for me to learn, and a lesson and discipline that I still battle with today.

It is difficult to climb the seven story mountain of madness with heavy burdens, plodding with little progress.

Free the weight, and the natural warm air currents will lift high the spirit, and the body will follow.

"Angels fly because they take themselves lightly" ~GKC

Don't run code you found on a shady forum on production.

At the University, Algorithms class, exercises lesson..the assistant explaining the results of an assignment:

"Because here..if we use a classic 'if-else' loop..."

😳

This is why you should make a knowledge database and never trust the internet to keep things

Two quality rants with a lot of useful information I favorited are missing, surely because their authors removed their account

Lesson learned. One more resolution to apply for 2021

I'm the kind of person that says "Fuck python, worst language, fuck C#, Java, Golang", assembly and C are superior.

But I have learned my lesson; Yesterday I learned enough C# to be able to make a windows app that connects to a another app via sockets. I tried first to do it with C++ but my app looked like shit and took me about a whole day to make. Then I tried with C#, got the App working on an hour, now I'm delighted with C#. I guess I have to be open-minded.

*knock knock*

Race condition!

Who's there ?

And thaaaat's the lesson i learned today after I spent two hours staring at code, to find out that the solution was just moving an unlock_mutex() a few lines down.

In our databases lesson, we are going to use Microsoft SQL Server throughout the year.

This shit's setup fails at random, doesn't even start (empty error box??????) on some machines, and when it, uh, works, kinda, it's a convoluted mess.

Help.

The ground rules for developers: ABC

Always
Be
Coding

// stole this line from my friend Tim -> credits to him! ;p

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

a lesson that I learned the hard way: Don't test a code or a library on your master branche, in other words: don't shit where you eat.

Lesson learned the hard way: Remember your SSH Ports or write them down...

On the bright side of things, i had backups this time! Tyy DigitalOcean :)

Had another meeting today. The solution architect said two insulting jokes about developers like:

"The devs will nevertheless mess it up"

Devs are the ones who make chaos

This meeting was with a customer and his developer. I was just furious!

This useless son of a bitch needs to learn his lesson

No wonder my Python code was broken. I called the super function of the wrong ancestor 🙄 Lesson learned: run the tests after every functional change, no matter how trivial it might seem.

C++ tough me that having 2 or 3 friends is ok in some situations, but its best to avoid them when possible.

Also, you cannot have friends outside of class.

Lesson Learnt..
Never make decisions when lacking sleep and caffeine as well. I nuked my HDD today morning around 3 am, I got another reason to do a fresh start btw.

How to not run a company 101. First lesson: this

At Italian lesson: The professor asks me "What is a sentence?" I answer "it's a CharSequence". He looked me very badly

A good life lesson:
1. DON'T DELETE FILES YOU MAY WANT TO RECOVER

And if you DO delete them and then recover them, then
2. DON'T SEND THE RECOVERED FILES TO A·N·Y·O·N·E

Today I found a lost µSD card in the street. I did what every sane person would do -- plugged it into my laptop :)

There I found a directory with recovered pictures. I figured, some of them may contain the author's info in metadata, so I ran a quick plaintext search for @gmail.com.

Turns out, inside some of the recovered picture files I could find embedded company director's emails in plain-text. I mean, open the picture with a text editor and read through those emails - no problem! And these emails contain some quite sensitive info, e.g. login credentials (lots of them).

Bottom line, if you delete and recover your files, then do your best to keep them close: don't share them, don't lose them. You might be surprised what these recovered files may contain

"Is this going to be on the final exam?"
- Asked every week after every lesson, by the same person.😲🔫

That awkward moment when u look svn history to find out which idiot wrote this stupid code and u leant it was you yourself. You feel so glad you didn't go all gun blazing criticising the guy to your colleagues before ur investigation.
Lesson learnt for future ha ha ha

The past 4 days taught me a very important lesson,
Gentoo is neither good for my laptop, nor for my mental health.

A lesson to be learnt by every programmer!

<insert bear grylls meme>
Improvise. Adapt. Overcome.

Lesson learned: take measures before buying parts

I have the same problem as @linuxxx does. Buying things when I really don't need to.

I went to a mall with a friend today because his headset was literally falling apart. We both bought new headsets. Great.

Lesson learned: Don't leave your house unless necessary.

My physics teacher would call it a sin. Technically enough for wk81 xD

Yeah, i coded an entire NN on paper while physics lesson. Worked pretty well. Except it doesnt work yet :/ Compiler errors because of some referenncing issues

Lesson learned: never ask for VPN

Always choose the right tool for the job.

On IT English lesson:

Professor: Simple question - how do we call all devices inside computer, like HDD, or CPU.

Some random guy: International Devices

*Insert loudest facepalm here*

Dev lesson learned the hard way. Never rm -rf with wildcard arguments... If you think you're being clever it probably means you're about to mess up some shit.

sudo rm -rf *

Just started out on linux, learning the ins and outs. All I wanted to do was remove two directories. Thankfully it was a fresh install, didn't lose anything important.

A valuable lesson was learned that day. 😂

Trying to resolve merge conflicts and you cant remember which changes are the ones you want to keep. Lesson learned, make sure your pull requests dont sit waiting for weeks while master is happily being worked on.

This is the real times. This is not that it's happening right now, this is pretty regular. Lesson? Rethink before you decide the variable type

Duolingo used to be better. New updates and restrictions are shit. Specially the whole "take a heart away for a mistake, five mistakes and you can't use the app for hours". Like, I get it, you couldn't manage the traffic. But this is ridiculous. Also, where did the lesson overviews go?

Lesson learned: Browsers won't not try to draw huge images. They'll just...

Virus Rant: Unwanted folder keep creating itself after deleting it.

Windows Defender detected some malware & cryptominer exist and originated from Chrome folder

Solution: Remove completely Chrome and stick with Microsoft Edge for now!

I cant believe I am removing Chrome and stick with Microsoft Edge.

Lesson learn: please be vigilant at all time.

One crucial lesson I learned while diving into programming:

Use various learning resources. Everyone explains things a little different.

You can understand stuff much easier.

Business Continuity / DR 101...
How could GitLab go down? A deleted directory? What!
A tired sysadmin should not be able to cause this much damage.
Did they have a TESTED dr plan? An untested plan is no plan. An untested plan does not count. An untested plan is an invitation to what occurred.
That the backups did not work does not cut it - sorry GitLab. Thorough testing is required before a disruptive event.
Did they do a thorough risk assessment?
We call this a 'lesson learned' in my BC/DR profession. Everyone please learn by it.
I hope GitLab is ok.

After over two days of debugging, lesson learnt don't assume your table's prefix nor depend on other APIs for SQL injections

Lesson Learned: Don't ever be so ambitious that you are no longer realistic about your abilities. I remember when I started out, I would give unbelievably short TTC estimates for medium/hard tasks that would undoubtedly take some time.

Lesson: you learn the most from side projects.

PreMature optimization is the root of all evil

!rant
Just realised my game development and design teacher is the senior game designer of sacred 2. Well next lesson gonna be a constant flame of this shitty random drop generator which literally mostly drops you stuff for all the other classes.

#1 life lesson learned from coding: There are things I just can’t be good at no matter how hard I try.

Lesson learnt. Never use vanilla bootstrap with react js

Lesson learned: Always use node LTS in production, library maintainers are lazy af.

Lesson of life 1-B: like DevRant

TL;DR; do your best all you like, strive to be the #1 if you want to, but do not expect to be appreciated for walking an extra mile of excellence. You can get burned for that.

They say verbalising it makes it less painful. So I guess I'll try to do just that. Because it still hurts, even though it happened many years ago.

I was about to finish college. As usual, the last year we have to prepare a project and demonstrate it at the end of the year. I worked. I worked hard. Many sleepless nights, many nerves burned. I was making an android app - StudentBuddy. It was supposed to alleviate students' organizational problems: finding the right building (city plans, maps, bus schedules and options/suggestions), the right auditorium (I used pictures of building evac plans with classes indexed on them; drawing the red line as the path to go to find the right room), having the schedule in-app, notifications, push-notifications (e.g. teacher posts "will be 15 minutes late" or "15:30 moved to aud. 326"), homework, etc. Looots of info, loooots of features. Definitely lots of time spent and heaps of new info learned along the way.

The architecture was simple. It was a server-side REST webapp and an Android app as a client. Plenty of entities, as the system had to cover a broad spectrum of features. Consequently, I had to spin up a large number of webmethods, implement them, write clients for them and keep them in-sync. Eventually, I decided to build an annotation processor that generates webmethods and clients automatically - I just had to write a template and define what I want generated. That worked PERFECTLY.

In the end, I spun up and implemented hundreds of webmethods. Most of them were used in the Android app (client) - to access and upsert entities, transition states, etc. Some of them I left as TBD for the future - for when the app gets the ADMIN module created. I still used those webmethods to populate the DB.

The day came when I had to demonstrate my creation. As always, there was a commission: some high-level folks from the college, some guests from businesses.

My turn to speak. Everything went great, as reversed. I present the problem, demonstrate the app, demonstrate the notifications, plans, etc. Then I describe at high level what the implementation is like and future development plans. They ask me questions - I answer them all.

I was sure I was going to get a 10 - the highest score. This was by far the most advanced project of all presented that day!

Other people do their demos. I wait to the end patiently to hear the results. Commission leaves the room. 10 minutes later someone comes in and calls my name. She walks me to the room where the judgement is made. Uh-oh, what could've possibly gone wrong...?

The leader is reading through my project's docs and I don't like the look on his face. He opens the last 7 pages where all the webmethods are listed, points them to me and asks:
LEAD: What is this??? Are all of these implemented? Are they all being used in the app?
ME: Yes, I have implemented all of them. Most of them are used in the app, others are there for future development - for when the ADMIN module is created
LEAD: But why are there so many of them? You can't possibly need them all!
ME: The scope of the application is huge. There are lots of entities, and more than half of the methods are but extended CRUD calls
LEAD: But there are so many of them! And you say you are not using them in your app
ME: Yes, I was using them manually to perform admin tasks, like creating all the entities with all the relations in order to populate the DB (FTR: it was perfectly OK to not have the app completed 100%. We were encouraged to build an MVP and have plans for future development)
LEAD: <shakes his head in disapproval>
LEAD: Okay, That will be all. you can return to the auditorium

In the end, I was not given the highest score, while some other, less advanced projects, were. I was so upset and confused I could not force myself to ask WHY.

I still carry this sore with me and it still hurts to remember. Also, I have learned a painful life lesson: do your best all you like, strive to be the #1 if you want to, but do not expect to be appreciated for walking an extra mile of excellence. You can get burned for that.

Me: Ah, I need to delete /path/to\ some/directory

... starts typing

rm -rf /path/to

finger slips, touch "Enter" too hard for my comfort, heart skips a beat, but nothing is happening. Phew. I dodged a bullet.

I'll never ever learn this lesson.

It sucks to realize that none of ur work leaders appreciate the efforts you and ur team are doing even though they don't give u the necessary materials to do ur job.

Lesson: no matter what u do, theres always gonna be ungratefuls out there.

Run the tests before you commit, even if it was just a minor modification.

(Yep, I broke most of the tests by changing only a couple of lines. Lesson learned.)

Have been playing the pirated version of Rust for 30+ hours with no issues.

Decide to buy the game and every fucking time the game turns into Chrome and consumes all my RAM forcing Windows to show the low on memory dialog.

Lesson learned I guess.

Learnt a very important lesson today..

To add some context; I'm currently in my second semester of uni studying a Bachelor of Computer Science (Advanced), and started the year with no experience with any language.

Up until recently all my practical work has been guided by context sheets, now I have some freedom in what my program does.

Because of the very small projects earlier in the year I have built a habit of writing the whole program before compiling anything. This worked fine since the programs were small and at most only a few errors would be present.

Cut back to today, and I had been writing a program for a bigger assignment. After an hour or so of writing I began thinking I should probably test everything up to this point. I ignored it...

Fast forward 4 hours to having "completed" writing the full program. I knew by this point I was taking a massive risk by not testing earlier.

Lo and behold, I try compiling everything for the first time and countless errors prevent the program from compiling. I tried for quite some time fixing the errors but more just kept appearing as 1 was fixed.

I'm now left with no time to fix the program before the deadline with no one but myself to blame.

Lesson learnt :/

Rant at myself for being a moron.

Manually tried moving some InnoDB stuff around on a local server and corrupted a load of databases, with no backups since June 28th. Spent all day yesterday trying to recover with no luck 😑

Lesson learned: need to backup databases more regularly. Any good tools?

Classmate from school has logged in to his gmail account on my laptop and has not logged out yet. Now I have access to all the his subscription including g facebook.

Now as a friend and human, should I teach him a expensive lesson ?

You time starts now. Reply fast 00:59:00

I just asked a client if he wants a contact form instead of just writing down an email address on their contact page.

Now I'm trying to explain to him how building a full blown CRM is outside the scope the business website we agreed to build.

Lesson Learned: Never make suggestions.

Making scripts for custom physics is fun. One moment, the object gets stuck on the ground. The next, it shoots off into the far distance.

Lesson of the day? Don't be an idiot for once, stop, grab a notebook, Google some formulas and think like a human being before messing around with the script again.

YikYak will probably be used as a lesson in app development on what not to do. They killed their entire app in a single release. Biggest mistake was never listening to their users.

Lesson learnt.
Never argue about any type of OS (Desktop or Mobile) when sitting between Devs. Be it about features or development.

I was teaching a friend of mine how CSS works for her exam and we reach the point where she had to style the tables and she reads:

To avoid having spacing between table cells you can use:
border-collapse: collapse
[...]
border-collapse can also have value "separate"

She fucking freaked out like "WHAT THE FUCK IS EVEN THE SENSE OF IT? SHOULD I HAVE BORDER SEPARATE: SEPARATE? WHY THE FUCK SHOULD I WRITE THAT TWICE? HOW THE FUCK DOES THIS EVEN WORK OUT?"

I just loved how she doesn't know how to make a website but she already hates CSS before even using it on an actual browser

Why does everything look perfect on the emulator but messes up on the first phone you test it on.

Every single time.

Lesson: Test on phone first then emulator.

Never! ever! EVER!!! run sudo rm -fr * inside your home directory! Hard lesson learned on a Monday :(

P.S it was not intentional at all!

My teacher showed some Mr. Robot episodes on lesson. I think it's pretty good. What are your opinions about it? Should I start to watch it?

So I just spent 3 days trying to write a custom WordPress query with WP_Query and limit the result set with tax_query. I wrote my own code, copied and pasted code from the docs and watched a couple of tutorials, no matter what I did my results just weren't right. Turns out I was calling my code too early so my tax_query was being ignored.

Time wasted or lesson learnt?
.... I'll take lesson learnt. Oh well.

Coding hungover pretty much sucks...one day I'll learn my lesson...

Today I had to write some shitty code that should work on ie in compatibility mode which is like ie in Version 6. I only coded on the clients system and never backed up. Silly me. Every think worked so I continued with another clients project. Suddenly my colleague came in our office and told me that the client deleted my code by accident. I never will keep code on client systems only again in the future.

How to manage when you start something good for you, start taking decisions for your good and people start spreading hate about you. It obviously will effects your mental health right?
How you guys manage it? I mean how?

Today I'm feeling of getting bullied and getting bullied again from the same person. I'm correct but can't show the correctness just because there's no proof I've in-hand.

I'm literally tired of people now!

Used a wrong filter during loading of a table in ETL. Did not test and migrated to production. 80% of users had empty reports.
Had to stay awake till 4AM to get it fixed.
Realized an important lesson -

' A test in time saves nine'

Lesson of the day? Dont use 1&1

Today the government from Costa Rica announced their solution to tax double any UBER charge registered to debit/credit cards.

Their logic is to pretty much do it for any commerce that includes the letters UBER. Like something out of your first Unity C++lesson

What I learnt after 3 hrs of debugging for a stupid issue today ?

Lesson 1 - Getting some unknown error even though your code ks right and no error in logs ? Check you SQL version and its rules.

Lesson 2 - phpmyadmin is fuckin shit ass software

Lesson 3- I need to learn JavaScript for backend ASAP

Our cv teacher at school basically just printed out selfhtml.org on paper and told us to start writing websites. He then went on to chill on his chair for the rest of the lesson.

We just had the introduction lesson about Emails. I think our teacher had fun sending fake mails from his computer over the server under our name.

As a 0.1x programmer, I realised an important lesson today :
You can win school coding contests by plagiarizing code. No one cares, and no one will know.

Because the dude who won the contest was literally copying from Google and stackoverflow and they didn't caught him 😭

While listening to Algo and Data struct teacher, a friend of mine ("Blue Hair") told me about devRant. Guess i'm going to learn not much about BST today.

In computing class, we were asked to identify different connectors/ports in one lesson.
Someone couldn't tell what a USB port looked like >.>

Lesson of the day:
<If a section of your code keeps on bringing errors, just comment it. The code is likely to work./>

Learn the hard way:
Episode 1:
Struggled 4 hours building my package. Some dependent package was failing build. Tried everything and atlast, contacted that package developer. He checked and said: "It seems it's broken. You can use v1.1 instead."
Lesson learnt: Sometimes, it's better to ask instead of banging your head and debugging things out.

Every Moral Lesson I encounter:

"If it works, don't touch it."

Lesson learned: never fuck up with the python version that comes with a distro. I spent the whole day re-installing Linux Mint on a new partition and transferring home folder to the new partition. 😣😣😣

I'm an idiot 😥

20 issues assigned to me this sprint with very vague titles and in the requirements it says "See *person name* for details"

Lesson learned: Never go on vacation during the spring planning meeting.

You do not own your companies code. Of you hate working at your job, don't let the feeling of responsibility for the codebase keep you there. I keep learning that lesson.

Hell Yeah "Hello World"

I would rather create a circular inheritance class for my last task before I'm out of the company. And make some changes to the dependency injection module. Leave it blank documentation. So the one who take my position after me would get enough lesson and reason why he's not to join the company.

Lesson of life 1: be organized

"Send me a unity package file when you're done, which includes any models, scripts, and prefabs."
Seems like someone didn't take a lesson in naming or basic computer housecleaning.

Hidden pixel just scratched my finger while I was wiping the screen with my palm. Lesson successfully learned.

If you live in the past, then you have depression. If you live in the future, then you have anxiety. If you live in the present, then you have peace.

Made on networking lesson.

Met a newly recruited Data Scientist the other day and he complemented me on my work on information retrieval.
The lesson is keep learning, keep reading and keep trying

today's lesson:
one does not simply open a new window with mvvm pattern

Debugging lesson learnt

The place where you think you can't make a mistake is the place you make a mistake.

Duolingo's lesson...

On how to **flirt 😂

Years ago when I was a kid I was into making things to solve problems. Earlier in my life I remember as a kid seeing a neighbor shove 120VAC into the ground to get worms to come up to the surface. I also remember taking a worm and slapping it on one of the posts and shocking the shit out of myself. Apparently that lesson did not stick.

As a teenager I wanted a device similar to this. So I wired a 120VAC plug and cord to a 1/4" audio connector. I threw this in a box and forgot about it. Years later my sister went through my things looking for a power plug for a synthesizer we had. It had an audio 1/4" plug for headphones. She told me she plugged this cord she found of mine into the synth and it started smoking. She went to pull the plug out and shocked the shit out of her. I don't think that the synth ever worked correctly after that.

Well, today I was thinking fondly about that story. I mean, who wouldn't think fondly about shocking the shit out of your sister (she didn't die, so its okay). However, it was dangerous. Really really dangerous.

The lesson I can take from this memory is this: if you know a software interface (or electrical) is not safe then don't build it. Someone will try and use that shit years later and really fuck some stuff up. I have to wonder. What kind of software traps have I built in the past that are yet to be discovered?

Me: What if I use navigation props in EF Core, what might go wrong?

*tests API call*
*120 seconds later finally got result*

Me: I better undo my changes and stick with 2 seconds response time O_O

Life(naive_person) {
While(lesson not learnt) {
Change characters;
Repeat story;
}
Return dead_person;
}

Today I learned what actually happens if you don't close your database connections (because you forget) after you've used it. Feck all happens for the first 9 requests, and after that error 504 😂