Details
Joined devRant on 8/16/2016
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
-
After Hours of Coding.. I'm finally get in bed, but my mind can't overcome from fucking code and i can't sleep.
I don't know how to take proper and quick sleep after programming without taking any pills. Another side effect is after started programming 18 hr /day I'm losing my memory power, and can't remember some things properly.
And yes this image is Worth something to me... It describes my current situation.
Just one word
HELP !19 -
My mother forced me to buy winrar when I was ~10. They saw the licence popup every time I would open minecraft.jar to install a mod.
They are big anti-piracy supporters and so they thought I pirated winrar.
Well.... So for my punishment for "pirating" winrar, they made me buy it with my birthday money...
I moved to 7zip
Then linux.
Now I'm happy.8 -
PHP 🐘 is so damn easy to learn, run straighforward in all OSs, that anyone can start coding in no time. Therefore, the amount of crap code around, made by unskilled devs, is just *unbelievable*. 💩18
-
Not being able to directly read in inputs as any data type rather than string and thus having to convert it and check for Exceptions if users enter bullshit4
-
Looking for a job as a deveoper be like:
Job title: car driver
Job requirements: professional skills in driving normal- and heavy-freight cars, buses and trucks, trolley buses, trams, subways, tractors, shovel diggers, contemporary light and heavy tanks currently in use by NATO countries.
Skills in rally and extreme driving are obligatory!
Formula-1 driving experience is a plus.
Knowledge and experience in repairing of piston and rotor/Wankel engines, automatic and manual transmissions, ignition systems, board computer, ABS, ABD, GPS and car-audio systems by world-known manufacturers - obligatory!
Experience with car-painting and tinsmith tasks is a plus.
The applicants must have certificates by BMW, General Motors and Bosch, but not older than two years.
Compensation: $15-$20/hour, depends on the interview result.
Education requirements: Bachelor's Degree of Engineering.41 -
!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 -
>Building advertising platform
>Life is good
>Fire up the dev server and open in browser
>No assets
>What the fuck
>Check code and config for like an hour it's all good
>What the fuck
>Try incognito browser, it works.
>What the fuck
>Oh yeah. Adblock. Fuck.4 -
My boyfriend.
He's an amazing software developer, has a few more years of experience with me, and because he's not a colleague, I feel comfortable asking him dumb questions. Combined with his patience and willingness to explain things very thoroughly, it's helped my post college learning immensely.
I love that I can cook him dinner, and then go to him with a code smell that I found at work, and spend the meal discussing ways to make cleaner code. I'm not sure who the real winner is in that situation. Probably my employer, haha.23 -
Me: 1 is something, 0 is nothing, NULL is the absence of things
JuniorDev: wut
Me: You've got pizza in a box, that's 1. If there's no pizza in the box, that's 0. If there's no pizza and no box, that's NULL.
JuniorDev: OOH so there's no object to reference if I ask for a slice!
Me: *small tear*
Always explain things in terms of pizza. Always.25 -
!rant
This is one of the best explanation I have ever seen for the difference between SIGTERM and SIGKILL.
Picture credit : www.itsfoss.com8 -
A young guy I work with burst into tears today, I had no idea what happened so I tried to comfort him and ask what was up.
It appears his main client had gone nuts with him because they wanted him to make an internet toolbar (think Ask.com) and he politely informed them toolbars doesn't really exist anymore and it wouldn't work on things like modern browsers or mobile devices.
Being given a polite but honest opinion was obviously something the client wasn't used to and knowing the guy was a young and fairly inexperienced, they started throwing very personal insults and asking him exactly what he knows about things (a lot more than them).
So being the big, bold, handsome senior developer I am, I immediately phoned the client back and told them to either come speak to me face-to-face and apologise to him in person or we'd terminate there contract with immediate effect. They're coming down tomorrow...
So part my rant, part a rant on behalf of a young developer who did nothing wrong and was treated like shit, I think we've all been there.
We'll see how this goes! Who the hell wants a toolbar anyway?!401 -
I have this old lady that I help from time to time with her computer issues.
She is nice, so I feel compelled to help her.
Get a call one day.
Lady : "hello, my internet and email isn't working, I've tried everything, could you maybe help me?"
Me : "Sure, ill come over after work and check it out"
*arrive at her house*
Lady : "you see, none of the web pages load, and my email refuses to sync. Should I call (insert isp name), or can you fix it?"
Me : I'm sure I can get it, gimme a sec.
*find the issue in a sec or two, dunno how to tell her about it, she isn't totally stupid*
Me : "Uhh, I don't know if you checked, but the ether.. internet cable isn't plugged in"
Lady : *realizes the wtf moment I'm having, obviously feeling very stupid*
Me : "Don't worry, happens to the best of us"
Obviously I lied a little, most of us would probably check the damn cable. Sometimes is just better to make people not feel like its their fault. People learn better when they don't feel like something is making a fool of them.
I have helped this lady with so many things that are just straight out of this world.
The one time she tried emailing 37mb tiff files over her 315kbps network.
Another time she said her email was not syncing, so I went to her house and clicked the "sync" button.
She even once phoned me to get their wifi password.
I just like helping her, somehow it makes me feel as if we all have something to learn.6