Details
-
Abouti am software engineering student, working and love creating a lot of things myself. I started coding when I was 13 (now 22)
-
Skillsc++, c#, SQL, Oracle, Assembler, Java
-
LocationZagreb, Croatia
Joined devRant on 7/31/2017
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
-
!rant
After over 20 years as a Software Engineer, Architect, and Manager, I want to pass along some unsolicited advice to junior developers either because I grew through it, or I've had to deal with developers who behaved poorly:
1) Your ego will hurt you FAR more than your junior coding skills. Nobody expects you to be the best early in your career, so don't act like you are.
2) Working independently is a must. It's okay to ask questions, but ask sparingly. Remember, mid and senior level guys need to focus just as much as you do, so before interrupting them, exhaust your resources (Google, Stack Overflow, books, etc..)
3) Working code != good code. You are an author. Write your code so that it can be read. Accept criticism that may seem trivial such as renaming a variable or method. If someone is suggesting it, it's because they didn't know what it did without further investigation.
4) Ask for peer reviews and LISTEN to the critique. Even after 20+ years, I send my code to more junior developers and often get good corrections sent back. (remember the ego thing from tip #1?) Even if they have no critiques for me, sometimes they will see a technique I used and learn from that. Peer reviews are win-win-win.
5) When in doubt, do NOT BS your way out. Refer to someone who knows, or offer to get back to them. Often times, persons other than engineers will take what you said as gospel. If that later turns out to be wrong, a bunch of people will have to get involved to clean up the expectations.
6) Slow down in order to speed up. Always start a task by thinking about the very high level use cases, then slowly work through your logic to achieve that. Rushing to complete, even for senior engineers, usually means less-than-ideal code that somebody will have to maintain.
7) Write documentation, always! Even if your company doesn't take documentation seriously, other engineers will remember how well documented your code is, and they will appreciate you for it/think of you next time that sweet job opens up.
8) Good code is important, but good impressions are better. I have code that is the most embarrassing crap ever still in production to this day. People don't think of me as "that shitty developer who wrote that ugly ass code that one time a decade ago," They think of me as "that developer who was fun to work with and busted his ass." Because of that, I've never been unemployed for more than a day. It's critical to have a good network and good references.
9) Don't shy away from the unknown. It's easy to hope somebody else picks up that task that you don't understand, but you wont learn it if they do. The daunting, unknown tasks are the most rewarding to complete (and trust me, other devs will notice.)
10) Learning is up to you. I can't tell you the number of engineers I passed on hiring because their answer to what they know about PHP7 was: "Nothing. I haven't learned it yet because my current company is still using PHP5." This is YOUR craft. It's not up to your employer to keep you relevant in the job market, it's up to YOU. You don't always need to be a pro at the latest and greatest, but at least read the changelog. Stay abreast of current technology, security threats, etc...
These are just a few quick tips from my experience. Others may chime in with theirs, and some may dispute mine. I wish you all fruitful careers!221 -
2nd year of college, in computer science course and they're teaching us how to create star patterns using 'for loop'. Feels like 9th grade all over again (sigh)6
-
Difference between C# and Javascript
Me: Hold my cup of tea.
C#: That's not a cup of tea.
Me: Hold my cup of tea, with two teaspoons of sugar in it.
C#: That's not a cup of tea with two tea spoons of sugar in it.
Me: Hold my cup of tea, with two teaspoons of sugar and milk in it.
C#: That is not a cup of tea, with two teaspoons of sugar and milk it.
...
Me: Hold my cup of tea.
Javascript: I'll hold your cup of coffee.31 -
It saved me from suicide.
You have to understand first that things in India work differently. Academics are not personal, but a social business. Academic competition in India is very high and not in a good way, or for the good reasons.
As a teenager was sent off from my home to the other side of the country. I didn't like it. My studies suffered, and I failed my exams. Came back home and faced months of emotional abuse (guilt trips, scornful comments, plain insults) from my parents, neighbours and relatives. Indian society is just built that way. They didn't know they were damaging my psyche, or they were too angry to care. Lots of other shit (lost friends, lost love) happened at roughly the same time period and everything started to fall like dominos.
I fell into severe depression. Lost appetite, lost sleep. Nothing mattered anymore. There were mornings when I would wake up and not get up from my bed for hours, and not even move a finger. Self-hate became the motto of the day. I became violent and anti-social. I would either be angry or trying not to break down and give up all the time. Many a night, I considered suicide. I would end up googling for easy ways out to take.
But what gave me a way out of the pains of my reality was programming. It helped my keep my head, figuratively and literally. It kept my mind distracted and gave me a sense of purpose. I would shut myself in, plug in my headphones, shut the world out and just experiment.
I am not saying that I am the best at what I do, but those sleepless and troubled nights, and many other similar nights over the years have given me a definite edge over my colleagues.
Even today, when everything is falling to pieces, I know I have something to fall back on. I still get episodes of depression every now and then, but I know I can always pick up a new project and distract myself. It probably isn't healthy, but eh...
I am alive. I code. I kick ass. My colleagues respect and value my opinion. I love my job.
Computer does what I tell it to do (mostly :p) and I feel good. Because for that small moment, I am in control of everything. For that infinitesimally small moment of my average, boring, and somewhat painful life, I am God.51 -
At one of my former jobs, we devs had to do all sorts of non-dev work, such as writing quotes and even contracts!
The CEO of that company had this naughty habit to contact devs directly without delegating through the CIO. Sure, if it's really urgent like when some system is down because of a bug, go ahead and disturb a dev. But interrupting coders to write some freaking quote? Come on!...
Once, that CEO asked me to stop everything I was doing to write a quote to a customer ASAP, as this was really urgent.
I spent several hours writing that quote. It had to be done right as any specifications in our quotes were used in our agreeements and were referred to in the case of any dispute. So not only were we devs and salesmen in the same time; we also needed to be lawyers.
When I was done and delivered the quote to the CEO, he told me he had no intention to take on that customer in the first place. Instead, he wrote a polite we-are-not-interested e-mail to the customer and cc:d it to me just so that I could read for myself how very sleek a businessman he was.
Me: why did I have to write that quote when you knew all along that you were not going to use it anyway?
Him: It's for your own personal development.
Another naughty habit of that same CEO is that he made "jokes" and remarks that I found inappropriate, such as "You walk like a drunken sailor".
Later, he decided to discontinue our team/product because "it isn't proftable". Well, what do you expect when devs are forced to waste half day completing pointless tasks?!
It was for the better anyway, and I was actually relieved when I left the company. I'm still thinking though, that the real reason he sacked me is that I am too honest and not the docile kind of employee that would be ideal for him. I did question some of my tasks, and worst of all: I didn't laugh at his stupid jokes.1 -
hello devRant!
i've been lurking for about a week but i finally decided to activate my account and introduce myself :>
this seems like an awesome community and i'm glad to be a part of it!14 -
He gave me task, and I estimated it will take 2 (120 minutes) hours...
He came after 20 minutes to check the progress... Then he came after 40 minutes... Then he call me after 70 minutes... Then he came again after 90 minutes... Then I delivered the task in the time with my resignation letter draft.9 -
Client on fiverr.com won't give me SSH access and I am unable to finish my work...
And the client has no Linux knowledge and is unable to set things up my himself.2 -
Dear people who complain about spending a whole night to find a tiny syntax error; Every time I read one of your rants, I feel like a part of me dies.
As a developer, your job is to create elegant optimized rivers of data, to puzzle with interesting algorithmic problems, to craft beautiful mappings from user input to computer storage and back.
You should strive to write code like a Michelangelo, not like a house painter.
You're arguing about indentation or getting annoyed by a project with braces on the same line as the method name. You're struggling with semicolons, misplaced braces or wrongly spelled keywords.
You're bitching about the medium of your paint, about the hardness of the marble -- when you should be lamenting the absence of your muse or the struggle to capture the essence of elegance in your work.
In other words:
Fix your fucking mindset, and fix your fucking tools. Don't fucking rant about your tabs and spaces. Stop fucking screaming how your bloated swiss-army-knife text editor is soooo much better than a purpose-built IDE, if it fails to draw something red and obnoxious around your fuck ups.
Thanks.62 -
www.crossinstall.com
Go fuck yourself. They're the company that makes those pain in the ass mini-game ads. You know, the ones that aren't even relevant to the game.
"Oh look! A city building game. Let's advertise it with a tower defense game!"9