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
Search - "be humble"
-
Worst dev I've interviewed?
"Archie" ran his own consulting business for almost 20 years. Prior to his interview, Archie sent HR (to send to us) his company's website, where he had samples of code for us to review (which was not bad, this guy did know his stuff).
What I found odd was Archie was the lone wolf at his company, but everything I found about him (the about page, his bio, etc), Archie was referred to as 'Mr. Archie Brown'.
Ex. 'Mr. Archie Brown began his humble career and 'Mr. Archie Brown is active in his church and volunteers his time in many charities ...'
Odd to refer to yourself in the third person on your own site, but OK, I like putting hot sauce on my mac & cheese (no judgement here).
Then the interview..standard stuff, then..
Me: "Given your experience, this is an entry level developer position. Do you feel the work would be challenging enough for you?"
Archie: "Yes, Mr. Archie Brown would have no problem starting at bottom. You see ..."
Almost any time he would reference himself, instead of 'me' or 'I', he would say 'Mr. Archie Brown'. As the interview continued, the ego and self-importance grew and grew.
My interview partner wanted to be done by using the escape clause, "PaperTrail, I'm good, do you have any questions?"
Yes, yes I do. I was having too much fun listening to this guy ramble on about himself. I made the interview go the full hour with the majority of time 'Archie' telling us how great he is.
The icing on the cake was my partner caught his gold cuff-links and tie-pin where his initials and how he kept raising his hands and playing with his tie to show us (which I totally missed, then was like "oh yea, that was weird")
After the interview, talking with HR:
HR-Jake: "How did it go?"
John: "Terrible. One of the worst. We would have been done in 10 minutes if PaperTrail didn't keep asking questions."
Me: "Are you kidding!? I had the best time ever. I wish I could have stayed longer."
HR-Jake: "Really? This guy was so full of himself I wasn't sure to even schedule with you guys. With his experience, I thought it deserved at least a round with you two. You think we should give him a chance?"
Me: "Hell no. Never in a million years, no. I never in my whole life met anyone with such a big ego. I mean, he kept referring to himself in the third person. Who does that?"
HR-Jake: "Whew!...yea, he did that in the phone interview too. It was a red flag for us as well."
Couple of weeks later I ran into HR-Jake in the break room.
HR-Jake: "Remember Mr. Archie Brown?"
Me: "To my dying day, I will never forget Mr. Archie Brown."
HR-Jake: "I called him later that day to tell him the good news and he accused me of being a racist. If we didn't give him the job, he was getting a lawyer and sue us for discrimination."
Me: "What the frack!"
HR-Jake: "Yep, and guess what? Got a letter from his lawyer today. I don't think a case will come in front of a judge, but if you have any notes from the interview, I'll need them."
Me: "What are we going to do?"
HR-Jake: "Play the waiting game between lawyers. We're pretty sure he'll run out of money before we do."
After about 6 months, and a theft conviction (that story made the local paper), Mr. Archie Brooks dropped his case (or his lawyers did).23 -
Spending 5 years at University with a friend....uh???
Let me explain...
I have a friend. A very good friend I can say. I know him since 18 years but I started being everyday with him at the beginning of my "University's journey".
And when I say everyday, I am not joking...every lesson, every exam, every project...
The problem is that he is one of the smartest person I have ever met in the "scientific field". So? He is also unable to say that he doesn't understand something. He is unable to say the he is wrong or to admit that someone else is better then him.
Let just say that he is not good in "relating to other people".
I am very smart too and suddenly he started to fail where instead i was doing good. Jealousy, anger. Every occasion to point out my errors. Every occasion to say to the others that I am stupid and he is smart.
But I know him and I am not like him. So I continued to stay with him, work with him and also going out with him. Because he is my friend.
And you know what? After 5 years he started to be more "human". I learned so much from him and he learned to be respectful and humble.
It was a very stressful period but thanks to that I know that I can be strong and work hard also when someone try to stop me. I am not afraid to say my opinion just because someone is yelling at me. And I know that I can go over stupid judgements and still work good as a team member.
That's it.
Be respectful. Be patient but defend your opinions. Trust yourself but listen and learn from everyone. And if sometime you fail, remember that it's normal. No one is perfect. No one can be perfect alone.
I hope that this rant can help someone else.
Good week to all of you.7 -
Attended one of the best meetups ever. To give you an idea how awesome it was..
Speaker took the first ~20 minutes introducing himself.
His intro card deck kept referring to himself in the third person (he is the only employee in consulting 'company'). Ex. "Mr. Smith began his humble career .."
The powerpoint presentation began with him clicking each page, not executing the slideshow (ex. pressing F5).
Finally someone asked "Can you make slide bigger?"
S:"You can't read that?..um..sure...I guess .."
Starts fumbling around the zoom ...
Dev: "No, can you start the slideshow?"
S: "I don't know what you mean...there...I zoomed it, is that better? Now I can't see my notes..just sec.."
<fumbles again with the zoom>
Dev: "No, not zoom, start the slide show, press F5"
S: "Oh...you want me to F5 it...OK..."
<he *clicks* the slide show button>
Finally getting into code, trying to get out of powerpoint ...
S: "How do I get out of this fullscreen?.."
Dev: "Hit escape"
S:"No..um.."
<keeps trying to click on 'something'>
S:"I see visual studio, but its not on the big screen... "
<keeps click on 'something', no one is sure whats going on>
Dev: "Hit Escape to stop the slideshow"
<finally hits escape, then able to put Visual Studio on the big screen>
S: "Ahh...there, I figured it out."
Speaker had no end of making wild/random statements like:
".Net Core is the future of Microsoft, if you're using .Net 4.5...forget it, its not even supported anymore."
"When I was at Microsoft Build, I asked them why not put all the required .Net assemblies in one directory. Looks like with .Net Core, they listened to me" (he was serious)
"I don't use SQL Server Mgmt Studio. Its free and it sucks. I use <insert a very expensive SSMS clone>, its great, you guys should check it out", then proceeds to struggle to open a query window to write some SQL.
"When you use .Net Core and EntityFramework, you have to write your own stored procedures. If a developer can't write stored procedures, he shouldn't be in this business."
I was on the edge of my seat, hungry for the next crazy bat-shit thing to come out of his mouth. He did not disappoint. BEST MEETUP EVER!9 -
There is one thing I have seen here in devRant. No matter how stupid rant you post no one trolls you. People are kind of humble here. They try to help you.
Just an observation, may not be true.10 -
I'm a new developer. Here is the top advice I've received:
0. Think like a programmer, outside of work too.
1. Programming is tough. It takes a certain kind of mindset to sit in front of a monitor and think it through a problem till the end. Develop that mindset.
2. Handwork pays.
3. Do it for fun. Be exceptional. Money will follow.
4. Care about the craft you build. Write such a beautiful code that your fellow devs would think about your code and have a nerdgasm.
5. Simple is beautiful. Anybody can make things complex. It takes a stroke of genius to make things simple.
6. Write modular code. It makes your code reusable and easy to maintain. Future developers who will work on your piece of code will appreciate it.
7. Share your knowledge. Unlike materialistic things, knowledge grows when you share it.
8. Add comments. You think you'll remember why you wrote that piece of code that way or a clever hack you created but trust me, you won't.
9. Be humble. You'll never know everything. Don't hesitate to ask for help.
10. Writing code is exciting! Of course there will be some frustrating moments. But don't give up! You'll miss a lot of fun.5 -
---- Startup RantLife ----
A senior developer joined the team, let's name him Bob, and this guy is really good no doubts about that.
He made suggestions, some improvements, but Bob is always waving his hands and says out loud that some part of the code base is really really bad.
I kept quiet until one day I had to pair with Bob to check a feature. Guess what happened, as usual, Bob clenched his fist and start pointing that this code is super ugly.
So let's check the history of changes and boom, Bob was the main writer.
That moment, I was completely silent, trying not to smile as Bob came up with an excuse, he never admits that he is wrong, now he needs a scapegoat and he starts blaming the process, the planning...
I believe that being humble and saying sorry is a quality that it requires time to develop.
So don't be like Bob, please :)12 -
Always be humble and always keep learning. No matter how good you get, there is always some better.4
-
My biggest tip to new developers? Embrace your ignorance, don't be embarrassed by it. Let it inspire you to learn as much as you can, let it humble you into asking questions when you're stuck, let it prepare you to change within an industry that is anything but static. Admitting you don't know something isn't a weakness, it's an opportunity 😃6
-
note to self : don't be too humble.
Why?
I just got Roasted in front of Advanced Programming class by a person who got an A in previous class by 100% copying other's work and change all variable and function name to differ.10 -
My boyfriend, actually. But I value the human aspect more than the tech genius in fairness. He may be no Linus Torvalds but I don't care and wouldn't change him.
Why him?
He's very kind to less experienced developers and always happy to help them. He teaches them not only how to solve things but how to get un-stuck the next time and what to learn.
His code reviews are inside out, not just a quick scan, he gives a chance to learn and takes one for himself too.
He takes pride in delivering great quality, well thought over code, on time.
He owns his mistakes and isn't afraid to admit when he makes them.
He reads a ton of tech books and always learns something new yet stays humble while discussing things he knows a lot about.
He has a ton of hobbies other than coding which he's good at.
Ah there, yeah whatever I'm a big softie today 😋 he's not on DevRant btw. Also sometimes I want to punch him too, but mainly he's a good guy :)5 -
My dev skills currently feel like England in the mid 1600's.
Everyone around me has already conquered some projects while I sit in the side fighting a civil war with myself while having very humble accomplishments.
But I'll show them. I'll show them all. While they grow weak and weary over the ages, I'm slowly but surely getting stronger.
In the end I will conquer and rule the waves like no other. I will build a dev empire that will be remembered for years to come.3 -
Long long ago there was a man who discovered if he scratched certain patterns onto a rock he could use them to remind him about things he would otherwise forgot.
Over time the scratching were refined and this great secret of eternal memory were taught to his children, and they taught it to their children.
Soon mankind had discovered a way to preserve through the ages his thoughts and memories and further discovered that if he wrote down these symbols he could transfer information over distances by simply recording these symbols in a portable medium.
Writing exploded it allowed a genius in one place to communicate the information he had recorded across time and space.
Thousands of years passed, writing continued to be refined and more and more vital. Eventually a humble man by the name of Johannes Gutenberg seeking to make the divine word of God accessible to the people created the printing press allowing the written word to be copied and circulated with great ease expanding vastly the works available to mankind and the number of people who could understand this arcane art of writing.
But mankind never satiated in his desire to know all there is to know demanded more information, demanded it faster, demanded it better. So the greatest minds of 200 years, Marconi, Maxwell, Bohr, Von Nueman, Turing and a host of others working with each other, standing on the shoulders of their brobdinangian predecessors, brought forth a way to send these signals, transfer this writing upon beams of light, by manipulating the very fabric of the cosmos, mankind had reach the ultimate limits of transmission of information. Man has conquered time, and space itself in preserving and transmitting information, we are as the gods!
My point is this, that your insistence upon having a meeting to ask a question, with 10 people that could've been answered with a 2 sentence email, is not only an affront to me for wasting my time, but also serves as an affront to the greatest minds of the 19th and 20th centuries, it is an insult to your ancestors who first sacrificed and labored to master the art of writing, it is in fact offensive to all of humanity up to this point.
In short by requiring a meeting to be held, not only are you ensuring the information is delayed because we all now need to find a time that all of us are available, not only are you now eliminating the ability to have a first hand permanent record of what need to be communicated, you are actively working against progress, you are dragging humanity collectively backwards. You join the esteemed ranks of organizations such as the oppressive Catholic church that sought to silence Galialio and Copernicus, you are among the august crowd that burned witches at Salem, the Soviet secret police that silenced "bourgeoisie" science, you join the side of thousands of years of daft ignorance.
If it were not for you people we would have flying cars, we would have nanobots capable of building things on a whim, we would all be programming in lisp. But because of you and people like you we are trapped in this world, where the greatest minds are trapped in meetings that never end, where mistruth and ignorance run rampant, a world where JavaScript is the de facto language of choice every where because it runs everywhere, and ruins everywhere.
So please remember, next time you want to have a meeting ask yourself first. "Could this be an email?" "Do I enjoy burning witches?" if you do this you might make the world a little bit of a less terrible place to be.6 -
After using StackOverflow for years, it makes me mad that the devRant community hates on it saying "i get downvotes", "people are assholes". But when you go ahead and see those questions, the Poster took less that 15 seconds to copy/paste their shitcode with poor indentation, no context, no question, no expectation description, and no result description.
YET, THEY DEMAND FREE HELP and for people willing to help, to BREAK THEIR FUCKING EYES reading your non indented and/or non preformatted crap of shitcode
Listen here you little shit, if you don't take at least fucking 5 minutes to let me know what the fuck are you trying to do, what the fuck have you tried, and what the FUCKING SHITFUCK you expected to happen, THEN DON'T GO RANTING LIKE A PRE-PUBERT GREASY KID ON WHY YOUR FUCKING QUESTION GOT DOWNVOTED.
The problem is YOU AND YOUR LACK OF CONSIDERATION TOWARDS OTHER DEVELOPERS, <BOLD>WHO ARE WILLING TO DO FIX YOUR SHITCODE FOR FREE</BOLD>
It took me a while to understand that, when I started posting years ago. But once I learned, it was extremely helpful.
SO SHUT THE FUCK UP, BE HUMBLE, AND WRITE A PROPER FUCKING QUESTION.
WHY AM I RANTING ABOUT THIS, YOU ASK? WELL SOME FUCKTARD JUST POSTED "java - if(Plot Number == booked)then change the color of CardViewBackground color and text color Recyclerview Android", AND THE FUCKING BODY IS JUST A COPY PASTE OF A SHITCODE JAVA CLASS.
WHAT THE FUCK DO YOU EXPECT TO GET WITH THIS???
OOOOHHHHH BUT, I'M SURE AS FFFUUUCKKKK HE'S GOING TO CRY TO DEVRANT ABOUT HIS FUCKING QUESTION GETTING 3 DOWNVOTES.12 -
Tired of stereotypes. It seems that if someone uses a Mac, is posh; if someone uses Windows is a silly cunt, and if someone uses Linux ... well, it seems that's the way to go, right? Well, no.
Suddenly the world is filled with script kids who come and indirectly recriminate you that you have no idea of computer science because you use Ubuntu instead of Arch. That has happened to me with a recently graduated kid.
Really? Do you really consider yourself a good developer only because you have Arch installed and you hate Windows and Apple?
Let people use the system and development software that they prefer most (or that one that their company forces them to use).
This kids have to be more humble and focus on creating better code, help their colleagues and know how to deal with clients.11 -
Give everyone a chance
If someone in your company/workgroup doesn't know something basic that you might take for granted, don't undermine them and mock them.
Everyone has to learn and it just breaks morale and motivation.
Be humble and think that you're not any kind of God and think that you wouldn't like the same thing happening to you.
People who mock others for not knowing stuff just piss the shit out of me.
Be humble guys4 -
As a junior developer, your primary goal should be to learn and absorb as much as you can, not to try to make a name for yourself. It's all too common that I see devs fresh out of college with this amazing gung ho attitude that quickly devolves into needing to feel like the smartest person in the room.
This leads to an unnaturally inflated ego, a feeling of self importance, and blocks you from truly understanding what is going on in the stack in front of you.
That's not to say you can't try to take on difficult tasks, just be humble and ask for help when you need it, and don't make assumptions that might lead to rework later.
I would much rather you ask me a question then put up a PR that has wildly different assumptions because you didn't fully understand the acceptance criteria of a particular task.
tl;dr - sit down, shut up, do your job, learn what you can as fast as you can.
Sincerely,
A very fed up Senior Dev5 -
devrant is the only community that I feel comfortable in.
I've been browsing since 2000 and been in many communities online so far, so that's saying a lot.
I've seen supportive comments towards me and others here, and that really makes me feel less hopeless.
I think the internet in general makes you feel like you're a number. Click the like and the sub button, just be one more in a million.
But here, you matter.
If you try to post something and you are sincere, but humble people will ++ and say nice comments.
If you get upvoted, you can WHO did it and what their online persona looks like.
It feels very organic and personal, which is saying a lot for a place like the internet.
In the standard online experience, people online take advantage of the anonymity to say shit they wouldn't online:
anything, from troll shit to presumptuous comments.
I don't understand how some people can connect being anonymous with denying themselves as moral beings.
Do these people walk around in real life fighting with every person that has an opposite point of view?
There's actual people out there that will read this post and think "what a fucking boy scout".
Sorry for having emotions.
how many fucked up people are there, so that devrant feels like a goddamn mirage?9 -
I couldn't care less for aggressive 20 year old devs opinions.
Everytime I see a post where someone is being an asshole making strong comments about software, I'm like "oh, how cute, he's trying to be taken seriously by insulting others".
Then I check history and it's just a flow of hateful comments and memes...
(I do mind respectful and humble 20 year olds though)14 -
Dunning-Kruger effect is strong with me.
Thankfully, one of the most important skills that I learned is active listening. I am less vocal about my silly thoughts and shitty opinions these days.
I don't feel dumb. Instead, I realise that I AM dumb.
The people in my new org are exceptionally smart and talented. Each everyone is a hand picked gem. This isn't a coincidence. Rather it's evident that they hire folks very carefully.
In my previous org, I used to be the one driving everything. Like the smartest guy in the room.
But here, I am just quiet in every meeting and I enjoy working 12 hours a day. I am the dumbest guy in the room surrounded by people who are brilliant and humble.
I truly feel fortunate and grateful to be part of such an amazing org and wonderful team. One of the best decisions I made in my career and life.8 -
[ ] be humble, but not unconfident.
[ ] Step out of your comfort zone. Don't apply to a job that is exactly like your last one.
[ ] A good team is the most important thing for a developer. Intelligent, and nice people to work with and to learn from is more important than the salary difference between jobs.
Try to 'feel' for a good team. Ask to be introduced or to look around when you finish the interview.2 -
DevRant is a wonderful community, and the last thing any of us would want it to lose it. I think DR should have ads. To think that DevRant grew so fast and large, yet they haven't implemented ads shows just how awesome these guys are. But, it worries me to think that it's only supported by merch and people paying for collab and avatar stuffs scares me. Just a small ad at the bottom of the screen, I'm sure most of us wouldn't mind, and if it helps these humble and amazing people who created DevRant, I would be more than happy.17
-
Well, devRant has turned me from a bigot arse into quite the humble and decent person, and on top of that, introduced me to some new series (well more so the users than the platform, but you know what I mean).
Binge watched Silicon Valley (season one, I just started) and learnt about dick to floor ratio.
Prior to that binge watched Mr Robot. Cannot remember who suggested that, so I cannot attribute the appropriate gratitude to the appropriate person here.
Add to that that I no longer claim one language to be holy amongst others. Yeah. I was that dick before, we all have a bad side. I'm just admitting it.
I sat down and started utilising other languages, and even found quite a few that did what I wanted more efficiently. Plus I have gotten to meet some sharp people and broaden my own mind.
Fuck I hate my job, but I see a fucking brilliant future for myself thanks to coding and the open mind that I have attained. I attribute this to devRant (perhaps it was lying dormant, but you guys awoke it.).
Enough chitty chat, I'm off to sleep and then code my balls off.2 -
Story time on my job hunt: Currently interviewing with Google during my notice period.
I always had a love hate relationship with Google. Unlike my hate towards Meta or Amazon, where I had a reason to hate them for how ill intended they are, I never had a valid reason to dislike or hate Google apart from the fact that they steal my data.
That's it. That's my only reason why I hate Google. But I fell in love with their products during my trip to Istanbul and how throughout my journey, Google products were there for me to solve all my needs.
As y'all know, I was treated badly during my Meta interview, last October. With Google, the experience is on another level.
People are fucking smart and ingenious, but at the same time very polite, humble, and respectful.
During my 3 interviews so far (2 more remaining), each one of them made me so comfortable that I was more anxious before the interview than during or after.
They supported me during each question they asked. They made me felt heard and focused on my strength, instead of the weaknesses (or trying to break me down unnecessarily).
The interview syllabus is so fucking vast, and recruiters know so much that they helped me not only with preparation material, but also guided me personally. Haven't seen such knowledgeable recruiters.
The questions were dynamic in nature and thankfully because of my preparation, I was able to answer them most.
Overall, the culture at Google seems brilliant and an environment where one can flourish. No wonder companies are trying to copy every aspect of how Google operates and no surprise that Google is doing well at scale.
I feel so high on emotions (positively), after these interviews that I wonder how would it be to work at Google with such phenomenal people and exceptional environment.7 -
sooooooooo for my current graduate class we were to use the MVC pattern to build an IOS application(they preferred it if we did an IOS application) or if you didn't have an Apple computer: an Android application.
The thing is, they specified to use Java, while in their lectures and demos they made a lot of points for other technologies, hybrid technologies, such as React Cordova, all that shit, they even mentioned React Native and more. But not one single mention of Kotlin. Last time I tried my hand at Android development was way before Kotlin, it was actually my first major development job: Mobile development, for which we used Obj C on the IOS part and well, Java on the Android part.
As some of you might now, I rarely have something bad to say about a tech stack(except for VBA which I despise, but I digress) and I love and use Java at work. But the Android API has always seem unnecessarily complex for my taste, because of that, when I was working as a mobile development I dreaded every single minute in which I had to code for Android, Google had a great way to make people despise Java through their Android API. I am not saying it is shit, I am not saying it is bad, I just-dont-like-it.
Kotlin, proves a superior choice in my humble opinion for Android development, and because the language is for retards, it was fairly easy for me to pick it up in about 2 hours. I was already redesigning some of my largest Spring applications using half the code and implemented about 80% of the application's functionality in less than 3 hours(login, fragment manipulation, permissions, bla bla) and by that time I started to wonder if the app built on Kotlin would be ok. And why not? If they specifically mentioned and demonstrated examples using Swift, then surely Kotlin would be fine no? Between Kotlin and Java it is easy to see that kotlin is more similar to Swift than Java. So I sent an email. Their response: "I am sorry, but we would much rather you stick with the official implementations for Android, which in this case is Java for the development of the application"
I was like 0.o wat? So I replied back sending links and documentation where Google touted Kotlin as the new and preferred way to develop Android applications, not as a second class citizen of the platform, but as THE preferred stack. Same response.
Eventually one of the instructors reflected long enough on it to say that it was fine if I developed the application in Kotlin, but they advised me that since they already had grading criteria for the Java program I had to redo it in Java. It did not took me long really, once I was finished with the Kotlin application I basically rewrote only a couple of things into Java.
The end result? I think that for Android I still greatly prefer Kotlin. Even though I am not the biggest fan of Kotlin for anything else, or as my preferred language in the JVM.
I just.......wish....they would have said something along the lines of: "Nah fam please rewrite that shit for Java since we don't have grading criterias in place for Kotlin, sorry bruh, 10/10 gg tho" instead of them getting into an email battle with me concerning Kotlin being or not being the language to use in Android. It made me feel that they effectively had no clue what they were talking about and as such not really capable of taking care of students on a graduate level program.
Made me feel dirty.12 -
I used to kill some time reading devrant some years ago and I just stopped because most rants were basically whinny little teenagers that think they know everything, keepers of knowledge and truth, being clearly crying babies about “ boo-hooo my coworker is not using the language I like” or something they clearly still have a lot to learn about.
Grow the fuck up. I guarantee you that when you have a few more years of experience you’ll realize how little you knew and how great you thought you were when in reality you knew shit.
Hell, I’m on my 16th year of programming experience and what o thought I knew last year had so many knowledge gaps.
Friendly advise, be more humble. You know shit. Get off your high horse and consider for a second you’re not as smart you think you are.
With that said, there are some really good rants here. But it didn’t change much from years ago.10 -
Sometimes you get too used to everything, that you forget to be humble and curious, to explore and learn new things all the time. I miss the time when I say:oh this shit is cool, I am gonna try it out.
Glad someone knocked this back into me. -
Brush up on your unix skills while supporting charity and O'Reilly media: there's a Unix book humble bundle! Will not be equally interesting for all, but worth a look.
https://humblebundle.com/books/...2 -
People talk about how they would love to switch to Linux, but cannot, as they claim that gaming lives on Windows. This may have been the case ten years ago but it isn't now.
And further, Microsoft is working hard to break steam, humble, gog, and any other delivery systems they do not control. Such anti-consumer behavior should not be tolerated, let alone rewarded. One result of this is that almost every indie game that comes out now has native Linux support within months, if not on day 1.
The only weak spot is AAA games. But as AAA games and mobile games begin to converge, in terms of the subscription/microtransaction models they're both moving toward, with very few exceptions, I personally don't think I'm really missing anything when I see a Windows-only game for $60 with no Linux support.
And if I really want, I can play un-wine-able Windows games through parsec, though that's getting rarer and rarer all the time.11 -
I think my favorite MacBook Pro™ with touch bar feature is when I'm changing the volume while listening to music, and the bar bugs ou- ahem, decides that I actually want to listen at max volume, and proceeds to rape my ears.
If only Tim Cook were here, and would grace my humble existence by allowing me to pleasure him with my mouth. It is moments like these that make me feel truly blessed to be an Apple chosen one.2 -
When you snap at the other Developer because you SWEAR your bug fix push corrected the issue, to then be put back in your place...realizing the other Developer was right...humble yourself4
-
Ok, time to eat some humble pie. I seem to remember ranting about the fact we were going to use an offshore dev house a while back, and I'd convinced myself they were going to be absolutely useless.
Far from it. It's certainly meant I've had something else to do in managing them, and I can't say everything has been completely rosy - but overall, they're a bunch of hard working, decent devs who write good, well-tested code, are receptive to feedback in code reviews and take the initiative and ask questions when they need to. Shame on me for initially thinking otherwise - I'll miss working with them when I leave this place.3 -
K&R Like it or not, everything that we use was impacted by the advantage of having the C Programming language on our side. C is still to this day a cornerstone of what a a language should be, nothing more nothing less.
John McCarthy the creator of Lisp and the one that coined Artificial Intelligence as a topic, a term, without him if else statements would have probably taken a while longer to figure out the way my boy did. Lisp will make you a better developer.
Alan Kay, creator of OOP, yeh we had ways to emulate this with C before, bit without his contribution to what I believe to be the purest form of oop we would not haveany additional things. Smalltalk is still the best programming language in my humble opinion.
Terry A Davis, disciplined, and crazy, the man built a skyscraper by himself, God knows what he would have done if he weren't afflicted by mental illness.
Linus Torvalds, for many different things, creator of the kernel that would power my favorite operating system.
Ryan Dhal, took the world by storm with Node.js -
Inspired by @NoMad. My philosophy is that technology is a means to and ends. We’re a tool oriented species. As it relates to software and hardware, they should be your means to achieve your ends without you needing to think. Think of riding a bicycle or driving a car. You aren’t particularly conscious of them - you just adjust input based on heuristics and reflex - while your doing the activity.
For a long time Software has been horrendously bad at this. There is almost always some setup involved; you need to front-load a plan to get to your ends. Funny enough we’re in the good days now. In the early days of GUI you did have to switch modes to achieve different things until input peripherals got better.
I’ve been using windows from 95 and to this day, though it’s gotten better it’s not trivial to setup an all in one printer and scan a document - just yesterday I had to walk my mother through it and she’s somewhat proficient. Also when things break it’s usually nightmare to fix, which is why fresh installing it periodically is s meme to this day. MS still goes to great lengths with their UI so that most people can still get most of their daily stuff done without a manual.
I started Linux in University when I was offered an intro course on the shell. I’ve been using it professionally ever since. While it’s good at making you feel powerful, it requires intricate knowledge to achieve most things. Things almost never go smoothly no matter how much practice you have, especially if you need to compile tools from source. It also has very little in the ways of safe guards to prevent you from hurting yourself. Sure you might be able to fix it if you press harder but it’s less stress to just fresh install. There is also nothing, NOTHING more frustrating than following documentation to the T and it just doesn’t work! It is my day job to help companies with exactly this. Can’t really give an honest impression of the GUI ux as the distros have varying schools of thoughts with their desktop environments. Even The popular one Ubuntu did weird things for a while. In my humble opinion, *nix is better at powering the internet than being a home computer your grandma can use.
Now after being in the thick of things, priorities change and you really just want to get things done. In 2015 I made the choice to go Mac. It has been one of my more interesting experiences. Honestly, I wish more distros would adopt its philosophy. Elementary only adopted the dock. It’s just so intuitive. How do you install an application? You tap the installer, a box will pop up then you drag the icon to the application folder (in the same box) boom you are done. No setup wizards. How to uninstall? Drag icon from app folder to trash can. Boom done. How to open your app? Tap launch pad and you see all your apps alphabetically just click the one you want. You can keep your frequent ones on the dock. Settings is just another app in launchpad and everything is well labeled. You can even use your printers scanner without digging through menus. You might have issues with finder if your used to windows though and the approach to maximizing and minimizing windows will also get you for a while.
When my Galaxy 4 died I gave iPhone a chance with the SE. I can tell you that for most use cases, there is no discernible difference between iOS and modern android outside of a few fringe features. What struck me though was the power of an ecosystem. My Mac and iPhone just work well together. If they are on the same network they just sync in the background - you need to opt in. My internet went down, my iMac saw that my iPhone had 4g and gave me the option to connect. One click your up. Similar process with s droid would be multi step. You have airdrop which just allows you to send files to another Apple device near you with a tap without you even caring what mechanism it’s using. After google bricked my onHub router I opted to get Apples airport series. They are mostly interchangeable and your Mac and iOS device have a native way to configure it without you needing to mess with connecting to it yourself and blah. Setup WiFi on one device, all your other Apple devices have it. Lots of other cool stuff happen as you add more Apple devices. My wife now as a MacBook, an IPad s d the IPhone 8. She’s been windows android her life but the transition has been sublime. With family sharing any software purchase works for all of us, and not just apples stuff like iCloud and music, everything.
Hate Apple all you want but they get the core tenet that technology should just work without you thinking. That’s why they are the most valued company in the world14 -
(I guess the Question category is the best for this)
Do you believe that someone can be a good dev even if they write shit code?
I personally do, if that person acknowledges the fact that their code is shit, wants to improve it, is humble, is always in the search for constructive, etc as in to make their code better and more readable, I'd think they are a pretty good dev.2 -
Programmer OAth. Just read on a github repo
0. I will only undertake honest and moral work. I will stand firm against any requirement that exploits or harms people.
1. I will respect the learnings of those programmers who came before me, and share my learnings with those to come.
2. I will remember that programming is art as well as science, and that warmth, empathy and understanding may outweigh a clever algorithm or technical argument.
3. I will not be ashamed to say "I don't know", and I will ask for help when I am stuck.
4. I will respect the privacy of my users, for their information is not disclosed to me that the world may know.
5. I will tread most carefully in matters of life or death. I will be humble and recognize that I will make mistakes.
6. I will remember that I do not write code for computers, but for people.
7. I will consider the possible consequences of my code and actions. I will respect the difficulties of both social and technical problems.
8. I will be diligent and take pride in my work.
9. I will recognize that I can and will be wrong. I will keep an open mind, and listen to others carefully and with respect.4 -
Don't know if I am experienced enough to give any advices but still:
1. Whenever doing freelance work, always take some advance payments, even its for your friends.
2. Use git even if you think it doesn't apply to you. I started really late.
3. Contribute to open source. You grow when the community grows.
4. Be humble even if you are the best there is!
5. Whenever you feel you are tired of this shit, remember why you started. Don't give up!
Most importantly, take time for yourself, family and friends. It won't be lines of code that you remember on your death bed!1 -
In my previous company we developed a CRM web app for the company to use internally and it was in my humble opinion really easy to make sense of, but for some freaking we kept getting calls whenever someone got an error, and our default response was always to send us an email, then we will get back to you, as it was mostly stupid things they called about, for example, a customer might have to be status terminated, before you can click button A, button A would then be disabled and employees would call asking why. Apparently, people got annoyed by our response and went to the management, to get some guidelines as to when they could call the "development apartment" for help, so the management sends out some guidelines as to when they could call, write or whatever... The following was done without consulting us in any way ANY WAY AT ALL!... Because we all know management knows fucking best, and why bother asking the people that sit with it every day, and the way it was done was by saying:
If the background color on your error is red, it means the error is fatal and you can call the developers immediately, if its orange send an email and they will answer within 48 hours LIKE WTF... Seriously???. That was basically it, and honestly we had just been using colors, without much thought to it ofc red, was an error etc. But they we're not "OMG EVERYTHING IS BREAKING" alert, so we decided to use a couple of hours refactoring the color of the flash errors, and after that, we did not have many red alerts(None, yes none what so ever) We changed all the red ones to orange, and introduced some new colors. That worked for some time around 6 months or so, but then people obviously started calling again like, why even bother... So we created a simple service desk, blocked all incoming calls to our phones that were from regular employees, heard a lot of complaints about this from the employees, management was mad, we had so many meetings with those top paid management fuckers that know everything (way better than you and me), about how to handle this. As it took way too much of our time, that people couldn't bother trying simple things, or make some sense as to why a button is disabled etc. We ended up "winning", was allowed to block calls for some time, till the employees had learned to use a freaking simple service desk, it's not fucking rocket science Okay, stop being a pain in the ass... And it actually fucking worked! Most relaxing time after people got a hang of using the service desk instead of calling life was good after that... <3 -
I just can't stress enough how fascinated I am by biology and biochemistry.
I mean, we, who call ourselves engineers, are no more but a gang of toddlers having a blast with jumbo legos on Aunt Lucy's dining room carpet on a sunny Sunday afternoon. Our solutions using "modern tools" and "modern engineering" are mere attempts to *very* remotely mimic what beautiful and elegant solutions are around us and inside of each of us.
IC/EC engines, solar batteries, computers and quantum computers, spaceships and ISSes, AI/ML, ... What are they? just the means to leverage what's been created all around us to create something that either entertains us, encourages our laziness or helps us to look at the other absolutely fascinating engineering solutions surrounding us so we could try and "replicate" their working principles to further embrace our laziness and entertain us.
Just look at the humble muscle - a myofibril made out of actin and myosin. The design is soooo simple and spot on, so elegant and efficient, the "battery" and signalling system are so universal and efficient.
Look at all those engineering miracles, small and big. Look how they work, how they leverage both big and small to create holistic, simplistic and absolutely efficient mechanisms. And then come back to me, and tell me again that all these brilliant solutions came out of nothing just by an accident we call "evolution".
How blinded by our narcissism are we to claim that there can't be a grand designer of any kind, that there's nothing smarter than us and that the next best thing than us is an incomprehensible series of accidental mutations over an unimaginable amount of time?
I mean.. could it be that someone/something greater than us created us and everything around us? naaaah.. we are the crown jewel of this universe. Everything else must be either magic or an accident. /s
Don't read this as yet another crazy-about-God person's ramblings. I'm not into religion fwiw. But science has taught me enough critical thinking to question its merit. Look at it all as engineers. Which is more probable: that everything around us happened by an accident or that someone/something preceding us had a say in the design?random biology humanity think about it biochemistry creation big and small shower thoughts narcissism had to be said naive evolution20 -
C'mon, really?
Okay, I understand that they want to lock down the Chromebooks they send home with us, we don't own them and they have the right to do that. But I'm still annoyed when I find "harmless" stuff is blocked.
They said it themselves that they want us to be able to do basically anything we want web browsing wise on them.
It's not a fun experience to say to your self "hey let's look at the current humble bundles!" just to find that humblebundle.com is blocked for "games". (Which makes sense, but I can't remember any other examples)
Imagine thinking to yourself "I'm going to go to the Os Dev Wiki" and typing that into the Omnibox (tm) and pressing enter, directing you to your favorite search engine duckduckgo, but instead of finding the amazing duckduckgo results page you find the godforsaken securly "THIS PAGE IS BLOCKED" screen.
I can guess why they do that (probably because, to my knowledge, duckduckgo doesn't have any form of "safe-search" feature they can force it to use because they do that) but it's kind of annoying to not be able to use your favorite search engine anymore.
Should I really be getting so annoyed at this? No, because it's not my device, it's theirs and, they have the final say on what goes, but sometimes it really annoys me. I should be, and am, thankful they even let us bring the Chromebooks home, which is pretty cool.
Ugh...
If you want a fun time, just read the reviews on the Securly extension in the chrome web store!6 -
Observation rather than a rant.
Some of the best, most experienced devs I've ever had the pleasure of meeting and working with have invariably all been the most humble and least opinionated. Mention (x language that might commonly draw disdain) and you don't hear boos and hisses and jokes being thrown around, you hear considered, succinct observations about how, if they were to work with this language, there'd be various coding styles and rules that they'd suggest working to in order to avoid some common pitfalls and frustrations.
Mention a language or framework that they know little about, or heck, they know quite a *lot* about but in which they wouldn't consider themselves an expert, and they're the first to suggest drafting in help. They're more than happy to listen to bring themselves up to speed, even if that "outside help" comes from someone considerably younger and less experienced than them.
This has particularly come to mind as of late as I've found myself working with both ends of the spectrum, but it's been my experience for many years now. Have many others had the same experience?2 -
I want to say I would not have been the programmer I am now, if it hadn't been for all of my mentors in my past and current job who took a chance on me.
I am socially awkward, am nervous and stutter around new people, cannot sustain conversation, and as a consequence come out rather poorly in most kinds of interviews.
But there has been 3 mentors/leads in my life so far who saw through the nervous wreck I was in the few hours of the interview and took, what felt like to me, a gamble by hiring me. My current mentor even taught me everything I know on my job and has vastly shaped the programmer I am.
A humble thank you to all the amazing mentors out there, who inspire and enable the now green engineers, who will later be the mentors of the future generation!1 -
I usually crib about how stupid people are and how I struggle to stay afloat.
Let's switch some gears now. A post about some good people, product, and processes.
You know what the common theme here is?
The goodness here cannot be measured. Your first interaction with them makes you feel so comfortable that you start feeling butterflies.
These people just keep on giving. They are selfless. They are pure. They actually care.
And when you think it's done, then they give you some more.
What blows me away is, they don't expect or accept anything in return. Absolutely nothing. Not even a simple thank you.
And they are like a wizard. They walk into your life when you least expect them but need them the most. And when the task is done, they'll be gone before you even know.
No lingering, no drama, no bullshit. Just pure goodness.
Like my ex-lead in current company, I have a very senior guy in neighbouring team (for which they were gonna hire me initially), who also happened to interview me, is a gem.
He takes care of me like his own younger brother. Supports me and always answers my queries no matter how occupied he is.
And same is with good products and processes. They feel effortless. So smooth and add exceptional value to your existence. They give rise to wonderful companies.
You'd never experience a single negative aspect about them. No matter how much you try, things will just keep getting better until they don't need to.
And then they'll be long gone. Never to be seen again and never to be forgotten.
You cherish them only in your memory and wish they lasted longer. But they didn't because the purpose was served.
Such people and experiences inspire me. They push me to become a better human.
No matter how the world is or how it treats me, I must always live with high values and be a better version of past self.
The other evening, I was conversing with my mother where we spoke about some family friends who are insanely wealthy but humble and kind.
Mom and I mutually agreed that they don't have such good traits because they are wealthy, but they are wealthy because they live with humility, kindness, and pure intentions.
World is surely a beautiful place because of such people and I aspire to be one. May lord guide me well :)3 -
When java was facing extinction, during the JavaScript, Node, and reactive programming hype. It did what it had always done. just adapt to the hype and maintain backward compatibility. We can all learn a thing or two from the humble java. It never rushes, it's patient. Be calm and wait before you hype yourself.2
-
Oh,I have learned a lot, I would not say from programming but from the career as a whole
Never get peer pressured
Always show empathy
If in a leading position, taking care of people is your top priority
Overconfidence will destroy a lot of good work
People by definition will always remember your mistakes
Never get over involved in the company you are working for, it's just a job
Your health is more than important
Nobody knows everything
Always be humble
There is a lot of bullshitters out there
Success is relative
Competition is high and there is always someone with better skill set, so you will suffer if you don't accept that -
A peeve of mine is when someone in the software industry denigrates a technology/tool/framework outside of his role eg webdevs on sysadmin stuff or viceversa.
I'm not trying to shame anyone for having subjective experiences, I just think that if you're gonna talk about tools that are not on your domain, then you need to be twice as humble as usual.
I'm a webdev and I don't post around how I KNOW how to make ssh secure, while other people devote their entire careers to that and all related matters.
What prompted me is seeing some not webdevs do this here that seem to be sysadmins/devops (can't tell for sure since I don't know them), but in real life, I've seen people from any role do this, webdevs too, even testers!
Imagine you had cancer, and you had a tumor extraction, and the oncologist said to the surgeon "step aside son, let me show you how to deal with cancer".5 -
I am a good person. I can even say I am a good programmer. I have worked hard to get where I am and that shows perseverance. Although, where I am right now is not what I expected, I am somewhere. I can do something. I have good intentions.
Someday, I will build software which will be used by millions of people around the interwebs. And they will love me, for I will have made their lives better....in some way. Some will even consider paying me for it. Not because the well placed and non intrusive donate button I put there, but out of pure adoration and bare necessity to preserve someone as brilliant and precious as me. I shall be the definition of success. But I long for neither adoration nor wealth, for I am humble or at least that is how I will be perceived.
Like flies to the honey my success will attract big evil corporations to acquire my business. And I shall spit on their wretched face....at first. I would like to be wooed. Such display of integrity shall inspire generations of programmers. Let ye be inspired. There will be those who envy my achievements and they will be mocked and shunned by my true believers. But being the kind soul that I am, I will bring back my minions, for it could a PR nightmare.
All these events will take place in a not too distant future. Sure, I am going through a dark time now, it will pass. 'tis nothing but me transitioning from a lame ass PHP coder moth to this totally badass software engineer who is also a cool bro. This eclipse of my brain shall pass. My neurons will fire in all directions like photons from the sun during late winter, for it may overheat and we definitely don't want that.
I pray to the gods of engineering to grant my wishes. Trust me guys, you will be thanking yourselves when donate my money to charities that will help me set up. But that's another scheme. Amen.4 -
i am at the point of deep depression again as a CS student. a few weeks back and forward is a busy weeks with a lot of team projects/research. as always, team project never be as smooth as i expect, I always who be the one who work in the project with the rest of the team and they doesn't even care what the project does.
also a few week forward there will be a Leadership Training, and i just quit from it, why ? because i need sleep. why again ? BECAUSE I AM THE *ONLY* ONE WHO WORK ON THE PROJECT YOU FUCKING DIPSHIT, i am the one who can't sleep everyday working on the project scraping the deadline and class hour.
why i drop important thing (Leadership Training) just to keep me from depriving my sleep and to keep the project up while the team disregard me? am i being too humble yet i just rant about "don't be too humble".
..i...i just... I just can't take it anymore. :( god help me15 -
Really loving all these Udemy sales and humble book bundles, a lot of is for programming and some of them are actually really good!
It's a good time to be a Dev! -
Here comes lots of random pieces of advice...
Ain't no shortcuts.
Be prepared, becoming a good programmer (there are lots of shitty programmers, not so many good ones) takes lots of pain, frustration, and failure. It's going to suck for awhile. There will be false starts. At some point you will question whether you are cut out for it or not. Embrace the struggle -- if you aren't failing, you aren't learning.
Remember that in 2021 being a programmer is just as much (maybe even moreso) about picking up new things on the fly as it is about your crystalized knowledge. I don't want someone who has all the core features of some language memorized, I want someone who can learn new things quickly. Everything is open book all the time. I have to look up pretty basic stuff all the time, it's just that it takes me like twelve seconds to look it up and digest it.
Build, build, build, build, build. At least while you are learning, you should always be working on a project. Don't worry about how big the project is, small is fine.
Remember that programming is a tool, not the end goal in and of itself. Nobody gives a shit how good a carpenter is at using some specialized saw, they care about what the carpenter can build with that specialized saw.
Plan your build. This is a VERY important part of the process that newer devs/programmers like to skip. You are always free to change the plan, but you should have a plan going on. Don't store your plan in your head. If you plan exists only in your head you are doing it wrong. Write that shit down! If you create a solid development process, the cognitive overhead for any project goes way down.
Don't fall into the trap of comparing yourself to others, especially to the experts you are learning from. They are good because they have done the thing that you are struggling with at least a thousand times.
Don't fall into the trap of comparing yourself today to yourself yesterday. This will make it seem like you haven't learned anything and aren't on the move. Compare yourself to yourself last week, last month, last year.
Have experienced programmers review your code. Don't be afraid to ask, most of us really really enjoy this (if it makes you feel any better about the "inconvenience", it will take a mid-level waaaaay less time to review your code that it took for you to write it, and a senior dev even less time than that). You will hate it, it will suck having someone seem like they are just ripping your code apart, but it will make you so much better so much faster than just relying on your own internal knowledge.
When you start to be able to put the pieces together, stay humble. I've seen countless devs with a year of experience start to get a big head and talk like they know shit. Don't keep your mouth closed, but as a newer dev if you are talking noise instead of asking questions there is no way I will think you are ready to have the Jr./Associate/Whatever removed from your title.
Don't ever. Ever. Ever. Criticize someone else's preferred tools. Tooling is so far down the list of what makes a good programmer. This is another thing newer devs have a tendency to do, thinking that their tool chain is the only way to do it. Definitely recommend to people alternatives to check out. A senior dev using Notepad++, a terminal window, and a compiler from 1977 is probably better than you are with the newest shiniest IDE.
Don't be a dick about terminology/vocabulary. Different words mean different things to different people in different organizations. If what you call GNU/Linux somebody else just calls Linux, let it go man! You understand what they mean, and if you don't it's your job to figure out what they mean, not tell them the right way to say it.
One analogy I like to make is that becoming a programmer is a lot like becoming a chef. You don't become a chef by following recipes (i.e. just following tutorials and walk-throughs). You become a chef by learning about different ingredients, learning about different cooking techniques, learning about different styles of cuisine, and (this is the important part), learning how to put together ingredients, techniques, and cuisines in ways that no one has ever showed you about before. -
many many times in the past I had this impostor syndrome in various situations but I never lost faith in my dev skills!
you have to be humble to realise that this situations are fine and that you will learn something from it (not necessarily tech things, but also how life works). Also you have to realise that development as everything else in life is just never ending learning endeavour! When you accept all of that, impostor syndrome goes away forever.
It's been around 3 years since I felt like impostor for the last time because I accepted who I am as a person.
It crawled up on me last week in a different way - I was thinking of myself - what if I am just really good at googling things and understanding how those things work but I am also very capable problem solver so I can understand the principle and apply it to my code.
Then I realised - ok, that's what programmers do! So that's the story of how the impostor syndrome actually become confirmation syndrome!
Folks, believe in yourself, be forgiving to yourself as we all were there, give yourself some time as people don't become good developers overnight - and this is OK.3 -
Right,i consider myself a pretty damn good dev... I can back up everything I say to prove that I'm right on not lying to clients
But I see all these devs who do lie... Who withold data from clients cause it's not great.
And I go to clients and prove that they are lying not doing it right.
But I know saying to them... Oi your current devs are shit fire them ... Isn't a good way to get them as a client
Me and my company are open and honest ... we go all out on all of our projects. I work nonstop. It is seriously baffling the kind of developers are out there and how bad they can be I'm... Seriously just.... Urgh 😖
How should I go about talking to clients without going ... Fire them quick or saying that in a ... More humble respectful way...
I need more clients ... To survive and I don't mind coming across as a dick as long as they understand what's going on and that they are people ripped off by these asshole devs5 -
I'm typically very humble about my work. There's a certain project that I enjoy a lot. It is challenging to me, which is something important to me. I learn a lot.
Colleagues do not enjoy the project in the way that I do. In fact, most of them don't like it or try to avoid when they can. When they can't, they often consult with me about the project. I have a genuine curiosity and interest in it.
However, there is one aspect of it that I don't like at all, but I deal with it. It comes with the territory, I guess. What IS discouraging and turns me away from it though, is when colleagues "get the better end of the deal" when it comes to making special arrangements for this project. Sure, make me dedicated to it for a period of time so that I stay focused on the topic, but yet, kind of do the same for another team member but reward the other person with not having to also deal with the particular task I don't enjoy. Give them the pieces I enjoy and stick me on the pieces I don't.
I know this is a very general post and it probably makes no sense, but I needed to let off some steam and still keep it somewhat anonymous. I work hard for this project and I often don't take credit when it's given to me / when I should be taking it. It's just discouraging how things are arranged sometimes.2 -
This story just left me speechless in any way and i want to share it. tl;dr at the end.
Im studying computer science in germany and in the first of the small classes i noticed... no, i was disturbed by a guy who would just say that the thing we're learning atm were so easy and the teacher shouldn't even bother to explain it to the class. I don't understand why you would spoile a class that hard... I'm here to learn and listen to the teacher, not to you little asshole. (We were doing basic stuff like binary system etc. but still, let us learn)
So he became unpopular pretty fast.
Fast forward, a few weeks of studying later there was a coding competition where you had to solve different algorithmic problems in a team as fast as possible.
I came there, without a team because my friends aren't interested but I enjoy such tournaments. This guy and me were the only ones without a team and we had to work together.
After him being a total dick for hours i had to watch him code a simple for-loop, that iterates through a sorted array. Nothing special, at this point anyone could do that task in our class so it shouldn't be a problem for him.
He made a simple for-loop and it worked fine, but we figured we had to iterate through the array the other way around.
'Alright', I think. 'Just let the index decr..' 'Pssshhh', he interrupted me and said he knows exactly how to do this.
I was quite impressed when he started to type in 'public int backsort..' in a new line. He tried to resort the array backwards with a quicksort that he then struggled to implement. (Of course we had to implement a quick runtime and we needed that quicksort badly)
I was kind of annoyed but impressed at the same time. I mumbled 'Java has an internal sorting algorithm already' just to amuse myself.
He then used that implementation.
After a few minutes of my pleasure and multiple tests without hitting the requested runtime, i tried to explain to him why we wouldn't need to sort that array backwards and he just couldn't believe it.
I hope that he stays more humble after that..
Also we became last place but thats ok :)
tl;dr: Guy spoiles whole class, brags with his untouchable knowledge (when we do things like binary system). In a competition has to iterate through a sorted array backwards - tries to implement a sorting algorithm to sort it backwards first. I tell him, we could use a already implemented java method. Then tell him we could simply iterate through decreasing the index. Mind-Blown2 -
Not a DRV rant bit I am Maaad AF here
I am doing an internship at an amazing company. Everything is going well and I have learned a lot. This internship is for 6 months and almost 4 months are remaining. Now this shitfuckery of obscene ignorance that I call my college , wants every student to attend classes no matter what. I have already told them the status of my internship but they said "college is more important ". Along with this they want 2 projects in this semester and my HOD said we have to give developments of our project weekly
When I told this amazing piece of human knowledge that I won't get off for every week and I will be using git , he can see my developments and we can communicate on slack etc.
This humble genius said with utmost compassion " what is got, I don't use it , come daily to college". Man, first time in my life I have ever given that Michael Corleone stare at sollozzo killing death stare.
Indian colleges are messed up.1 -
Joined a new startup as a remote dev, feeling a bit micromanaged. So this week I joined an established startup as a senior mobile dev where I work remotely.
Previous two devs got fired and two new guys got hired (me as a senior dev and another senior dev as a teamlead, also third senior dev will join next week).
Situation is that codebase is really crappy (they invested 4 years developing the android app which hasn't even been released yet). It seems that previous devs were piggybacking on old architecture and didn't bother to update anything, looking at their GIT output I could tell that they were working at 20-30% capacity and just accepting each other MR's usually with no comments meaning no actual code reviews. So codebase already is outdated and has lots of technical debt. Anyways, I like the challenges so a crappy codebase is not really a problem.
Problem is that management seems to be shitting bricks now and because they got burned by devs who treated this as a freelance gig (Im talking taking 8-10 weeks pto in a given year, lots of questionable sick leaves and skipping half of the meetings) now after management fired them it seems that they are changing their strategy into micro managament and want to roll this app out into production in the next 3 months or so lol. I started seeing redflags, for example:
1. Saw VP's slack announcement where he is urging devs to push code everyday. I'm a senior dev and I push code only when I'm ready and I have at least a proof of concept that's working. Not a big fan of pushing draft work daily that is in in progress and have to deal with nitpicky comments on stuff that is not ready yet. This was never a problem in 4-5 other jobs I worked in over the years.
2. Senior dev who's assigned as the teamlead on my team has been working for 1 month and I can already see that he hates the codebase, doesn't plan on coding too much himself and seems like he plans on just sitting in meetings and micromanaging me and other dev who will join soon. For example everyday he is asking me on how I am doing and I have to report this to him + in a separate daily meeting with him and product. Feels weird.
3. Same senior dev/teamlead had a child born yesterday. While his wife was in hospital the guy rushed home to join all work meetings and to work on the project. Even today he seems to be working. That screams to me like a major redflag, how will he be able to balance his teamlead position and his family life? Why management didn't tell him to just take a few days off? He told me himself he is a senior dev who helped other devs out, but never was in an actual lead position. I'm starting to doubt if he will be able to handle this properly and set proper boundaries so that management wouldn't impact mental health.
Right now this is only my 1st week. They didn't even have a proper backend documentation. Not a problem. I installed their iOS app which is released and intercepted the traffic so I know how backend works so I can implement it in android app now.
My point is that I'm not a child who needs hand holding. I already took on 2 tickets and gonna push an MR with fixes. This is my first week guys. In more corporate companies people sit 2 months just reading documentation and are not expected to be useful for first few months. All I want is for management to fuckoff and let me do my thing. I already join daily standup, respond to my teamlead daily and I ping people if I need something. I take on responsibility and I deliver.
How to handle this situation? I think maybe I came off as too humble in the interview or something, but basically I feel like I'm being treated like a junior or something. I think I need to deliver a few times and establish some firm boundaries here.
In all workplaces where I worked I was trusted and given freedom. I feel like if they continue treating me like a junior/mid workhorse who needs to be micromanaged I will just start interviewing for other places soon.5 -
got my left bicep bone fractured from srm wrestling. dude just took my hand and half bicep bone away with him. what a happy new year 2024.
and just few hours ago, i was having death thoughts just because my parents were not allowing me to take car to work on a foggy morning.
karma can hit anytime. be humble.3 -
After years of working at a place where you are as good it gets in terms of domain knowledge, it can be refreshing to work with someone who has way more experience than you.
The previous company I was with wanted to have me as one of their primary engineers, and everyone else who came in would have to learn from me (most of them were low-skilled contractors). This should have been great in theory, but it was actually quite frustrating since I did not relish being the mentor figure while just being two years into my career. Despite it getting to my head at times, I was aware that I still lack a lot of skills, but with no one to teach me, I hardly progressed in terms of growth, even though the leadership treated me well and listened to me.
Took a leap of faith and quit, to join a start-up where I would be the most inexperienced (and the youngest) person. Has been a few months, and I have stumbled and goofed up more times than I like to admit, but taken with the right mindset, it is nice to see how a team of professionals goes about it. It is a learning curve to get back into the mindset of the novice (after more than a year of being the undisputed "go-to" person), and to make effort knowing that you'll fall short in multiple places by the standards here, but at the same time, it's nowhere like the frustration I felt previously when my head was pushing against the shallow ceiling.
Fun part is, the learning is almost not at all about the code, but about how to be a proactive team member and all the things to think through and finalize BEFORE getting down to code. Some of it is bureaucracy, yes, but given the chaotic place I come from, I don't really mind it as long as it only goes as far as what is required.
The most amusing part of it all to me is how I try to be humble and listen to people (everyone's got a lot more experience than me), but I'm often asked to be critical of what others say and poke holes instead of just taking what they say at face value, which has been one of the most challenging things to adapt to for me (for similar organisation cultural reasons mentioned previously)/1 -
I love devrant so much for how I feel it's the one social network in which I feel part of the community, and I hate it for letting me realize how alive all of the stereotypical behaviours the IT crowd is usually shunned for are amongst us.
Users and managers aren't stupid, processes in a company are usually there for a reason, and if your boss is really that much of a dimwit, then why the hell are you even there?
This has to be one of the most recession proof professions out there. Change jobs. Stop blaming everybody else for your shortcomings, damn it.
But, yeah, much love to all of you making us look good and being humble about it.10 -
>Be me, humble physicist turned quantitative developer
>Big physics nerd, but code for the cash
>Working on some quantitative finance software, all about risk measures
>Girl comes over one day, cute as a quark
>Think to myself, "This is it, time to make a move"
>Instead, brain decides it's time to explain my work
>Start rambling about refactoring, polymorphism, and data encapsulation
>She's looking at me like I've started speaking in binary
>She tries to steer the conversation back to normal stuff, but I'm stuck in a recursion loop
>Keep going on about my project, can't seem to stop myself
>She tries to stay longer, even tries to show interest in my work
>But the more I talk about algorithms and time complexity, the more her eyes glaze over
>Eventually, she gives up, says she has to leave
>She leaves, probably thinks I'm more interested in my code than her
>mfw I realize I've chosen code over companionship
>Why am I like this?10 -
Been thinking about this a lot and I'd love your thoughts. Recently a friend was starting in dev. They asked me for some advice. I just said "be humble and hungry". I've built my career on that phrase. Be willing to listen and willing to put in the work.
What is your best advice for the young devs out there?4 -
The senior iOS dev I was working with in my first job after uni - he showed me so many objc tricks and his self-written libraries to make working with UI stuff in swift more concise, it blew my mind. At the same time, he was very humble and calm, and had a funny humor at times. Also his code and the architecture in an older app we needed to work on was super easy to read and understand. That's why I want to be more like him - and eventually grow a beard :-)2
-
@notRant
The devRant team seem quite humble. I feel it's quite important to have a humble face to your user base, because without it, our jobs as devs would be meaningless, even if you develop a cool app like {{ $coolApps[0] }}.
@include('funny_meme.jpg')
@endNotRant -
Tired of seeing people showing off their bootcamp certification on LinkedIn as if they had just climbed Mount Everest, and as if they were about to enter the most glamorous field of work one could imagine.
OK I went through a bootcamp myself but I certainly knew I was still a baby upon completion of the journey and still consider I have a veeery long way to go today after two years of dev work experience. Also I knew working as a developer probably wouldn’t be as awesome as these bootcamps make it out to be. In fact it’s everything but glamorous when you take into account the stress, the dynamics with coworkers, POs, PMs, shitty management, wacky clients, weird demands, deadlines etc.
Don’t get me wrong. I enjoy being a developer and have more or less been able handle the workload and expectations. But for goodness sake stop drilling into bootcampers’ heads that it’s gonna be amazing and that they’re doing incredible things. Congratulate them for their hard work and then wish them good luck because they’re going to need it. Bootcampers, stay humble. Be prepared for the worst while hoping for the best3 -
I can't help it sounding bitter..
If you work some amount of time in tech it's unavoidable that you automatically pick up skills that help you to deal with a lot of shit. Some stuff you pick up is useful beyond those problems that shouldn't even exist in the first place but lots of things you pick up over time are about fixing or at least somehow dealing or enduring stuff that shouldn't be like that in the first place.
Fine. Let's be honest, it's just reality that this is quite helpful.
But why are there, especially in the frontend, so many devs, that confuse this with progress or actual advancement in their craft. It's not. It's something that's probably useful but you get that for free once you manage to somehow get into the industry. Those skills accumulate over time, no matter what, as long as you manage to somehow constantly keep a job.
But improving in the craft you chose isn't about somehow being able to deal with things despite everything. That's fine but I feel like the huge costs of keeping things going despite some all the atrocities that arose form not even considering there could be anything to improve on as soon as your code runs. If you receive critic in a code review, the first thing coming back is some lame excuse or even a counter attack, when you just should say thank you and if you don't agree at all, maybe you need to invest more time to understand and if there's some critic that's actually not useful or base don wrong assumptions, still keep in mind it's coming from somebody that invested time to read your code gather some thoughts about it and write them down for you review. So be aware of the investment behind every review of your code.
Especially for the frontend getting something to run is a incredibly low bar and not at all where you can tell yourself you did code.
Some hard truth from frontend developer to frontend developer:
Everybody with two months of experience is able to build mostly anything expected on the job. No matter if junior or senior.
So why aren't you looking for ways to find where your code is isn't as good as it could be.
Whatever money you earn on top of your junior colleagues should make you feel obligated to understand that you need to invest time and the necessary humbleness and awareness of your own weaknesses or knowledge gaps.
Looking at code, that compiles, runs and even provides the complete functionality of the user story and still feeling the needs do be stuff you don't know how to do it at the moment.
I feel like we've gotten to a point, where there are so few skilled developer, that have worked at a place that told them certain things matter a lot Whatever makes a Senior a Senior is to a big part about the questions you ask yourself about the code you wrote if if's running without any problems at all.
It's quite easy to implement whatever functionality for everybody across all experience levels but one of your most important responsibilities. Wherever you are considered/payed above junior level, the work that makes you a senior is about learning where you have been wrong looking back at your code matters (like everything).
Sorry but I just didn't finde a way to write this down in a more positive and optimistic manner.
And while it might be easy to think I'm just enjoying to attack (former) colleaues thing that makes me sad the most is that this is not only about us, it's also about the countless juniors, that struggle to get a food in the door.
To me it's not about talent nor do I believe that people wouldn't be able to change.
Sometimes I'm incredibly disappointed in many frontend colleagues. It's not about your skill or anything. It's a matter of having the right attitude.
It's about Looking for things you need to work in (in your code). And investing time while always staying humble enough to learn and iterate on things. It's about looking at you
Ar code and looking for things you didn't solve properly.
Never forget, whenever there's a job listing that's fording those crazy amount of work experience in years, or somebody giving up after repeatedly getting rejected it might also be on the code you write and the attitude that 's keeping you looking for things that show how awesome you are instead of investing work into understanding where you lack certain skills, invest into getting to know about the things you currently don't know yet.
If you, like me, work in a European country and gathered some years of industry experience in your CV you will be payed a good amount of money compared to many hard working professions in other industries. And don't forget, you're also getting payed significantly more than the colleagues that just started at their first job.
No reason to feel guilty but maybe you should feel like forcing yourself to look for whatever aspect of your work is the weakest.
There's so many colleagues, especially in the frontend that just suck while they could be better just by gaining awareness that there code isn't perfect.6 -
Day 2 of my new job done. Still going over courses and doing jack shit. Today the hiring manager told me to play a game. I have to buy gifts to the girl thats in my office (lol what) and she also has to buy gifts to me in return (wtf and im still getting paid to do nothing), the company will pay for these gifts with a limited budget
Both of us had to fill out a form such as hobbies movies food drinks and if we believe in santa claus
Told this to my hot blonde gf that i have to buy gifts for another girl and she got so jealous. She literally asked me "but what do u need her for" lmao
As she should. Love seeing her jealous and mad -- but only because she disrespected me several times in the year 2023. several times caught her lying to me. Rude behavior from time to time. Always bitching and complaining with the most idiotic phrases and I'll quote "i hate how some kids younger than me are just born in a wealthy multi millionaire billionaire family and they're automatically rich and successful and dont have to do anything in life anymore while i have to struggle and work and never be successful like they are. Im so jealous of them" she keeps complaining about this majority of the time. I got really fucking annoyed. Shes stupid as fuck
And then compared to listening to that dumb shit, i met this girl, who works in the backend part, smart, beautiful, doesnt fucking bitch and complain about such obnoxious bullshit we cant control, works a 9-5 and gets her shit together. She even told me today "u dont have to buy me any of those gifts I'd be really grateful if you can just buy me some tissues for my nose cause i got a small flu haha" she even got the jokes! that was such a humble request.
Now compare that to the behavior of my spoiled blonde gf. Tf?
Im not even complaining by working a 9-5. Im actually very surprised. Everyone in the company is very nice to me and polite. Everyone is very friendly. Im getting paid even by not working shit, just sitting and watching courses to pass a devops cloud certification that the company will also pay for me
Whats going on6 -
Spent most of this week busting my ass working on a hotfix that came out of nowhere with mega high priority. This annoys me greatly because the hotfix wasn't even fixing a bug, it was adding new functionality because certain customers were being blocked from testing without this specific feature. In my humble opinion, given that we release every weekend, hotfixes should be reserved for actual critical bugs. But anyway, as I probably could have predicted, the code got to QA and exploded. Literally nothing works.
This is what happens when you try to rush out features to satisfy customers. If you try to rush something that is late, you WILL make it later.
Meanwhile there's an issue I'm supposed to be fixing for our next release which goes out this weekend and I've had no time to even look because of this hotfix. And now it's the end of the day and I just feel worn out from stress, tomorrow will no doubt be similar.1 -
Mom and dad randomly came home and bought me a brand new 15 pro max as a gift for starting my first devops job on 15th december... I didnt ask for this. Nor do i urgently need it. I wanted to buy it myself when i earn money. But i cant be ungrateful so ill be humble and appreciate this gift. I feel bad for them, they are broke and are now paying off this phone for 2 years every month. additional unnecessary stress of money shit on top of their back and i dont like that. Need to give them back as soon as i earn from this shit job and also buy my mom the same phone for her bday thats in 3 months5
-
I'm learning Rust as a case study for my own programming language. It's funny how many approaches exist to the humble loop.
- In classic procedural languages, a loop's job is to repeat actions, and as such it provides a multitude of tools to control this repetition.
- In all languages with iterators, a for-in loop is a construct that does something with every element of a collection. In languages with both iterators and generator functions, this can even be used to define a sequence in terms of another.
- In Rust, a loop is an expression that obtains its value through repeated execution. It can also be used like a classic loop, of course, but this is the interesting part.
- My little language is a functional language, so "loop" is the Y combinator. To loop means to define the value of an expression in terms of itself. It's the only looping construct, gets special treatment from the type checker and it's also used in recursive type definitions. -
Full time internship started, and I'm a week through. It's my first time in the industry and it's awesome!
Going a bit slow right now but I'm looking forwards to the future.
I didn't expect this, but the hardest thing so far has been getting used to the existing codebase.
Also, for anyone going into the industry, be humble about what you don't know. Ask lots of questions.2 -
It just hit me. If you wanna achieve something great you have to dream big. If you aim for something humble, you'll just get lost in the endless land of diminishing returns where you take forever to make little progress
If you aim high, you are naturally inclined to do big strides since you feel that there is still so much left to be done
Just a thought I had working on my engine2 -
New office stories during the emotional turmoil...
Story 1: The creepy fuck
So being unaware of the fact that I was connected with this guy on LinkedIn already.
Ron walks upto my desk and greets me on my first day on floor. Weird, but whatever.
I politely interact, because gotta make friends and create my following to get shit done.
The next day, randomly comes asking for a laptop sticker and I am like WTF! He is like sticker was an excuse, I just wanted to say Hi!
👀
Day 3: same random creep shit. Talks about personal topics and invades personal space uninvited.
Day 4: Keeps starring at me while I ignore and judges me evidently with stupid suggestions on how to exist without being asked for.
Fuck this guy.
Story 2: The classic case of Dunning Kruger effect
So I get introduced to my tech team today and everyone start piling on me to guide them on decision making. The CTO creates a Slack thread with me and Co-founder asking me to get things moving on priority.
The co-founder shut him out right away. Fucking hilarious.
But, a retard starts schooling me on how to use Slack. Lmfao.
Me being polite, said I'll follow.. dude starts bragging on how he wrote company policy to get everyone on Slack yada yada..
To be honest, the Slack experience is beyond broken based on what these idiot has setup.
He literally opened my Slack and responded to the CTO thread.
That's where I got pissed. I upfront told him that hey! Calm your tiddies down. I know how to use Slack. I have used it since it was in the beta.
I have been in much much mucy bigger orgs and places more well structured than what you have here.
I told him on his face what the flaws where and how I felt a downgrade from where I am coming from.
The look on his face was priceless and he started sweating. Lol
Never again he'll school anyone.
I mean I understand if you are humble and genuinely guiding a new hire. But being cocky unnecessarily and shoving things down my throat without yourself knowing shit or know about the other person is purely asshole move.
Anyway, I am still upset about the scam. Fuck this world.5 -
Be humble. Nobody knows everything.
Keep learning: read books, take Pluralsight courses, go to meetups.
Write unit tests for your code. No really! Write unit tests for your code!
Learn what the SOLID principles are.
Your job does not define who you are, you define who you are.1 -
I'm an iOS developer and I cringe when I read job specs that require TDD or excessive unit testing. By excessive I mean demanding that unit tests need to written almost everywhere and using line coverage as a measure of success. I have many years of experience developing iOS apps in agencies and startups where I needed to be extremely time efficient while also keeping the code maintainable. And what I've learned is the importance of DRY, YAGNI and KISS over excessive unit testing. Sadly our industry has become obsessed with unit tests. I'm of the opinion that unit tests have their place, but integration and e2e tests have more value and should be prioritised, reserving unit tests for algorithmic code. Pushing for unit tests everywhere in my view is a ginormous waste of time that can't ever be repaid in quality, bug free code. Why? Because leads to making code testable through dependency injection and 'humble object' indirection layers, which increases the LoC and fragments code that would be easier to read over different classes. Add mocks, and together with the tests your LoC and complexity have tripled. 200% code size takes 200% the time to maintain. This time needs to be repaid - all this unit testing needs to save us 200% time in debugging or manual testing, which it doesn't unless you are an absolute rookie who writes the most terrible and buggy code imaginable, but if you're this terrible writing your production code, why should your tests be any better? It seems that especially big corporate shops love unit tests. Maybe they have enough money and resources to pay for all these hours wasted on unit tests. Maybe the developers can point their 10,000 unit tests when something goes wrong and say 'at least we tried'? Or maybe most developers don't know how to think and reason about their code before they type, and unit tests force them to do that?12
-
In the kingdom of aws reigns the Owner of Products.
In his court many a vassal noble (or a "sre" as they are often called) delivers their tribute.
Wise ministers (called "analysts" in these here parts) advice the Owner of Products on how to instruct his sres and where to lead the kingdom.
Needless to say, in the court the blabber is endless and the egos of the courtiers, deservedly or not, are even larger.
But there is but one member of the court, leader of none but master of japes, who dares to mock not just the courtiers, but even the Owner of Products.
Tester the Jester, from the houses of Operations Research and Quality Assurance.
There is a unique relationship between a ruler and his jester. The jester mocks the ruler, with the most outlandish of propositions, with the most malicious interpretations of the ruler's orders, evidencing the most absurd (but mathematically viable) results of a plan.
The jester makes ridicule of the ruler's edicts... so that the Owner of Products may remain humble, without need to defer to any upstart courtier.
And, in a more subtile manner, the jester prevents any courtier from maliciously complying with the edicts of the ruler.
For all in the court have heard how the lowest among them voiced the preposterous interpretation... And dare not show themselves to be even lower.
TL;DR had an all-hands meeting of tech leaders with the allmighty PO. In the meeting there is this bloke who apparently spends all his time just fucking with the bigwigs' ideas. Dude is a department of one. It seems that his whole job is being an outlandish scenario simulator & sarcasm artist. I now have way more respect for this place. -
We have an intern older than I am and a junior as I am of course I don’t know everything. But i would usually hint him things he should/should not do based on the devs team process pr the dos and donts. But he doesn’t listen most of the time. Only does what I tell him when he’s out of option. He obviously thinks he’s better, he would ask for my help but wouldn’t acknowledge my answer. Rather he’ll spark an argument even cutting me when I’m explaining it nicely to him. I even asked if he badly wants to prove he is correct and I am wrong, I’ll go ahead and ask a more senior dev. Andddd of course he cut me and did not let me ask the senior dev. Then i told him he could do the query himself. Anddd mother fucker shut up bcos I was right. Didn’t even hear him apologize or at least say he was wrong or just be humble and accept it.2
-
I've always thought Gedit (Ubuntu text editing software) doesn't have Redo feature as the shortcut Ctrl + Y didn't work. Just realised it's Shift + Ctrl + Z
Lesson - be humble and look at the provided menu items. -
Advice to new devs: be open minded and adapt to the way things are done at your new gig. Be humble, things that aren't the way you're used to aren't necessarily bad (even bracing style and editors). Have a guru and absorb all you possibly can. Don't be afraid of showing that you don't know yet.
-
I'm starting to feel like coding is too much boilerplate all the time.
I've been thinking about why, and I think (and I'm trying to sound humble here) it's because I'm usually honoring the SRP. But this entails this enormous drawback of enormous amount of code!
Don't get me wrong, I'm usually glad with the design I end up with .... but only after what seems to be hours of typing
Anyone recognize this problem? Suggestions, comments?1 -
0) I can be as socially withdrawn as possible without getting eyes and comments on being socially withdrawn. Going to a tea house with a laptop to code in a corner sipping Earl Grey is great without getting questioned.
1) I can make whatever the hell I want. I can do whatever the hell I want. I can automate whatever the hell I want. And then I can Humble Brag™ to everyone.
2) Because it's fun. I get to meet more folks I haven't met before through hubs like this and programmer Discord servers. And we can be nerdy together.
Edit: Also because I have a fecking pillow fort on my bed made for tucking in while coding. It feels gud in pillow fort. All of us needs a coding pillow fort.1 -
Close to delivering a project on time. Nothing spectacular or particularly big. But it's been my baby and I could introduce other devs to the codebase without having any "negative" feedback on the design; only minor improvements that made total sense.
We've had one technical disagreement where I very unjustly had to pick my suggested solution. The discussion didn't lead to an agreement and we couldn't stay blocked. Old me would have chosen the design that did not (in my not-so-humble opinion) make any sense, just not to step on any toes. Probably imagined toes and steps and whathaveyous as well.
We're making good progress. We're learning from each other. I like this.
This team lead thing is very temporary, but I haven't grown this much in ages. It's just a regular old job where I help someone else get rich, but it's a great tool for self development. I guess I could be spending my time worse... huh, I like the sound of that. -
I could write a fucking dissertation on why snek is objectively a piece of shit, together with all your favorite dumbass collections of syntactic diarrhea full of needless operators and toothless fucking conventions that make no sense in retrospect.
By that I mean to say among all of it's real world uses the foremost is screwing yourself, which is analogous to utilizing the fine hands of a classically trained violinist for virtuous masturbation. And you cannot fix it, you can only Keep It Solemnly Sucking.
Now I'm not saying that if they were humans their lot in life would be to get down on their knees and passionately blow me until my eyes pop out. All I'm saying is their lot in life IS to get DOWN and passionately BLOW me until my eyes pop out, to which the general scientific consensus is indeed yes, it is, and they absolutely should.
But back to commanding the demons trapped inside the sillicon and all the existing ways to to do so being terrible half-assed abortions that serve as a perfect encapsulation and prime example of mankind's greatest shame and failures. If I had to volcanically ejaculate for each time I heard a thorough and perfectly valid critique of insert flavor of fucking stupid, I'd be long-rotting dead from dehydration.
You think that's funny? A man just died creaming in his pants and we are all wiser for it, show some respect. Some people simply do not understand the value of humility, and I will be *proud* to anally humble them for it, free of charge.
Anytime, I swear, ANYTIME that I come back to a language I fucking hate and I'm immediately reminded of why I do everything in my power to avoid it, I invariably come out with the feeling that it wasn't quite as bad as the last time.
THAT is how I measure my progress: still swimming in a sea of deeply decolored and fermenting alien reptile excretion -- but I'm a much better swimmer. This isn't so bad, I may even ignore the burning desire to kill myself next time.
But I'm so blinded by your plump fucking tits that I can't even remember what was my point, I may have just delivered the verbal equivalent of complete mental castration. Again.15 -
Modern Web Developer
(To the tune of "I Am the Very Model of a Modern Major-General" from Gilbert and Sullivan's "The Pirates of Penzance")
I am the very model of a modern web developer
I’m quite fluent with JavaScript; An HTML whisperer
My code is clean and elegant, I genuinely innovate
And even know my way around a Promise and async / await
I’m very well acquainted too with matters vector graphical
I understand why SVG coordinates seem magical
And even without Photoshop I elegantly can produce
A mockup or a logo in most any format that you choose
[Chorus]
A mockup or a logo in most any format that you choose
A mockup or a logo in most any format that you choose
A mockup or a logo in most any format that you choose
I'm quite adept at ES6 expressions like destructuring
I know the ins and outs of functional reactive programming
In short, in matters browser-based or Node.js if you prefer
I am the very model of a modern web developer
[Chorus]
He is the very model of a modern web developer
I know our mythic history, the humble start, the browser wars
I know why Douglas Crockford fought the battle over ES4
The World Wide Web Consortium and Ecma International
My knowledge of our legacy is truly supernatural
With LESS and SASS and CSS, designing for mobility
I’ll perfectly apply the right amount of specificity
From custom fonts and parallax to grid and flex and border-box
I know most every tip and trick both common and unorthodox
[Chorus]
He knows most every tip and trick both common and unorthodox
He knows most every tip and trick both common and unorthodox
He knows most every tip and trick both common and unorthodox
And when it comes to lazy loading, bundling up and splitting code
There’s nothing quite like Webpack, which of course is built on top of Node
Considering my resume, I’m certain that you will concur
I am the very model of a modern web developer
[Chorus]
He is the very model of a modern web developer
When new frameworks and libraries emerge I must be ravenous
And gobble up the hot new thing, my appetite is bottomless
React and Vue and Angular, Immutable, RxJS
The list will be outdated long before I'm finished singing this
My pull requests rely on multitudinous utilities
To help me lint and test and build, a deluge of analyses
And every single day there are a hundred thousand more to learn
The web is going through an irresponsible amount of churn
[Chorus]
The web is going through an irresponsible amount of churn
The web is going through an irresponsible amount of churn
The web is going through an irresponsible amount of churn
This pace is agonizing! Code from yesterday is obsolete!
The speed of innovation is enough to knock me off my feet!
It's happening too fast! I can’t keep up! I’m tired! It’s all a blur!
I am the very model of a modern web developer!
[Chorus]
He is the very model of a modern web developer!1 -
update : we are at hr round baby!!!
part 1 : https://devrant.com/rants/5528056/...
part 2 (in comments) : https://devrant.com/rants/5550145/...
the tech market is crazy mann! it's one of the top indie fintech companies in our country and has a great valuation.
i totally felt that they i am crashing the interviews , and am seriously not trying to be humble. before the dsa round , i was trying to mug up how insertion sort works 🥲
--------
now my dilemma is should i switch if i get the offer. in a summary:
current company:
- small valuation but profitable (haven't picked funding for last 3 years , so poast valuation is some double digit million $, but can easily be a unicorn company)
- very major b2b player in my country. almost all unicorns (including this fintech company) and some major MNCs are their client and they have recently acquired a few other companies of us and eu too, making them- a decent global player
- meh work : i love being a cutting edge performer in android but here we make sdks that need to support even legacy banking apps. so tech stack is a lot of verbose java and daily routine includes making very minor changes to actual code and more towards adding tests , maintaining wrapper sdks in react/cordova/unity etc, checking client side code etc.
- awesome work life balance : since work is shit and i am fast enough, i am usually working only 2-4 hours a day. i joined gym, got into shape , and have already vsited 5 places in last 6 months, and i am a guy who didn't used to have time even on sundays. here, we get mote paid leaves than what i would usually need.
- learning opportunities: not exactly from the company codebase, but they provide unlimited access to various course learning platforms like linkedin learning, udemy and others, so i joined some web dev baches and i now know decent frontend too. plus those hybrid sdks also give a light context to new things
new company :
- positives : multi billion valuation, one of the top players in fintech , have been mostly profitable ( except a few quarters)
- positive : b2c so its (hopefully) going to put me back into racing shoes with kotlin, jetpack and latest libraries.
- more $$$ for your boy :)
- negetive : they seem to be on hiring spree and am afraid to junp ship after seeing the recent coinbase layoffs. fintech is scary these days
- negetive : if they are hiring people like me, then then they are probably hiring people worse than me 😂. although thats not my concern what my main concer is how they interviewed. they have hired a 3rd party company that takes interviews of people FOR THEM! i find that extremely impolite, like they don't even wanna spare their devs to hire people they are gonna work with. i find this a toxic, robotic culture and if these are the people in there then i would have a terrible time finding some buddy engineer or some helpful senior.
- negetive : most probably a bad wlb : i worked for an year for a fast paced b2c edtech startup. no matter how old these are , b2c are always shipping new stuff and are therefore hectic. i don't like the boredom here but i would miss the free time to workout :(
so ... any thoughts about it?4