Details
-
AboutProgramming student
-
SkillsC, vim, JavaScript
-
LocationFrance
Joined devRant on 7/14/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
-
Not my mom, but my wife's whole family. I'm a software developer.
So we're invited to her grandmother's 85th birthday celebration with pretty much every family member they could think to invite. 100+ people, and we all sit down in a circle in a huge room to watch a video that my wife's father and aunts/uncles put together.
They start the video and there's no sound. I'm a software developer, so I'm not an expert in hardware issues. I try to turn invisible, because every tech person knows what comes next, and this is in the center of a room of people I don't know.
After about 15 minutes of people struggling to get the audio working, one of the people remembers I "work with computer". Soon I have a dozen people calling me to the center of the room.
I begrudgingly make my way to the computer and projector. Upon inspection, I find that the computer is connected via VGA to the projector.
Me: "This cable only carries video. You need a different kind of cable, or you can hook up an AUX cable--the kind you use for headphones."
Other Guy: "I used this cable earlier and the audio was working."
Me: "...that's weird. Well, can we try plugging in an AUX cable?"
Yet Another Guy: "Will this help?" Holds up an HDMI cable
Me: "Oh, yeah! That should do it."
Other Guy: "I tried plugging that in, but it didn't change anything."
Me: "Hmmm..." Quickly unplug VGA and plug in HDMI, then click play.
The sound comes out in its full cheesy music glory. Everybody cheers, and I walk back to my seat. Throughout the rest of party, I'm approached by various other family members who ask me if I can fix X since I'm a "computer guy". Isn't it great to work in tech?12 -
My girlfriend has these :D
(called Code:Deck - available here https://varianto25.com/playing-card...)14 -
I'm a hobby programmer and i don't hav any programming ideas! How do you all get programming ideas?7
-
Need to learn JavaScript.
My question is: What good books/websites/ youtubers etc are out there that have good explanations.
Thx in advance.64 -
Can anyone give me tips for my first Interview for the web developer spot of a large local company?2
-
!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!222 -
If found a Website with a nice Guestbook. Funny thing: HTML-Code and JavaScript-Code in the message was not getting escaped. So I wrote a little JS-Script wich alerts “Nope“ and the then redirects to pornhub.com after page load.
After about 2 WEEKS of funny redirecting, they updated their site and HTML-Code is now getting escaped.10 -
Today we interviewed a _very_ good Angular1 Dev, by chance we showed him the forked ngRouter module we use, after some debate he explained that we were using it incorrectly.. I asked if he'd used it before to which he responded:
"Yeah, I'm the guy who built it"
😅27 -
string excuses[]={
"it's not a bug it's a feature",
"it worked on my machine",
"i tested it and it worked",
"its production ready",
"your browser must be caching the old content",
"that error means it was successful",
"the client fucked it up",
"the systems crashed and the code got lost" ,
"this code wont go into the final version",
"It's a compiler issue",
"it's only a minor issue",
"this will take two weeks max",
"my code is flawless must be someone else's mistake",
"it worked a minute ago",
"that was not in the original specification",
"i will fix this",
"I was told to stop working on that when something important came up",
"You must have the wrong version",
"that's way beyond my pay grade",
"that's just an unlucky coincidence",
"i saw the new guy screw around with the systems",
"our servers must've been hacked",
"i wasn't given enough time",
"its the designers fault",
"it probably won't happen again",
"your expectations were unrealistic",
"everything's great on my end",
"that's not my code",
"it's a hardware problem",
"it's a firewall issue",
"it's a character encoding issue",
"a third party API isn't responding",
"that was only supposed to be a placeholder",
"The third party documentation is wrong",
"that was just a temporary fix.",
"We outsourced that months ago.","
"that value is only wrong half of the time.",
"the person responsible for that does not work here anymore",
"That was literally a one in a million error",
"our servers couldn't handle the traffic the app was receiving",
"your machines processors must be too slow",
"your pc is too outdated",
"that is a known issue with the programming language",
"it would take too much time and resources to rebuild from scratch",
"this is historically grown",
"users will hardly notice that",
"i will fix it" };11 -
Love working with atom using this theme in coffeeshops, making people think I'm a top hacker, when in reality I'm just stuck with css classes or something. Equally stupid.25
-
So guys i really need your help. My girlfriend started getting phone calls at odd hours, so I got suspicious and started tracking her phone. Then I found out that she has been going to this guys house at wears hours, then once when I was tracking her my computer froze, so what could it be? How do I fix my computer14
-
"C makes it easy to shoot yourself in the foot; C++ makes it harder, but when you do, it blows away your whole leg."
Bjarne Stroustrup -
Debugging C++ be like:
2 Errors Found!
*debugs 1 error*
96 Errors Found!
*throws laptop across room*3