Details
-
AboutI hate everything
-
SkillsSystem Admin MariaDB Mysql Red Hat Phyton Oracle Linux Debian Based
-
LocationMalaysia
Joined devRant on 3/18/2019
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
-
This is PART 1/2 of a series of rants over the course of a software engineering class years ago.
We were four team members, two had never failed a class, I’ll refer to them as MT and FT, male and female top students, respectively, and an older student with some real world experience who I’ll refer to as SR.
Rant 1: As I was familiar with the agile methodologies I became the Scrum Master and was set with the task of explaining it to the team members, SR showed up late and nobody seemed interested in learning new methodology. At this point I knew we'd have trouble as a team.
Rant 2: FT made up her project proposal without informing anybody, which required a real client/product owner. We only figured it out after her proposal was accepted as the project, so we ended up working with fake requirements.
Rant 3: This one is partly my fault. I researched first and then worked, which meant I was the last to turn up my work. In one activity MT pressures me and I agree to a deadline so everyone can send their work to the teacher in a timely manner. Since I was the last to finish, I was also asked to give the doc some formatting, which I did in a hurry so it wasn't the best.
The next day MT and FT start complaining about me, saying I took too long and that they expect me to do better next time or else. At the same time they were stressed and in a hurry because we had to explain the project outline in front of the class and they didn't study.
Turns out copying and pasting all your work in less than an hour means you don’t learn anything. FT actually asked me for help days before and I sent her a website in English, which she wasn't very good at, so she just ran it through Google Translate and called it a day.
Later FT called me rude for interrupting MT in the presentation, which I did because he started making up stuff about the project.
Rant 4: SR expressed his dislike for school through profanity in variable names and commit messages. This caused MT and FT to dislike him. I thought it was immature but if anything it should’ve been reported to the teacher and move on.
Rant 5: I was stuck trying to get the REST API working for the project Admittedly this was my fault, too, because I was pushing for the usage of things nobody was familiar with for the sake of learning. This coupled with SR’s profanity led to drama and the progress was dropped, starting over from scratch.
At this point I stepped down from the Scrum Master role as nobody seemed to listen anymore.4 -
What the actual fuck?!!! ifconfig: command not found even after installing net-tools, just wtf
Who the fuck thought replacing nicely formated output of ifconfig with that garbage that "ip a" shits out was a good idea?!!
I will hate whoever did that until they burn in hell11 -
I was very troubled as a teenager. I had some pretty intense family issues that led me to smoking cigarettes at 12, marijuana at 13, and drinking everyday at 15. By 17, I was using other "party favors", as we called them, on an every day basis. I left high school at the beginning of my final year, about a week before I turned 18, moved out of my family's home and started working three different part time jobs.
This was the lowest point of my life. I've never felt so much like a fuck-up and loser than back in those days. I hated myself, hated what I had become, hated everything I did. Hate hate hate. I spent a year like this, pitying myself, seeking sympathy from people when I shouldnt have been, basically seeking out someone who would tell me that I wasnt so awful.
That never happened. I only deepened the hole that I had dug for myself.
Then I got angry. I thought it wasn't fair that everyone else was enjoying life except for me. I wanted to find a passion. I wanted to find excitement again. I wanted to look forward to something else besides going back to bed.
When I turned 19, I decided that I was going to take control of my life because I was so angry with my position at the time.
I put myelf into college. I made myself stay awake and focus on schoolwork and internal improvement. I started facing my flaws and defects head-on and conquering them rather than letting them eat me from the inside out.
Now, I am only a couple months away from turning 21.
I rarely drink now. I quit smoking cigarettes after almost 9 years.
I graduate this December, and enroll into my next degree program in January.
Today, I signed employment paperwork with the company I interned at over the summer. I am now a full-time DevOps Engineer with salary, bonuses, 401k, and full health coverage.
My boyfriend and I just moved into our own house that we are renting together. No more needing shitty roommates.
I have most of the debt that my mother left in my name paid off.
A couple of years ago, I couldn't have cared less about my life or how I turned out. I truly expected to get arrested, wind up homeless, or just flat-out end up dead.
I never thought I would see myself where I am today.
I am extremely proud of myself for turning my future around. I know some of you may read this and think I'm an idiot, or that this seems trivial because I am so young. Thats okay.
I have learned that hard work always pays off, and that sometimes you must sacrifice what is expedient to gain what is meaningful.9 -
!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 -
I have been working on an app for the startup i co-founded as only developer fulltime for the last 8 months...
I have yet to buy my first bread from the money i dont earn..
woops...2 -
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 -
!dev && dev_workflow
Hey guys, what are your favorite truly wireless headphones?
For context:
- my OSes: Android (phone), MacOS (laptop), iOS (tablet).
- my getting in love with wireless audio story: I have been using some Chinese ones off AliExpress just to test out the truly wireless waters, their sound quality and pairing experience especially on Android is pretty shit but the ability to forget that you have headphones in your ears and just listen to music obstruction-free is 🔥 but they are now dying so I am looking for a replacement.5