Details
-
AboutProfessional software engineer
-
Locationin space
-
Website
-
Github
Joined devRant on 2/1/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 -
Do you guys drop the S from your variable names? I am constantly in a dilemma as to what makes more sense.
For example a SQL Table:
Books
----------
BookID
BookName
....
---------
OR
Book
---------
BookID
BookName
.....
---------
Or even in a language like C# or JavaScript:
const BOOKS
var books
let books
or
const BOOK
var book
let book
Even if you have multiple items in that variable/table it seems very redundant to ever have the s.
What do you guys think? Any input appreciated!
Happy coding!24 -
Why Apple?
Configuring my new MacBook Pro
• jre ✓
• jdk ✓
• Android studio ....
• let's see what we get when we type "git" in Terminal.. surprise!!! You have to download Xcode which is 5.30GB. Goodness. Can I cry now? 😭😭😭18 -
Long story short,
I made a repository on GitHub containing all the necessary files to build network-card specific firmware that the developer Mellanox does not suply openly to the general public anymore.
Can they (Mellanox) do something to me for that? 😨
And should i pick a license for that repo?
The files were grabbed from either an old russian ftp who grabbed them from the mellanox page years ago while they were available.
Or from some programs appdata tmp folder where they magically appeared during installation.
The files are 2 different kinds,
Either a core firmware textfile containing encoded binary 😵, or
Adapter specific config files that could also be dumped from the adapter card itself.
In total, mellanox provides version compiled 2.9.1000,
I obtained "sources" for
2.9.1200
2.9.8350 and
2.10.0720
Which are massively better and needed for certain features and functionality. Like building in PXE.
Thanks1 -
Is php beautiful, or ugly?
Here's my php. The beautiful, and the ugly.
*nervously presses submit*16 -
Interview
HR: So .. tell us .. where do you see our AI acting in 5 years?
ME: Doing your job minus the stupid questions.
*silence*
Boss breaks out in laughter.
"Oh boy you're hired"12 -
Maybe, iOS developers get paid higher than Android developers because it's MORE STRESSFUL to use Xcode and deal with Apple Certificates.4
-
Presenting the inside of Xiaomi 5200 mAh power bank!
P.S. I tried Snapseed for photo editing and it's really nice ☺6 -
When you finally accept that the code will never be bug-free and instead make friends with the uncaught exceptions.1
-
The download manager is coming together nicely!
The idea is simple, all the downloads are multithreaded. It saves the chunks and then merges it together at the end. So far it uses 30-40mb for the whole thing!
Next stop, add queue management and then browser integration. The source code is here: https://github.com/tahnik/qDownload.
Don't blame me if you vomit once you see the code. I am still working on it and it will be clean soon. I would love to get some suggestion for the name of the project. It is "qDownload" currently and I fucking hate it.
@Dacexi is joining tomorrow to help with the UI. It's gonna be amazing 🤘24 -
Why do I create free services (at least free for now)?
Because one of my biggest dreams is to create a service which will be used by many many people.
A man can dream, right?
😞34 -
devRant should add a polls feature for simple questions with yes no answers or what version of linux people use etc maybe?18
-
Yesterday's JR web dev interview:
👨🏻💻: Experience?
👶: Well JS, pyhton, UX Design and bit of Sass.
👨🏻💻: Feel like you'll have a hard time learning PHP?
👶: Well if it needs to be PHP, I can learn it.. Are you using a certain CMS?
👨🏻💻: Cool, good. Yeah we're using WordPress and need to support our sites for IE8.
👶:... Well.. ehm.. *runs away and screams in panic 💨*20 -
Developers - The Real Superheroes.joke/meme superheroes late work i need to restrict my devrant usage overtime but no pay developers i should be asleep by now4