Details
-
AboutHey Guys, I am Andrew Jones a passionate guy who lives in New York, USA.
-
LocationNew York
Joined devRant on 11/18/2022
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
-
back to devrant, yay!
closed my account when i entered a really nice company, but after a year it was taken over by another one that was not-so-good at all, started working for another startup and, BOY, i really didn't miss ranting about work, but now i NEED a place to let this all up, little by little, somewhere, before my brain melts
current startup is one of those founded by rich dudes who had an "amazing" idea that, as time passed, turned into a monster that not only eroded the team from inside, but also made us see how spoiled the bosses are11 -
Splash pages. Remember that crap from 20 years ago? That was a home page with some "click to enter" nonsense to get to the actual home page. Laughably stupid.
Today's empty home pages where you have to scroll down to get to any real content is exactly the same moronic pattern, just by another name: showing off useless design wankery and forcing user interaction to bypass it. Fuck you if you still do that shit.29 -
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?!400 -
!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 -
Dev: This could be sooooo easily optimized...
Me: Uhm. Don't think so. What's your idea?
Dev: Just use threads.
Me: Nope. Problem requires 3 shared resources per process step, it won't be faster by threading. Shared resource will only lead to locking contention, decreasing performance.
Dev: I don't think that will happen. Can you PROOF to ME that this will happen?
Me: It was your suggestion, so you should proof me wrong. Nice try, but no thanks.
Dev: Yeah, but it's too slow and it should run faster.
Me: If you cannot find a better approach than the current one, it runs as fast as it can while providing correct results. That's not slow. That's just working as intended and designed.
Dev: Yeah, but it's still slow.
....
You know these conversations where you just wanna rip some people's face off, stick it in the shit hole they use to talk and toss them out of the window....
Yeah. Had those conversations today.10 -
Any day when I'm manic. Can work 12 hours without feeling tired. Also, 30% intelligence boost. Feeling like a god. Solving people's problems in minutes left and right.
It's unfortunate it only last a month tops, with the remaining year being deep depression. Matter of fact, I got diagnosed with bipolar type I when my psychiatrist mapped my awards from released products and articles to the timeline, and it resembled a bipolar cycle.6