Details
-
SkillsJava, React, survive on low budget
-
LocationGoiânia, GO, Brazil
-
Github
Joined devRant on 6/4/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
-
!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!219 -
Boss(Engineer Degree): Did you find any solution?
Dev: Option A is not possible, so i'm analyzing Option B.
Boss:(Sends me the first Google search result of Option B)
My god! I'm in presence of an illuminati! You save my day.2 -
Does anyone know a good book for learning PHP? I want to know more about back-end development and would like some recommendations. I've been programming mostly in Java before and also have experience with SQL, HTML and CSS.
If anyone could suggest a book or any kind of advice I would really appreciate it. I've found some interesting ones online like "PHP & MySQL Web Development – by Luke Welling & Laura Thompson", but would like to hear out first people who know more about this programming language.6 -
at a recent interview:
🕴️ interviewer: are you familiar with PHP?
Jr Me 👶: well I'm currently studying it but I thought this was a front end position? I'm looking to work with js, sass and UI design.
🕴️: Well PHP is frontend and we are working with it in our CMS.
👶:... *Getting weird WordPress flashbacks*.. I think I'll continue looking but thanks for your offer.
Later that day I checked if their websites have wp-login.php and woop de fucking doo... It does.. as well as all their clients sites..
Dodging bullets like the freaking Choose one! Ps. Second time this happens.. gotta start checking this before going to the interview..6 -
Not a specifically dev related story, but absolutely rant worthy.
Today I was working from home, and my wife called me to tell me that some awful person had thrown a young cat into the dumpster at her work.
To that person - you are a scumbag. You’re lucky no one left you alone in a hot car as a kid, let alone a dumpster. Seriously, why? Why is it so hard to take it to a shelter?
Anyway - I went and bought a whole bunch of cat stuff - I grew up with cats but I’ve never had one on my own. We’re at the vet now. I think we’ll name her Curry (after Haskell Curry, and lovely spicy dishes).22 -
Today we presented our project in Embedded Systems. We made our so called "Blinkdiagnosegerät" (blink diagnosis device) which is used to get error codes from older verhicles which use the check enginge light to output the error. (for reference: http://up.picr.de/7461761jwd.jpg ) This was common for vehicles without OBD.
We made our own PCB, made a small database for 2 vehicles and used a Suzuki Samurai instrument cluster for the presentation (hooked up to an Arduino UNO and a relay for emulating some Error Codes)
Got an 1.0 (A) for the project. Feel proud for the first project done in C++ and making our own PCB. So no rant, just a good day after all the stress in the last weeks doing all assignements and presentations.
Next week we hopefully finish our inverse pendulum in Simulink and then the exams are close. :D19 -
Working on a fuck off/you message service. You can easily generate a fuck off/you message and send it to someone.
No clue why I've (nearly) made it, maybe because I'm sick at home and wanted to make something.
It's nearly working though, yay.16 -
I just started working on a little project to browse devrant from terminal. It converts images to ascii art!43
-
Hey fellow devs,
I'm proud to say, that today I've passed my final step/exam of my apprenticeship.
So now I'm officially an IT-Specialist - Software Development or "Fachinformatiker für Anwendungsentwicklung" in german.
I'm so fuckin' relieved and happy that this chapter is now finally closed and the real fun can begin!
My new job - indeed the old one with 4x payment and just a 32 hour week instead of a 40 hour one.
Now I will cheer and drink as much whiskey I can find out there! :D
PS.: This baby (pic related) was my presentation device today. One member of the commission had to laugh, a ranter as it seems! ;)16 -
So I’m installing all the updates to Xcode and OSX to get ready to make an app update. Get ready, restart for the OSX update, reboots about 3 times. Apple splash screen comes up... Alright that was a pretty fast one...and then FUCKING FRUIT FUCKERS6
-
I can only imagine what goes through clients’ tiny brains. Do they really think: “oh I know what will get shit done, insult the developer, his work, and demand things be fixed while saying the whole system is broken even though they have multiple times in the past demonstrated that it was either me using it wrong or an extremely quick and simple fix. I also have a problem with a few listed items in particular not the whole system, but I’m gonna insult everything.”
Fucking rude fucks! -
!dev but since dev can still give you headaches:
Ibuprofen is damn close to magical. I fully understand the chemical mechanism by which it works, and it still don’t make sense how that shit can make you a new person in 45 minutes.2 -
This 3 day weekend couldn’t come at a better time! Today has done everything it can to delay it and everything has been a superb annoyance!
It started off with our internal systems going down, a frustratingly tedious project proposal process, our phones went down, off the wall calls to support all day causing them to ask me junk.
As a parting gift the pending windows update and it completely crashed my development VM and corrupted my install of virtual box. I had planed in only working a half day, but worked 6.5 hours, hit traffic al over. Was late to the event.
Not I get here and there’s a bunch of smokers outside and I could reallllllly use a drag. But I’m not gonna. 😒
Just ready to kick back and do non computer things til Tuesday. 😎 -
I know Windows update rants are a dime a dozen but HOW IN THE FUCK DID YOU MICROSUCKADICK BOOT LICKERS SHOVE SO MUCH HORSESHIT INTO THIS UPDATE THAT IT UNINSTALLED VIRTUALBOX? The hell?
Really, I rebooted my PC, short cuts everything, gone! Newer stuff is there plus any restore point would have had VirtualBox installed, so what the hell.
I’m stating to think that when Windows says “all your files are exactly where you left them” it’s a best guess because it just completely fucked with all your files for no reason and tried to put them back but it’s not so sure.4 -
Not using all my time. I really don’t apply myself sometimes. Sometimes that means not using work time efficiently, sometimes that means I get stuck on a simple problem for too long because I don’t think through it. Also, I’m trying to love coding more. It takes a lot of code to get a small result sometimes, and that’s ok. I got hooked on being able to do big things with little code from the start. As we get better we know there’s more that can be done, but we are more familiar with just how much work it really is. At the same time we are more capable than ever of doing it. Just gotta embrace the suck, then love your finished product.1
-
Once again:
BOSS and Client IT’S URGENT IT’S CRITICAL
ME: IT’S 4:30pm on FRIDAY AND THIS IS THE FIRST I’VE HEARD OF IT IT IS NOT THAT HOT2 -
It’s so crazy to me how my bosses sometimes wake up and it’s like they get in a groupthink that we are stuck on technology from five years ago. The company has grown our paths have simplified, our tools have gotten more powerful.
Everybody forgets that a new feature has come out occasionally, but sometimes for weeks at a time they will go about explaining things the old way, or saying it can’t be done. Then they’ll come back around. This has been on and off for all of this year basically.