Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Search - "mindset"
Let's take a moment to appreciate interested and enthousiastic non-developers who really want to learn a programming language.
I am studying Medical IT at my college and most of my classmates aren't coming from an IT background.
Some of my classmates approach me when they're stuck while coding and I try to teach them as much as possible so they understand what they are doing wrong and how to fix it.
I also show them how they can optimise their code step by step and they love it!
As a classmate told me yesterday:
"It's always so much fun working with you. I come up with a small problem, but I end up learning so much more about programming when solving a problem with you. I appreciate that."
It's a mindset I've learned when I was doing my developer apprenticeship back in the day. One of my colleagues told me: "if they want your help because they need a quick fix, tell them to kiss your ass. If you know they've already tried everything they could and ask you specifically because they want to understand what they are doing wrong, they are future developers with great potential, so go teach them."
May the force be with you, my enthousiastic little non-devs ❤️6
I fucking want to skin alive my engineering senior director and VP.
Fucking piece of shit people. Looking at their faces from behind the screen, I can sense them stink doneky balls.
They have made my life hell.
The entire tech architecture is absolute shit in nature and engineers cannot even build a single blue colour button without creating a major fuss about it.
Every single aspect of product is built kept in my only the engineer persona. Everyone else can go and suck a racoon's dick.
And they have no concept of tech debt. They just keep building and building stuff. And then build some more.
Entire engineering org is in rush to ship shit at the end of sprint and if they don't then VP and Director are pissed. So to keep those two half witted donkeys happy, these people ship garbage. And all they comment is "cool, very cool".
And hence, entire fucking product is built because it's cool irrespective of whether it solves a problem or not.
A single user role authorisation or authentication is so fucking complex that it would take an eternity for even a developer to figure what's happening.
Fucking toxic human wastes.
There's a company wide mandate to use a certain tech stack, design guidelines, and a vision that all teams have to align. But these faggots are going in opposite direction to do what they feel like and forcing everyone else to ignore all other engagements or alignments with other teams.
These two people should be skinned alive in town square during noon and then left there until they dehydrate entirely. Fucking baboons.
I am so fucking pissed with such mindset.10
I've told the same story multiple times but the subject of "painfully incompetent co-worker" just comes up so often.
I have one coworker who never really grew out of the mindset of a college student who just took "Intro to Programming". If a problem couldn't be solved with a textbook solution, then he would waste several weeks struggling with it until eventually someone else would pick up the ticket and finish it in a couple days. And if he found a janky workaround for a problem, he'd consider that problem "solved" and never think about it again.
He lasted less than a year before he quit and went off to get a job somewhere else, leaving the rest of our team to comb through his messy code and fix it. Unfortunately, our team is mostly split across multiple projects and our processes were kind of a mess until recently, so his work was a black box of code that had never been reviewed.
I opened the box and found only despair and regret. He was using deprecated features from older versions of the language to work around language bugs that no longer existed. He overused constants to a ridiculous degree (hundreds of constants, all of which are used exactly once in the entire codebase, stored in a single mutable map variable named "values" because why not). He didn't really seem to understand DRY at all. His code threw warnings in the IDE and had weird errors that were difficult to reproduce because there was just a whole pile of race conditions.
I ended up having to take a figurative hacksaw to it, ripping out huge sections of unnecessary crap and modernizing it to use recent language features to get rid of the deprecation warnings and intermittent errors. And then I went through the same process again for every other project he'd touched.
2 leetcode hard questions in 60 mins. That's what I faced in few company interviews. Trust me, if that's the expectation you're having from candidate, you're looking for a leetcode monkey but not a software engineer!
To the interviewers who have such unrealistic expectations, please change your mindset. It's literally impossible to come up with optimal solutions to 2 leetcode hards in 60 mins if I haven't solved those problems before! It just becomes a memorization game not a problem solving round!!!
Looking around where I work, I'm reminded of when I was young and ambitious, like all the other kids around me at the time, with a dislike for all the older dudes and dudettes in upper management. With the exception of three other guys around my age, everyone, including the CEO, was in high school, middle school, elementary school, or not even born yet when I started my career. Just like them, I was plucky and chatty and (trying to be) funny and social. I didn't know how fast I would go from that set to the old fat guy that they look askance at and wonder how I'm still around with my weird ways and "boomerish", socially retarded behavior. What's really galling is that I'm solidly Gen X, like some of them, but I guess I talk more like a Boomer because my parents were older when I was born and I was kinda raised in that mindset. I'm the office schlub now. A man out of my time. And I've never been in any kind of upper management, even. I am Kevin Malone.3
Hello everyone, I've returned and hopefully start ranting again.
I took a long needed break to think about a lot of shit and I'm back with a much healthier mindset and plan for myself.
Aside from the world going to hell what's new?5
If you want to make a startup but don't because there is a similar product or "every niche is already occupied", quit thinking this way.
Yahoo could once easily buy Google. They even received the offer but rejected it. But as for now, Yahoo is nothing.
Tumblr was once a top social network, but they crumbled. Foursquare once was preinstalled to smartphones, and now it pretty much doesn't exist.
Blackberry was a giant, the number one smartphone manufacturer. Where are they now? It wasn't betrayal like it was with Nokia and Stephen Elop.
Matter of fact, I'm now working for the company that entered a heavily occupied niche and over the course of three years pushed every competitor out.
Sometimes giants crumble. Small products crumble way more often, just because there are more of them.
There is always enough room in every niche of every industry. Just enough for your startup. Now, as you can't hide under "it's already occupied, and I can do nothing about it" mindset, the only reason your startup won't make it is that you don't work on it. Yes, accepting it is way less comfortable than hiding, but now you're able to change things. You _can_ do something about it.
Evaluate your goals, ask yourself whether making this startup would be just wasted time in case it never takes off, and if you think it's still worth doing, do it.
There is always enough room for your masterpiece.3
One of my bad dev habits is that I tend to take up too much work because a lot of devs I had to work with seemed not competent enough. It's a bad habit because I get way overworked which influences code quality and deadlines.
I have to learn to trust more in others and give up some responsibility... it's hard though.
I think a big influence on my mindset has been that I never worked in a team bigger than 4 developers and I had way more experience in web dev than the others.
I sometimes may appear as an arrogant prick, but it's not intentional.9
We find our hero, fullstackclown🤡, again harrowed by idiotic management.
Our backdrop and set: A Google calendar appointment was booked between the managers and fullstackclown. fullstackclown had created an all-day appointment for today which reads: "fullstackclown on site".
With the scene set, let us begin our tale..........
Manager: Are you going to be on site today?
fullstackclown🤡: Do you see the appointment I booked on our calendar stating that indeed I will be on site today?
fullstackclown🤡: you are an absolute idiot
I literally don't know what to do anymore. I mean it's RIGHT THERE IN YOUR CALENDAR. HOW MUCH MORE CLEAR DO YOU WANT IT TO BE?! DO YOU WANT A TWILIO APP THAT SENDS YOU A PRERECORDED VOICE MESSAGE IN MY VOICE, CONFIRMING MY CALENDAR APPOINTMENTS?!
What type of mindset causes this type of behavior of double or triple checking things as simple as a calendar booking? Honestly shows a complete breakdown of normal mental functioning in my opinion.5
Never trust organizations who claim to have adopted the agile mindset, saying they use SAFe or Scrum or w\e, unless the teams themselves say that they have full autonomy for the release process. Because the upper management is not agile. Especially in older organizations. Typically they are the ones who will have the final say if teams don't have autonomy.
As a consultant, I joined a team on an organization who says that they're using SAFe. "Scaled Agile Framework". There is absolutely nothing agile in that horrid process.
Agility only happens at the team level. That's where we seem to improve the ways of working. Levels above, nothing happens.
I've been on this team for a year and we haven't released ANYTHING to customers. So those "release trains" are sitting on their stations.
Upper management refuses to green light a product release to customers that doesn't contain everything they want in it. In their mind they have the "perfect product" in mind and it needs to be perfect before it can be delivered to anyone. Fighting them on that idea has proven pointless. They don't understand what an agile mindset it. At the moment we are providing zero value to customers.
The MVP release date has been pushed for over 6 months now because nobody can come to a conclusion as to what needs to be finished before the release. They can't accept that we'd just release it now and keep iterating it. Everyone from the team members to the organization leader to their grandmother has to green light a release. People argue about minor nuances. Semantics. Big manual regression tests are needed to make sure that everything works. When a minor bug appears, PO's lose their minds and start calling out developers to investigate and fix it, and to set up more gateway checks that these things don't happen.
Organizations don't adapt the agile mindset very easily. Frustration sets in. Waterfall is forever.5
I've really begun to resent working with an organization where everyone above the team has a complete industrial mindset. Everyone seems to look for someone to blame, covering their own asses, and that leads to gateways and checks to make sure the quality is good before showing anything to anyone. Typically the agile mindset accepts failure, learns from it and moves on, continuously improving. Blame should not be a part of it. Failure should be a lesson on how to improve. Damn some people are just dinosaurs.3
There is always one colleague who is not satisfied with the management and keeps complaining to other than management persons. One of my senior has mastered this ability and it always make my mindset f**ked up.4
Some people try to talk by changing their accent to look cool.
And my mind every time is like - man stop that and try to change your mindset first.1
Depends. If the schedule is busy enough, i try to carry on and focus on simpler, low-effort high-reward tasks so i don't stagnate.
If there is nothing getting burned in the oven i just call it the day and go out or relax with some game/show ^_^
I feel like all this "keep calm and carry on" mindset to solves crisis is just the result of bad micro-management of the society as a whole, but maybe i just get filosophical and anarhist when i'm low on motivation 🤔
So I’m 20 years old. Got a decent job as software engineer with a really good pay and really want to break into machine learning.
Aside from the syntax when I’m watching tutorials or reading books, I see data scientists and mathematicians make design mistakes in their code and it hurts my eyes and triggers my ocd.
I need tips on how to put my mindset in a moldable state so I can judge less and learn more and absorb data. Like you know that philosophy that when u get old your brain can’t learn things as fast anymore? I feel like that’s already happening to me rn at the age of 20.5
you're not going to believe me, but it seems like I have the recipe to achieve the feeling of absolute freedom.
People have the distinct mechanism of "believing" in somebody or something. You should only _believe_ in things you _made_.
As nothing is truly created from scratch, only believe in the part _you_ created.
I know, this recipe is not some "lifehack" or a shortcut, because achieving this mindset is astonishingly difficult, but it's at least possible.2