Details
-
Aboutresearcher in mobile and wearable tech
-
Skillspython, machine learning, data analysis, [learning] arduino
-
Locationcalifornia
-
Website
-
Github
Joined devRant on 11/7/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
-
I have a teacher that does nothing but reading from powerpoint slides.
Wrote a script that does a better job.19 -
!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 -
"IoT is awesome~!"
"What things about it do you love?"
"Hm, hold on a second. Oh dear."
"Something wrong?"
"Just a sec. My Fridge is getting DDoS'd"14 -
I was told that my comment on another rant needed to be its own rant. So here it is:
I had a client that runs a tattoo shops website to be updated and more modern. He wanted nothing to do with looking at or approve mock ups or designs so I just did my thing and took care of it. Once I was finished I showed him what I had and said “now I just need some content from you all so I can replace all the placeholder text and images”.
He seemed completely onboard. Took down notes of all the content needed, assigned all of it out to his artists to gather what I needed and provide it to me.
After 6 months, and several emails asking if they ever got that content together I finally get a response:
“LOOK MAN, if you didn’t want to do the site then you shouldn’t have accepted the money. I know you don’t need all these from us to finish up, you’re just stalling! I need the site up now!”
So I’m like “Sure man, I’ll publish it exactly as it stands now.”
An hour later I get a call “who are these people in these pictures? Why do you have our pricing all wrong? Why is everything in French or something (Lorem ipsum)? I just need my money back at this point.”
I explained that he’s not getting his money back because I already did my part, but just because it’s important to me that a client is satisfied (and seemingly what he wants is money) I can waive his hosting fee for the next 3 years.
It’s been a year now. Sites still up in all “French”, wrong pricing, random stock photos. Couple weeks ago he called to apologize for being a dick before.
Still haven’t gotten any content to finish up.
I don’t understand. It’s like these people think if you want to publish a book for instance that you just give the publisher the title you came up with and they’ll fill in the pages with story/info for you.
I’m a web developer, not a content manager.39 -
Root ain't givin' no fucks no mo'
My boss just demanded that I join a conference call. So, I call in, and there's three other people there.
He starts chewing me out for talking with some vendor directly (their VP emailed me directly and asked for a few things, and i was instructed to make him happy). Apparently I used "confusing wording" and "did not talk his language." Bossman was really getting into gear for a ten-minute berating.
It turns out that the guy in question only read half of my first email, and totally ignored the second email where I told him everything was finished and live and working. I told my boss quite bluntly that the guy should have read what I had written, and that he was an idiot. The boss's defense of the guy? "Well, he's a sales guy." I just laughed at him.
Later, bossman started in on me (once again) for not making enough progress on this ridiculous shared-spreadsheet sales tool he wants, saying "We discussed this a week ago!"
I casually reminded him that we had talked about it for the first time ever on Friday night (today is Tuesday), and he had said it wasn't going to be a priority for the next three weeks(!). Again he stopped in his tracks. Again, I laughed at him.
Guy's a tool and I'm so done with caring.
Root's going to be flippant and angry. Root's going to have fun (:
What's he gonna do, fire me? 😂25 -
Have you ever wondered we programmers have so many strong communities.... Stackoverflow, devRant, Reditt, etc...
No other profession has such communities... Why? Why?
Because, we haven't built one for them.... 😂😁61 -
Developer: We have a problem.
Manager: Remember, there are no such things as problems, only opportunities.
Developer: Well then, we have a DDoS opportunity.52 -
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 -
The problem with being a programmer...
I just broke up with a girl I've been seeing the past 2 months, that I was really into.
But in the end, it became a question of, either i'm with her, or I'm with my work.
I don't think that would happen with other professions, at least, not as easily.
I think, with other professions or projects, you tell someone "I need to work" and it's really fucking understood. "Ok, you need to work"
They understand it. If I was a lawyer.. I have a case. if I was a carpenter, I have a wall to build,
or a house. Etc. All understood things. Or physical things that can be seen.
But with programming, first of all, I work my own hours, I write software and then sell it. I do it all myself, I own my own business. I don't have normal hours like a job, but I do know my requirements, which is at LEAST 8 hours a day of solid, uninterrupted work.
If I had a "job" it would be like "gotta go to work" and that would be it.
But, because I work for myself, and because the things I build, aren't like something you physically see, nobody gets it.
My parents, as supportive as they are, will never understand how I just implemented a new design pattern and like, leveled up because of it.
They see software... buttons, and even then, when I try to explain what excites me, it's like trying to get a 3 year old interested in calculus.
How could they possibly understand the richness of what I do, how fulfilling it is
and how much I love it, when all they see
is me on a computer, clicking keys.
The same for this girl I dated.
The only place I feel where people understand,
is here.
Do you have any similar experiences to share?
Would love to hear it right now.35