Details
-
AboutAm Dev.
-
SkillsC++, Scala, JavaScript, TypeScript, Kotlin
-
Locationsmall stone
Joined devRant on 2/20/2018
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
The moment that I finally understood OOP.
Several teachers had already given up explaining it over and over again but one classmate took a few hours to explain.
Suddenly, after a few hours, that AH-HA! moment was there!
I've done as much OOP programming as possible since then and have explained it to others who were struggling with it as well 😊30 -
Linus Torvalds. He created Linux and Git, both used by millions of people. He started to create Linux when he was 21 and still in university. It is currently running on a lot of devices including Android. That is really an accomplishment, to make an operating system is one of the most complex things you can create as a programmer. It is also cool that it's open source and how it is maintained. Both Linux and Git was created because he needed them, he creates things that are useful. He could have earned a lot of money but he cares much more about tools and software than money. I think he is a great person and speaker (and he is from my neighboring country Finland 🙂). I use Git everyday in my work and it makes it so much easier. He is for me without a doubt the best programmer in the world.2
-
Got annoyed by hitting f11 instead of f12.
("step into" versus "go to definition").
Solved the problem :)
12 -
Had my first 'mentor' moment at work today!
Newest guy couldn't figure something out and asked me, slightly nervously, for help.
Suddenly I went into mentorish state, explaining stuff I was doing while fixing it in under a minute!
Felt good 😃8 -
I’m excited! I start my new (and first ever!) job as a dev today. I hope I do well. I’m surprised I got hired too, as I don’t have much professional experience to my name, but this is my dream and there’s no way I’m going to fuck this up! Wish me luck!2
-
Was helping somebody with a little C++ issue (disclaimer: I know jackshit about C++).
After a while off reading his code and opening a file called "pi.cpp", I noticed something odd...
This guy literally thought is was a good idea to put 81663 fucking decimals of pi in a #define statement :^)
On the screenshot, that weird "noise" on the right is actually a scrollbar of the code itself...
33 -
FULLSTACK DEVELOPER
- A buzzword that startup companies use when they can't hire a lot of people. Multitasking all the way sucker!7 -
public void method()
{
// :(
}
instead of
public void method() {
// :)
}
bothers me more than it should19 -
As a developer, sometimes you hammer away on some useless solo side project for a few weeks. Maybe a small game, a web interface for your home-built storage server, or an app to turn your living room lights on an off.
I often see these posts and graphs here about motivation, about a desire to conceive perfection. You want to create a self-hosted Spotify clone "but better", or you set out to make the best todo app for iOS ever written.
These rants and memes often highlight how you start with this incredible drive, how your code is perfectly clean when you begin. Then it all oscillates between states of panic and surprise, sweat, tears and euphoria, an end in a disillusioned stare at the tangled mess you created, to gather dust forever in some private repository.
Writing a physics engine from scratch was harder than you expected. You needed a lot of ugly code to get your admin panel working in Safari. Some other shiny idea came along, and you decided to bite, even though you feel a burning guilt about the ever growing pile of unfinished failures.
All I want to say is:
No time was lost.
This is how senior developers are born. You strengthen your brain, the calluses on your mind provide you with perseverance to solve problems. Even if (no, *especially* if) you gave up on your project.
Eventually, giving up is good, it's a sign of wisdom an flexibility to focus on the broader domain again.
One of the things I love about failures is how varied they tend to be, how they force you to start seeing overarching patterns.
You don't notice the things you take back from your failures, they slip back sticking to you, undetected.
You get intuitions for strengths and weaknesses in patterns. Whenever you're matching two sparse ordered indexed lists, there's this corner of your brain lighting up on how to do it efficiently. You realize it's not the ORMs which suck, it's the fundamental object-relational impedance mismatch existing in all languages which causes problems, and you feel your fingers tingling whenever you encounter its effects in the future, ready to dive in ever so slightly deeper.
You notice you can suddenly solve completely abstract data problems using the pathfinding logic from your failed game. You realize you can use vector calculations from your physics engine to compare similarities in psychological behavior. You never understood trigonometry in high school, but while building a a deficient robotic Arduino abomination it suddenly started making sense.
You're building intuitions, continuously. These intuitions are grooves which become deeper each time you encounter fundamental patterns. The more variation in environments and topics you expose yourself to, the more permanent these associations become.
Failure is inconsequential, failure even deserves respect, failure builds intuition about patterns. Every single epiphany about similarity in patterns is an incredible victory.
Please, for the love of code...
Start and fail as many projects as you can.30 -
My "Coding Standards" for my dev team
1.) Every developer thinks or have thought their shit don't stink. If you think you have the best code, submit it to your peers for review. The results may surprise you.
2.) It doesn't matter if you've been working here for a day or ten years. Everyone's input is valuable. I don't care if you're the best damn programmer. If you ever pull rank or seniority on someone who is trying to help, even if it isn't necessarily valid or helpful, please have your resume ready to work elsewhere.
3.) Every language is great and every language sucks in their own ways. We don't have time for a measuring contest. The only time a language debate should arise is for the goal of finding the right one for the project at hand.
4.) Comment your code. We don't have time to investigate what the structure and purpose of your code is when we need to extend upon it.
5.) If you use someone else's work, give them the credit in your comments. Plagiarism will not be tolerated.
6.) If you use flash, you will be taken out back and shot. If you survive, you will be shot again.
7.) If you load jQuery for the sole purpose of writing a simple function, #6 applies.
8.) Unless it is an actual picture, there is little to no reason for not utilizing CSS. That's what it's there for.
9.) We don't support any version of Internet Explorer and Edge other than the latest versions, and only layout/alignment fixes will be bothered with.
10.) If you are struggling with a task, reach out. While you should be able to work independently, it doesn't make sense to waste your time and everyone else's to not seek assistance when needed.
11.) I'm serious about #6 and #7. Don't do it.48 -
*code doesn't work*
-Run three times, just to be sure
-Its NOT the code, must be the project. Full rebuild.
-Run a few more times after rebuild didn't fix it.
-Google the issue.
-Stackoverflow must be wrong. The code is JUST like their solution.
-Run a few more times, but with your lucky underpants
-Reboot. Must be an operating system thing.
-Tea break. Give the issue time and it will fix itself.
-Run a few more times. Still unfixed
-Contact customer support.
-Walmart said they can't help.
-Consider writing your own language without this OBVIOUS flaw
-Kickstarter for c++++
-Raise $50,000
-Start a family
-Contact customer support again
-Run a few more times
-Now banned from Walmart
-Oh shit, missing a semicolon24 -
TODOs top 5
[x] create README.md with TODOs
[ ] add tests
[ ] write documentation
[ ] automate deployment
[ ] improve security5 -
Ranting here , about our fucked up life is like talking to a cat. You don't know if they are listening, you don't know if they care, but for some reason, it still helps ...3
-
Interview with a candidate. He calls himself "C++ expert" on his resume. I think: "oh, great, I love C++ too, we will have an interesting conversation!"
Me: let's start with an easy one, what is 'nullptr'?
Him: (...some undecipherable sequence of words that didn't make any sense...)
In my mind: mh, probably I didn't understand right. Let's try again with something simple and more generic
Me: can you tell me about memory management in C++?
Him: you create objects on the stack with the 'new' keyword and they get automatically released when no other object references them
In my mind: wtf is this guy talking about? Is he confusing C++ with Java? Does he really know C++? Let's make him write some code, just to be sure
Me: can you write a program that prints numbers from 1 to 10?
Ten minutes and twenty mistakes later...
Me: okay, so what is this <int> here in angle brackets? What is a template?
Him: no idea
Me: you wrote 'cout', why sometimes do I see 'std::cout' instead? What is 'std'?
Answer: no idea, never heard of 'std'
I think: on his resume he also said he is a Java expert. Let's see if he knows the difference between the two. He *must* have noticed that one is byte-compiled and the other one is compiled to native code! Otherwise, how does he run his code? He must answer this question correctly:
Me: what is the difference between Java and C++? One has a Virtual Machine, what about the other?
Him: Java has the Java Virtual Machine
Me: yes, and C++?
Him: I guess C++ has a virtual machine too. The C++ Virtual Machine
Me (exhausted): okay, I don't have any other questions, we will let you know
And this is the story of how I got scared of interviews29 -
This just makes me mad every time.
I have a friend who asks for help in coding and just reads and copies my whole code, doesn't even understand what's going on and just copies the whole damn thing (the variable names too). Also, says I don't know how to do it properly because I indent the code and he wants it all in a single line.
If there is any error in the code, just tells me that there is a problem and does nothing and keeps nagging me if I solved the problem every 2 minutes.
Once I solve the problem, just copies the stuff again and then brags to others about the code and takes all the credit.
After bragging, if someone asks him for help he just tried to match the code line by line and worry by word. And tells them their code is wrong if they are using a different method of solving the problem and asks them to do it like him.
Being an introvert, I don't go shoving my stuff in others faces and criticising their code.
But the professor knows I am good, so that works for me. :)17 -
After a year of college give everyone 2 hours to solve a programming problem in the language of their choice. Like implement a doubly linked list, or count the number of primes between two integers or something straightforward. Anyone who can’t do it gets kicked out of the major.
I’m sick of dealing with people who are 3 or 4 years into a CS degree, and can’t do 30-line programming assignments in two weeks. I might have to work with one of these clowns someday and I hope to God that my university doesn’t send them into the workforce with a degree.3
