Dear people who complain about spending a whole night to find a tiny syntax error; Every time I read one of your rants, I feel like a part of me dies.

As a developer, your job is to create elegant optimized rivers of data, to puzzle with interesting algorithmic problems, to craft beautiful mappings from user input to computer storage and back.

You should strive to write code like a Michelangelo, not like a house painter.

You're arguing about indentation or getting annoyed by a project with braces on the same line as the method name. You're struggling with semicolons, misplaced braces or wrongly spelled keywords.

You're bitching about the medium of your paint, about the hardness of the marble -- when you should be lamenting the absence of your muse or the struggle to capture the essence of elegance in your work.

In other words:

Fix your fucking mindset, and fix your fucking tools. Don't fucking rant about your tabs and spaces. Stop fucking screaming how your bloated swiss-army-knife text editor is soooo much better than a purpose-built IDE, if it fails to draw something red and obnoxious around your fuck ups.

Thanks.

Bought a Logitech G13 a few years ago knowing that the Linux support isn't good. Thought fuck it, I'll develop something for it.

That didn't go as planned. Tried numerous times to write something but the fucker is proprietary and I couldn't figure out how to get data from it.

Decided to try it again tonight with a "You're not winning this time, motherfucker!" mindset.

Figured out how to read data from it, looked long enough at the data coming in to discover patterns and started programming while testing my ass off.

Two hours later I have "mapped" all specific data points that the device sends to the hardware keys and now, whenever I have the device connected and run the program (node, no kidding), it displays which key I'm pressing when I press a key!

I finally fucking won.

This rant is devoted to my study friends. You see, I never knew what it was to not have people making fun of you/bullying you until I started my study.

Elementary school + highschool was one big mess of bullying, being made fun of and hardly having any friends.

At highschool I decided I wanted to go into IT. Especially programming. Programming in particular because when I was programming, I, for once, was the one in control. The code listened to me and for that tiny moment I was god.

Never really had much friends though and when I told my parents I wanted to do an MBO study (application development), my mother warned me that although she and my dad supported me with whatever my decision would be, MBO level studies were rough because of the general mindset/atmosphere there.

I thought fuck it, I want to do programming because that seems awesome and maybe I'll even make some friends with the same interests!

Then study arrived. Met a few guys with similar interests and we started hanging out together.

And then it came back just like before. Two guys who loved bullying and I was still a quite easy target because I couldn't stand up for myself.

But, then something happened. I liked a girl, she was in the hallway and two of the bullies (there were about 4-5 in total) got up and started fucking around with me (about her) and I just sat there, not daring to do anything with tears in my eyes.

Then two of my classmates noticed it, quickly came to my desk and started pushing the guys away with 'back the fuck off, what the fuck has he done to you?!'. Then one of those guys (now still about my best friend) came to me to see if I was alright.

We started talking. Then at some point, another bully had a go at me. This would be the final time. He was about 2 meters tall (I was about 160cm or something) and stood there in the door opening with a very nasty smile saying all nasty stuff, trying to intimidate me and probably tried to make me feel like crap again.

Nice guy on my right asked me to step to the left. Gave that guy a huge fucking foot in his chest and he smacked onto the ground. Made a gentleman's sign like 'go ahead, sir!' while gesturing towards the door.

From that moment on the bullying stopped. Throughout my study, some other bad things happened but those guys were always there for me.

Although I've lost touch with most of the guys (they're on social media, I'm not really), we still meet up once in a while and have a lot of beers while talking and laughing and thinking back to the good times we had together.

The study wasn't the best for what we were taught as in studying but it's the best choice I've ever made nonetheless.

Oh and that best friend and I still have loads of contact!

Started university of applied sciences to become a computer engineer instead of a web developer.

Met a lot of kids that are in the "computer studies = games + YouTube".

They struggle hard, but don't do anything to learn...

Then there's this classmate, the guy is 10 years older than me, is trying really hard, and struggles a lot.

I've been helping him out with assigns by asking questions, and he asks me how to solve a problem in general, not the assignments which is super refreshing to see someone that wants to learn.

Currently trying to help him "translate" the simple stuff into c++:

So, if you want the char at a certain position in a string, how would you tell me to do it?

"well, take the list, look at position x and bam its done"

Try writing it like that!

And instead of "[i]" he writes "stringvar[i]"

He really appreciates the help and I hope he'll get the mindset soon :)

Would hate to lose a motivated guy when there's so many idiots copy pasting everything from tutorials...

The Linux Kernel, not just because of the end product. I find it's organizational structure and size (both in code and contributors) inspirational.

Firefox. Even if you don't use it as your main browser, the sheer amount of work Mozilla has contributed to the world is amazing.

OpenTTD. I liked the original game, and 25 years after release some devs are still actively maintaining an open source clone with support for mods.

Git. Without it, it would not just be harder working on your own source code, it would also be harder to try out other people's projects.

FZF is possibly my favorite command line tool.

Kitty has recently become my favorite terminal.

My favorite thing open source has brought forth though is a certain mindset, which in the last decade can be felt most heavily in the fact that:

1. Scientific papers with accompanying GitHub urls, especially when it comes to AI. Cutting edge research is one git clone away.

2. There are so many open hardware projects. From raspberry pi to 3d printers to laser cutters, being a "maker" suddenly became a mainstream hobby.

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.

Progression in mindset of a developer trough professional life:

1. I'm going to make my code so efficient and beautiful that everyone will envy it!

2. I'm going to make sure I keep separation of concern.

3. I'm going to make my code at least maintainable for other developers.

4. Well shit. At least it works, for now.

Privacy & security violations piss me off. Not to the point that I'll write on devRant about it, but to the point that coworkers get afraid from the bloodthirsty look in my eyes.

I know all startups proclaim this, but the one I work at is kind of industry-disrupting. Think Uber vs taxi drivers... so we have real, malicious enemies.

Yet there's still this mindset of "it won't happen to us" when it comes to data leaks or corporate spying.

Me: "I noticed we are tracking our end users without their consent, and store not just the color of their balls, but also their favorite soup flavor and how often they've cheated on their partner, as plain text in the system for every employee to read"

Various C-randomletter-Os: "Oh wow indubitably most serious indeed! Let's put 2 scrumbag masters on the issue, we will tackle this in a most agile manner! We shall use AI blockchains in the elastic cloud to encrypt those ball-colors!"

NO WHAT I MEANT WAS WHY THE FUCK DO WE EVEN STORE THAT INFORMATION. IT DOES IN NO WAY RELATE TO OUR BUSINESS!

"No reason, just future requirements for our data scientists"

I'M GRABBING A HARDDRIVE SHREDDER, THE DB SERVER GOES FIRST AND YOUR PENIS RIGHT AFTER THAT!

(if it's unclear, ball color was an optimistic euphemism for what boiled down to an analytics value which might as well have been "nigger: yes/no")

Vsauce has made all of its Mindfield content free on youtube...

Watched the episode about moral licensing

TL;DR; If you do something very good you tend to compensate and give yourself a free pass to do not so good

It happens to me in software when I accomplish something really fast, like a bumpy process that is undefined and in most cases should take X amount of time, but due to luck + experience + right mindset I get it done like 5 times faster...

I end up wasting the other parts of the time feeling good about myself and exploring google maps and writing rants here...

!!privacy
!!political

I had a discussion with a coworker earlier.

I owed him for lunch the other day, and he suggested I pay him back either with cash (which I didn't have), Venmo, or just by him lunch the next time (which I ended up doing).

I asked about Venmo, and he said it was like paypal, but always free. that sounded a bit off -- because how are they in business if it's always free? -- so I looked it up, and paid special attention to their privacy policy.

The short of it: they make money by selling your information. That's worth far more than charging users a small fee when sending $5 every few weeks. Sort of what I expected when I heard "always free," but what surprised me is just how much they collect. (In retrospect, I really shouldn't have been surprised at all...)

Here's an incomplete list:
* full name, physical address, email, DoB, SSN (or other government IDs, depending on country)
* Complete contact list (phone numbers, names, photos)
* Browser/device fingerprint
* (optional) Your entire Facebook feed and history
* (optional) all of your Facebook friends' contact info
* Your Twitter feed
* Your FourSquare activity
(The above four ostensibly for "fraud prevention")
* GPS data
* Usage info about the actual service
* Other users' usage info (e.g. mentioning you)
* Financial info (the only thing not shared with third parties)

Like, scary?

And, of course, they share all of this with their parent company, PayPal. (The privacy policy does not specify what PayPal does with it, nor does it provide any links that might describe it, e.g. PayPal's "info-shared-by-third-parties" privacy policy)

So I won't be using Venmo. ever.

I mentioned all of this to my coworker, and he just doesn't understand. at all. He even asks "So what are they going do with that, send me ads? like they already do?"

I told him why I think it's scary. Everything from them freely selling all of your info, to someone being able to look through your entire online life's history, to being able to masquerade around as you, to even reproducing your voice (e.g. voice clips collected by google assistant), to grouping people by political affiliations.

He didn't have much to say about any of them, and actually thought the voice thing was really cool. (All I could think of was would happen if the "news" had that ability....) All of his other responses were "that doesn't bother me at all" and/or "using all of these services is so convenient."

but what really got me was his reaction to the last one.

I said, "If you're part of the NRA, for example, you'd be grouped with Republicans. If they sell all of this information, which they do, and they don't really care who buys it or what they do with it... someone could look through the data and very very easily target those political groups."

His response? "I don't have to worry about that. I'm a Democrat, and have always voted Democrat. I'll tell anyone that."

Like.
That's basically saying every non-democrat is someone you should be wary of and keep an eye on. That's saying Democrats are the norm and everyone else is deviant and/or wrong.

and I couldn't say anything after this because... no matter what I said, it would start a political conflict, and would likely end with me being fired (since the owner is also a democrat, and they're very buddy-buddy). "What if they target democrats?" -> "They already do!" or "What if democrats use it against others?" -> "They deserve it for being violent and racist, but we never would" (except, you know, that IRS/tea-party incident for example...)

But like, this is coming from someone who firmly believes conservatives are responsible for all of the violence and looting and rioting and mass shootings in the country. ... even when every single instance has been by committed by democrats. every. single. one.

Just...
jfl;askjfasflkj.

He doesn't understand the need for privacy, and his world view is just... he actually thinks everyone with different beliefs is wrong and dangerous.

I don't even know how to deal with people like this. and with how prevalent this mindset is... coupled with the aforementioned privacy concerns... it's honestly *terrifying.*

Gotta say, I find it awesome that I can connect with some devRanters through encrypted channels.

It's awesome to talk to devRanters with the same mindset through channels that offer a very high level of security/privacy.

Thanks!

My Girlfriend broke with me today.

We was in this relationship from two years now. we was doing very good, our relationship was not toxic, no fights, no bad words, zero problems.

One month ago she goes to travel with her evangelical aunt to the beach. Her aunt have lot of money she gets from scamming all that believers. I was happy for my ex-gf because here in out city she was having lot of problems of health, mainly because she was not very mind stable and that degraded her health.

When she goes, her physical and mental health improve a lot. i was happy she is stable now. Her aunt have some Church around the city they go, aunt started to bring her very often to the church. She started to strongly reinforce they God beliefs.

Of course im atheist, she know that from very long time ago. But of course when she started to be more devoted, feels dont fit with me. I refuse to change my mindset about that topic.

Today she says we must broke because im not a believer. This was the most painful experience in my life. I fall in cry for three hours. I truly love her. I recently wakeup and decide to write this rant. I dont have too much friends to talk apart from her. So i wish to share this here.

Im unemployed, she was my only support all this job hunting times. Now she was gone and im alone, this hurts a lot.

Im trying to dont fall deep af, to non return path.

Fuck religion. and her fanatic aunt.

Looking at code in our workplace.. I realized one thing. Like Devops, legacy code is actually a mindset.

So here goes my thought:

A piece of code is not legacy because it was written ten years ago.

A piece of code is legacy because it looks like a piece of legacy code.

With the legacy code mindset, you end up writing legacy code no matter where you are, when you wrote it.

I was looking at some part of our code which we written in just the last few months, and I can’t help but think that they were legacy, so it really doesn’t matter when it was written!

It is more about how you write your code that determines whether it is legacy :)

Hopefully this was not crazily confusing anyone. Have a good day guys & gals!

I got laid off from my previous position as a Software Engineer at the end of June, and since then it was a struggle to find a new position. I have a good resume, about 4 years of professional dev experience and 5 years of experience in the tech industry all together, and great references.

As soon as I got laid off, I talked to my old manager at my previous company, and he said that he'd love to hire me back, but he just filled his last open spot.

In order to prepare, I had my resume reviewed by a specialist at the Department of Labor, and she said that it was one of the better resumes that she had seen.

There aren't a huge amount of dev jobs in my area, and I got a TON of recruiter emails. But they were all in other states, and I wasn't interested in moving.

I applied to all the remote and local positions I could find (the ones that I was qualified for,) and I just got a bunch of silence and denials from all my applications. I had a few interviews that went great, but of course, those companies decided to put the position on hold so they could use the budget for other things.

The silence and denials were really disconcerting, and make you think that something might be wrong with you or your interviewing abilities.

And then suddenly, as if the floodgates had opened, I started getting a ton of callbacks and interviews for both local and remote opportunities. I don't know if the end-of-year budget surpluses opened up more positions, but I was getting a lot of interest and it felt amazing.

Another dev position opened up at my previous company, and I got a great recommendation for that from my former manager and co-workers. I got a bunch of other interviews, and was moved onto the next rounds in most of them.

And finally, I got reached out to regarding a remote position I applied for a while ago, and the company was great about making the interview process quick and efficient. Within 2 weeks, I went from the screening call, to the tech call, and to the final call with the CTO. The CTO and I just hung out and talked about cars/boats/motorcycles for half the interview, and he was an awesome guy. AND THEN I GOT AN OFFER THE NEXT DAY!

The offer was originally for about the same amount as I made at my previous job, but I counteroffered up a good amount and they accepted my counteroffer!

It's a great company with offices all over the world, and they offer the option to travel to all those offices for visits if you want. So if you're working on a project with the France team and you think that it'd be easier to just work with them face-to-face, then the company will pay to fly you out to Paris for the week. Or you can work completely remotely. They don't mind either way.

I'm super excited to work with them and it feels great to be back in the job world.

Sorry about the long post, but I just wanted to tell my story and help encourage anybody out there who's going through the same thing right now.

Don't get discouraged, because you WILL find an awesome opportunity that's right for you. Get somebody to go over your resume and give you improvement recommendations. Brush up on your interviewing skills. Be sure to talk about all the projects you've worked on and how they positively impacted people and/or companies.

This is what I found interviewers responded the best to: Be sure to emphasize that you love learning new things and that you love passing along that knowledge to other people, and that your goal is to be an approachable and reliable source of knowledge for the company and to be as helpful as possible. It's important to be in a position that encourages both knowledge growth and knowledge sharing, and I think that companies really appreciate that mindset in a team member.

Moral of the story: YOU GOT THIS!

!rant

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.
We're currently working with Java, PHP, JavaScript and some require Node for their semester projects.

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 ❤️

There are 3 types of questions.

Type 1 is a question that can easily be answered and mostly appears as the first result in Google.

Type 2 is a question that can be answered by stitching together various type 1 answers.

Type 3 is a question that has not been answered. It may be a bug you’ll have to find out about by reading an email chain 12 years ago or maybe a reason why epoll() doesn’t work on Linux VMs. There is no solid yes or no. You’ve most likely encountered this when reaching page 3 of your Google results and every link is purple (visited).

This is where depression and isolation hits. This is where you realize that if you can’t help yourself, no one else can (or has the experience and time to do so). This is where you must rely on your knowledge and infer an answer to your question pushing your concepts and theories to the extreme. If you solve this question, you’re solving it for someone else who may trek the same path later in the future. You’re solving it for the world!

If you’re willing to solve, attempting to solve, or even giving a reasonable inference about a type 3, you have a true engineering mindset.

I'm real tired of my coworkers always trying to one up me and being elitist about their code. Like I get it, you think PHP is shit, C is so much better than Java. Wow, you must be so knowledgeable! /s

Just because you're bashing on bad languages and talking shit doesn't mean you write good code, and in fact your code isn't top quality, I've read it. All you're going to accomplish with an elitist mindset is close yourself off to improving, and that's probably the worst thing you can do as a developer.

I get pissed when somebody takes me out of my coding mindset for something minor. A deep bubble of abstract thought gets popped so that I can be told that we'll be eating dinner in an hour. I then have to start my thought processes from scratch.
This is why I can't get any work done during the daytime, and why I do all my coding at night.
This comic depicts this issue perfectly.

This week Im firing a guy who I hired 5 weeks ago. I cant take it anymore. I setted up a nice environment for him and he keeps taking whole day sometimes two or three to do a 2 hour task. He came from electrical engineering background and never had a software dev job. As a person hes more creative type not logical based type. I dont have nor patience nor resources nor time to teach him basics that be could google but simply doesnt have the mindset to do. Sorry bill gates not everyone can learn how to code, or at least not everyone should.

Advice to other people hiring new hires: test the shit out of them before hiring, dont hire from gut. This guy was giving out a nerd vibe, but the only nerd thing that he has is nerdy puns, other than that as a software dev he know less than I did when I was 12 years old.

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.

Devs are my closest friends and I have learned so much from you all.

They ask some of the best questions, their skill set is ever evolving, they have the real problem solving mindset, they are critical towards any and everything in a good way, and so much more.

There was this thread asking what a bad Product Manager is and this answer takes the cake.

The point highlighted in red is the ultimate truth.

Devs are most innovative people of our times. Big shout-out to you all and thank you for making me who I am today :)

To that person who came here to weep about how his employees don’t want to work on weekends and how he’s gonna force them to and deleted his rant that was downvoted to oblivion:

Please re-evaluate your mindset. Today it’s just downvotes, tomorrow it’s your entire staff quitting and pressing charges.

The C Mindset: "Just get the code to compile so we can get to the real work... Debugging."

Enjoying the college life to the fullest was the mindset of the confident boy, who now burns the midnight oil to cope up with world and give himself a proud future.

Is this a story of some successful person, who has achieved a lot in his life?

No, it is the story of the guy who lost all his hopes of future after spending the very first month in his college.

The first month was enough to perceive the reality of the domain I got myself let into. It was enough for someone, who didn’t even knew what programming languages are, to realize how left behind is he from the people around him.

Being from a private college which hardly anyone recognizes, expecting them to prepare me to stand out lone would be foolishness. I took my first step and started learning my very first programming language , Python.

I met some people with similar interest .We discussed, we exchanged resources, we used to talk to seniors to guide us. And yes, we were guided.

There were many bad days. Days which made me regret about starting late. Many a times I myself confirmed me as useless and some other time people did. The good thing is I never stopped , and improved myself with each day.

And now, after spending more than a year in the same college, I look at the things I have learnt. Today I can develop decent websites, can train neural networks, can make me stand in good position in coding platforms.

All you need is to take a step.I may not be the best, but I am definitely better than what I was yesterday.

If you have started something, then concentrate on finishing it.

Anyone else approach coding with the mindset of - "make it work, then make it right".

It really helped me up my productivity

Job ad: Must have large amount of experience working in a completely unstructured environment, be hyper innovative and be willing to work HARD and have a PRODUCT MINDSET!

Translation: Management doesn’t know what they want and even if they did they are completely incompetent at communicating what that is. You will be accountable for reading their minds and coming up with something that makes them look good. This task is impossible so you are expected to sacrifice every spare second of your life in vain pretending it is possible. If you do somehow achieve it you will not be given any credit due to your “product mindset”.

Something I refer to as the "Lost Cause Syndrome".

Basically you start working on a project enthusiastically with the resolution to write the best possible code. But either one (or some or all) of management, client and colleagues succeed in transforming the project into a comedy (or tragedy, depending on your outlook) of errors.

Then finally, one day you decide that the project is a lost cause and stop caring about it. You end up in a "Let's get this over with and get out of here" type of mindset without making any efforts to improve the situation.

When I’m at work I can’t wait to get home to work on personal projects only to get home with no energy and just procrastinate and/or play games entire weekend/afternoon.
Think is i also feel extremely guilty if i try to relax and do nothing, but at the same time able to understand that i need time to chill, just can’t get in a positive mindset about it. Am i the only one?

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.

Good riddance.

My code review nightmare?

All of the reviews that consisted of a group of devs+managers in a conference room and a big screen micro-analyzing every line of code.
"Why did you call the variable that? Wouldn't be be more efficient to use XYZ components? You should switch everything to use ServiceBus."
and/or using the 18+ page coding standard document as a weapon.

PHB:"On page 5, paragraph 9, sub-section A-123, the standards dictate to select all the necessary data from the database. Your query is only selecting 5 fields from the 15 field field table. You might need to access more data in the future and this approach reduces the amount of code change."
Me: "Um, if the data requirements change, wouldn't we have change code anyway?"
PHB: "Application requirements are determined by our users, not you. That's why we have standards."
Me: "Um, that's not what I ..."
PHB: "Next file, oh boy, this one is a mess. On page 9, paragraph 2, sub-section Z-987, the standards dictate to only select the absolute minimum amount of the data from the database. Your query is selecting 3 fields, but the application is only using 2."
Me: "Yes, the application not using the field right now, but the user stated they might need the data for additional review."
PHB: "Did they fill out the proper change request form?"
Me: "No, they ...wait...Aren't the standards on page 9 contradictory to the standards on page 5?"
PHB: "NO! You'll never break your cowboy-coding mindset if you continue to violate standards. You see, standards are our promise to customers to ensure quality. You don't want to break our promises...do you?"

1. Being the only single wringable neck to keep 40+ websites afloat, plus 3-5 new ones coming in or being built each month all with an overseas team that uses Google Translate to communicate and who are also in an active war zone.
2. Being fired for being “too old” in my mindset about how to do things. I had just turned 40 and my boss was 24 and distracted by all the shiny frameworks when all the marketing person needed was a simple off-the-shelf CMS-based site to publish company offers.
3. Jumping into the middle of a HUGE clusterfuck of thousands of Slack channels, wikis, and Jiras and an outmoded content management system while trying to learn the ropes from a guy who has no time to teach properly and then who abruptly leaves the company with scant documentation on everything that he held mainly in his own head. And there was no way I.T. was going to allow him to have the ability in Zoom to make a video of his training sessions, for no discernibly good security reason at all.
4. Working for only 9 months at two separate companies for two separate frat dudes who could have been clones of each other and whose egos made them into seagull managers* in every sense.
5. Being told by a new employer that they’re hiring me to be the head of their new web team only to find myself shuttled off to obscure contractor roles at MegaCorp Inc and AcmeCorp Inc.

I have 17 more years of this shit ahead of me before I can retire.

*If you haven’t heard of this: Someone who flies in, makes a lot of noise, shits all over everything, and flies out leaving everyone else to clean up the mess.

!dev - cybersecurity related.

This is a semi hypothetical situation. I walked into this ad today and I know I'd have a conversation like this about this ad but I didn't this time, I had convo's like this, though.

*le me walking through the city centre with a friend*
*advertisement about a hearing aid which can be updated through remote connection (satellite according to the ad) pops up on screen*

Friend: Ohh that looks usefu.....
Me: Oh damn, what protocol would that use?
Does it use an encrypted connection?
How'd the receiving end parse the incoming data?
What kinda authentication might the receiving end use?
Friend: wha..........
Me: What system would the hearing aid have?
Would it be easy to gain RCE (Remote Code Execution) to that system through the satellite connection and is this managed centrally?
Could you do mitm's maybe?
What data encoding would the transmissions/applications use?
Friend: nevermind.... ._________.

Cybersecurity mindset much...!

First day on my first job ever, the boss asks me what I want to do. I indicated that I had some experience with php and the yii framework (which was at some point very cool xD), so I wanted to start with something like that. And so it goes: after two days of watching laracasts (which is an awesome platform by the way! :O) I got assigned to a project.

Now the company I work at uses some kind of self built system that tracks how many hours are spent on which project, and compares that to how many hours was estimated implementing a feature would take. That's cool, but then I saw that for the project I was working on the time estimated was 5 work days. This was the estimate for both designing the interfaces and implementing both front and backend. I knew in advance that this was probably way to little time for me, but didn't want to come over as the new kid who can't do shit x)

Anyway, I started on the project and was having fun, but the biggest time consuming aspect of the project was not necessarily that I didn't have enough experience: it was that the developer who started this project and made most of the design choices had written some very messy code, without tests or apparently any refactoring. Also, everything was extremly inconsistent and not according to all the best practices I just watched in my laracasts spree.

So fastforward a little: we're way over the estimated hours. Yay. Now suddenly the boss comes by with an almost angry face that the client is becoming angry and we need to finish soon. He makes it entirely our (me and the front end guy) problem and I just decide to say nothing and try to work faster.

Now I'm stuck writing fugly code on top of more fugly code and when I mentioned to my front end guy that I was almost finished with feature but I only needed to finish up the tests, he said something like "oh just don't write tests, that'll take too long"... Is that really the mindset of this company?! No wonder the project I work on was in a very bad state.

Thanks to devrant I see now that I just need to say something if I know that I won't be able to complete something in a certain amount of time and that other people are just like me (thank god). :) I think I'll need to post more rants to vent my frustrations x)

Start changing how young people look at programming. It’s not nerds doing nerdy things, it’s about real people using code to solve real problems. I think once the mindset changes it will get many more people interested.

So I sit in IT-Support, and let's just say that I don't quite have the mindset of a supporter, I'm simply sitting here to wait to move onto programming.

Anyways, I get a call and the person instantly asks me to check if someone else is busy, I ofcourse check up on the person, see that he sits in a completely different department than me (roughly 200km away from me) and I respond with the following "I can't check if he's busy, have you tried calling his phone".... This half brained dick bag, then says "I go on hold when I call his phone" aka the person is in the middle of a call...

I barely have any hair left, kudos to the people who work in IT-Support daily.

Biggest challenge as a dev was breaking away from the mindset that I was some brilliant, genius programmer and accepting that I like most people knew nothing. And that there was something I could learn from everyone, including my juniors.

Why the fuck does people who teach in professional colleges doesn't have the mindset to update their godamnn fucking dinosaur knowledge to the least basics of modern technology.

Had to do this mini-project for uni, and the languages allowed included java, python, php or any similar frontend tools for creating desktop app or web app. I planned on taking React + Express cz apparently that'll fall in the category.

Now she starts yelling at my project saying its not allowed and when I fucking asked her "can I use node.js which is basically javascript" she said yes.

And for gods sake she has a Masters degree and phd but doesn't even know what's the difference between get and post request!! Fed up with this college shit!!

Why do so many companies think that frontend work can be stuffed at the end of the product development right before a release is expected.

And to top it off, expect all things to be working, smooth, animating, responsive, crisp, fast with 100 fucking lighthouse score.

🖕 To everyone who thinks frontend work is meh!, Not real programming and similar. Fuck you!

Part 3: today has become a blog post.

WARNING: this is loooooooooooong

Background is my boss and I were talking about hiring the right people, also generalists vs specialists.

Essentially John and I are the specialists. When something goes wrong it ends up escalating to either him or me. But this is not sustainable as I can't handle the stress and most likely he eventually won't either.

And this goes back to general hiring standards.

All the good people leave and the remaining ones are stuck with all the problems and eventually for one reason or another they leave as well... or the code keeps getting worse... until someone decides to scrap everything and build a new one... But now the only people left to lead teams are monkeys.

Now current problem is the only person that can replace me is John and the only person that can replace John, at least in handling issues, is me...

It's a certain type of person, people that have a growth mindset and can pick things up.

Google and strong tech companies are full of these types of people where if needed there's always someone that can step in and help. They have the background and the ability to quickly learn. This also lets them innovate and identify and solve new problems.

I think that's what the technical interviews are for, to find these types of people.

And you really can't train this. I'm not sure how effective our "new" training program on high quality development is but I'm guessing it's not. Excellence has to be in the culture and it's not something that can be built overnight or by randomly hiring people.

So in a sense, tech companies aren't really paying well, they're paying cost to what their hires are really worth, after they've verified it, and enough to keep them from leaving.

That moment when you change your mindset from "I'll probably leave the office by 6pm" to "I hope I'll leave before midnight"

Just was at the FOSDEM beer party and although it was so busy that the line to get a beer took insanely long to get shorter, I met some really cool people and it was quiet nice to be among so many people who mostly share the same mindset!

Two days to go 😁

Any other noob coder here trying to gain the mindset of the pros, enjoy the environment although he doesn't get half the jokes and rants, and trying to fake it till he make it? (:^/)

No crazy prep, ever.

I always go in with a 'this is me, these are my skills, that's all you're going to get' mindset.

I of course do some research (about the company, their culture, technologies and stuff like that) but I find it kinda weird to spend a big amount of time on interview prep when there is a chance of rejection. (personal opinion)

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!!!

:)

So at the moment I'm developing a RESTful API for an internal project at work and I'm starting to learn and understand about HTTP status codes.

So I started incorporating proper response HTTP status etc, but my co-workers don't understand what any of it means. They think that just sending a JSON response is enough with any messages should be enough. I think this mindset stems from people who just do simple AJAX calls in JavaScript just to get or store data.

It's these kind of developers that I find are lazy or have no motivation to improve themselves, which is disappointing.

Game of Thrones totally fucked up my coding mindset tonight. I guess it's time for bed.

The ammount of digging I have to do in order to fix something or building the mindset to do something i don't want to.

I have a mental block regarding people telling me what to do. I consider myself a pretty chill dude, but when someone says "do this" my mind automatically goes into "oh fuck that" mode.

I hate being this way, wish I could just switch that shit off and work on what i am told and be done with it.

I can spend all weekend fucking around with php. But the moment someone tells me to do something at work with it I start dreading it

This applies to damn near everything in life except for anything that has to do with my children.

My dad was neglectful as fuck, that itself makes me overly paranoid of making my children feel the same way I did growing up. Just wanted to throw that out.

It seems I did some progress today! Thanks Dr Devrant!
Dr Devrant: tell me about your father
Me: motherfucker sucks camel balls

I know I was one at some point, but juniors can be so frustrating at times.

After some pairing for a while they're quick to adopt the "Dev" mindset and think as far as they need to...

... but with this latest batch... that day couldn't come sooner 🫠

Having to explain how exceptions work again is the last thing you wanna do under tight time constraints 🙃

!dev

I come from a small shitty valley where all that people want to achieve is getting approved for loans to buy more cows and shit.. My only friend comes from there as well but he’s different, more like me.. build a life, get out and pursuit something better and bigger..
We grew up smoking everything we could and drinking everything we got because what else are we gonna do, put shit on fire? Been there, done that.. it sucks growing up on the poop hole of the world.
We both left that shithole and started careers but he’s throwing it all out the window.. he’s getting caught with weed, DUI and shit. just a few years ago he got off of more serious drugs.. He built a career and shit for about 10 years but right now he’s just throwing it all away because drugs are in his comfort zone. But he has to go give Pias samples for a while now and if he doesn’t stop he is not getting his license back and the unemployment insurance won’t even pay him because (although he lost the job because of Covid) they said it’s because he smokes weed.
Without the license goes his career as he’s a service electrician.

So fucking hurtful to see, man.
And so hard to accept that he won’t listen and than I’m not his dad who can tell him what to do..

90% of the kids I grew up with who managed to leave that shit hole ended up as homeless junkies.. I guess I’m happy to have the mindset to not end up like them.. and that’s really all it is, the mindset is the only difference (which is complex in itself of course like parenting and stuff)

My biggest regret is the same as my best decision ever made.

The company I work for specializes in performing integrations and migrations that are supposed to be near impossible.

This means a documented api is a rare sight. We are generally happy if there even IS an (internal) api. Frequently we resort to front-end scraping, custom server side extensions and reverse-engineered clients.

When you’re in the correct mindset it’s an extreme rush to fix issues that cannot be fixed and help clients who have lost most hope. However, if your personal life is rough at the moment or you are not in a perfect mental state for a while it can be a really tough job.

Been here for 3+ years and counting. Love and hate have rarely been so close to each other.

I joined Devrant just for the stickers and the ball.Now,I don't even want those stuff,the fact that people with same mindset share their rants is enough to keep me glued to this stuff

I carry the same mindset as an aspiring programmer as I did when I was a music major. There were times I practice for hours and got very little out of it in terms of quality (because I wasn't interested, focused or willing) and then there were times I practiced for 20 mins and really made progress on the piece. So I always keep that in mind to save me time and to produce better code overall.

People with "I am a senior, only I have to be right" mindset are really fustrating to work it.
It is not that hard to accept the truth. No one can be right all the time and no one gonna look down on you for that. You don't have to shove off-topic stuffs down the other people's throat when you realize you might be wrong.

People refusing to learn an improved programming language or technology, because it might contradict to what they "already know" and you're just there mastering it and appreciating its advantages that you will never learn if you had a closed mindset.

go 3 years back and change my "lets not get involved in office politics" mindset.

Apparently, the good workers who arent besties with the founders or CTO dont get recognized for any promotions.

My social life consists of spending much of my free time with my girlfriend, seeing my close family on weekends and meeting with a few friends from time to time.

It's enough for me and since there's not much of it, it isn't hard to "balance". Whatever that means.

Seriously tho, "social/work life balance" is subjective. It depends on what you need to feel good and happy. What works for some will not work for others. Don't try to push others into being social when they don't want to. Don't give me that "you need to go out more" crap. I don't. I'm fine just like this. I prefer to stay home and see a movie with my girlfriend.

That "people need to be social" mindset made me feel bad about myself for too long because I'm just not like that and people keep pushing that idea into my head. I'll go out with you when I feel like it, don't push it. Stop asking me every fucking weekend ffs.

- was a manager of a super market
- got tired of walking to tills to give discount
- taught myself to code
- wrote a loyalty card system that automated the discount
- met an investor with a similar mindset and rolled it out nationally (after it was professionally refactored).

This was my "last job" starting in like 2009 not my current.

So I'm at that age of arranged marriage process. It's kinda like dating but even more complicated with more if conditions on religion, caste, region, age and impressions of a third person who may be a mutual relative or acquaintance. And yeah, you have to engage or marry before any kind of intimacy.

Finding a girl of same religion, caste and region is hard enough, ( not a matter for me personally, but it's a factor for families to go along ). I was lucky enough to find this pretty nice girl that seems be the best match I have received in the matrimony site so far.

She's also a programmer which is awesome and together we could also explore the earth as a Digital Nomad if she's also into that.

Here's the deal though, my father is not very keen on next steps in making this partnership ( guys parent calling girls family to know things better ) because apparently she did higher education abroad and works abroad, and I'm not that qualified in terms of education. And on top of that, he worries I'll move abroad leaving everything back at home.

I suppose that's his insecurity showing up.

He doesn't realize working in IT is the most flexible job as proved in 2020 and it's only going to get better in the coming years. We could work from anywhere with the right remote company.

Anyhow, the girl's family found out my number and reached out to me directly. I'm pretty impressed honestly.

I had left little traces on the internet for potential families to find more info about me if they choose to look me up! This was in a way a little filter of my own. Thanks to Google Analytics and Seach Console for helping me to track them XD

I just hope this works out and my father won't mess up my chance for me to get to know this girl better and potentially be with the life partner I dreamed of.

If this won't work out, I'm just gonna live alone rest of my life. The criterias and conditions set by boomers for arranged marriage are very disgusting for my modern mindset.

I changed "Bug" in TFS to "Monstrous Hideous Defect". That'll get the mindset right. The word bug is so common that nobody cares anymore. New Monstrous Hideous Defect? Holy crap, better fix that right away! 😃

Have a positive mindset. If the work in general sucks, you can almost always find some micro or nano task that you can focus on. Then you find something more fun to work with and switch job. But until then, stay positive and be happy. And use devrant to blow off steam.

I am thinking about leaving this platform. To be honest I don't get anything out of it anymore and the only thing keeping me here is the less-rant'ish content like @devNews or the stories.

I am actually a bit disappointed, the quality of devrant really did degrade alot in the last few months. Don't get me wrong but I feel like people have become "normies" over here. I don't mean that in an edgy or degrading way but let me explain. When I started here I had a very high opinion of the people here. Everyone seemed like a passionate / knowledgeable individual from whom you could hear interesting stories or learn. Maybe I just saw it like that because I was still a very inexperienced dev and was looking for a dev community. But nonetheless I think devRant transformed into a place of mediocrity.

Dont get me wrong I wouldn't think of myself as aspiring or generally "better" than anyone else on here, but the content over here got a little stale.

I am not the kind of person who would "rant", in the first place, so I may have a different mindset and to be honest "ranting" has always been a thing I looked down upon. It just does not support my style of thinking. I totally get that people sometimes need to "vent" their feelings but there is nothing productive to gain from ranting, like you ain't not improving your situation by doing it. The more passionate raters over here call people things, I would never even dream about saying to people. Don't worry I'm no sjw or something like it, I don't care if you do it. If it helps you sure, why not. But there is a point where you corner yourself so much that you stop respecting your colleagues because they wrote that shitty code, instead of helping.

Some tech sure is bad, but it is not getting any better by insulting it.

Another thing I use to notice are people, thinking so highly of them selfes / being so close-minded - that they only accept their own views as true. These are the people that I always try to avoid, but that is getting harder and harder as time goes on.

Collectivism and group thinking are very strong on devRant making it really hard to defend a unpopular opinion - I get that devRant is not the kind of platform that would support actual proper arguments/discussions - but I still feels like some people shove opinions down another people's throat with no reasoning behind it.

Arguments on devRant are always won by the person coming up with the most witty response. Having another opinion is always seen as offensive. That's not exactly the definiton of open-mindedness.

Another rather annoying thing are what I call the "non dev, dev's". See: As a developer you should aspire to understand what your doing - I won't get into this too much but one sentencd: How are things like serious "Semicolon memes" a thing? I am as much into memes as the next guy, but debugging 3 hours, just to find out its a typo. I mean come on...

I sure get that devRant is not the kind of place where you would find the people I am looking for, and that's why I am leaving.

My whole post may seem super negative of the platform - and it is to an extend - but I sure also had a good time back in the day - devRant as in "the platform" surely is not at fault, but a forum is only as good as the people on it. Maybe I changed, maybe devRant did. All I know is that it is not for me anymore.

I won't delete my account and I probably will not leave completely, but all I will do is the "once a week" checkout.

It's oddly satisfying to see other devs rant about the shit they go through. And yet, I can't deal with the shit that people rant on non-dev related on Facebook.

computers are really expensive around here, so I've been using the same laptop for 6 years. a couple months ago it perished (rip).

me and my bf got all new parts and made a reasonably priced pc. it's been the first in a really long time that i enjoyed using a computer lol. it's a huge difference in my mindset knowing things won't take 3 min to load and that it won't crash every 2 secs

Sometime ago I was introduced to that game "Stardew Valley", as a way to relax and unwind since it is a dynamic-pace simple-storyline and even simpler interactivity open world.
Well, it worked like a charm (sarcasm). I have a save where I am a profit-maxinizing capitalist who tries to score a million gp in an year - so a regular gamer approach. It wasn't the goal here.
So I got a second save where I just go along, getting enough to get by and no hurry to build farm buildings and whatnot, but slowly building up NPC relationships.
Man, what a good metaphor for life. That approach actually unwinds me.

But the dev in me is just like "just, woah! that is an stellar use case for GPT+3 APIs! You could have NPCs with dynamic adaptative dialog! *And* you can monetize it (piracy-proof!) by charging for API calls! No shops, no collectibles, just a unique but scalable experience!"

What is wrong with me? I gotta change into the second-save mindset...

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.

Official declaration: I am a fucking moron.

Last year, I acted stupid (as suual) and didn't invest enough money into some tax saving instruments.

I also picked the wrong taxation method and ended up paying more than double taxes.

Thankfully my country has an option where you can claim a refund by filing a return form.

And so I go ahead and I hire a finance guy who can help me do my taxes.

We sit at the table and do the math. It turns out my savings mindset prevented me from not investing enough and now it is difficult to claim the tax as refund.

I legit had no issues in investing more. Rather I was looking for ways to do so but I didn't. If I had done it, I'd would be paying zero taxes as my earnings would fall below a certain threshold.

Only trick is to evade by unethical means. Should I be the Jeff Bezos of my country and save my hard earned money from going to corrupt politicians?

Either way, I am a moron. Fucking hate my stupid decision.

I was assigned to maintain the website as full stack dev but the code from backend is horrible previous devs didn't use SOLID principle, DRY, KISS, or Design patterns. I had to adjust from OOP mindset to Procedural its hard to debug in this state.

I can't stand talking to clients on the phone!

One of my first freelancing clients used to talk to me for an hour at a time. I really wish I could have billed him by the hour, it took him twice as long to explain anything and then I'd have to get back in the mindset for what I was working on. The phone is just so disruptive.

I'm so much happier working for a company where the project manager deals with the client's and product managers.

Things I’m learning from my accounting job that will help me in my future dev career:

Today I have really, truly understood the need to sometimes just walk away.
I couldn’t figure out how to fix something, I kept fucking up, and at 16:40 I realized I can just stop, do something else that’s easy and doable, and come back to the fucked up mess I made in the morning. We’ll see how it goes, but it’s a lesson I’ve been continuously learning over the last few years, not to stubbornly brute-force my way into doing something when I’m not in the right mindset and able to do it, and instead just calm myself down and come back to it later.

The job hunt is exhausting but trying to keep a positive mindset coz my prospects look good so far. Just cant wait to be done with the interviews (hopefully within the next two weeks) and get back to reading books and binging series when i am not working without the guilt of i should be studying and won’t forgive myself if I don’t pass due to laziness.
I also actually miss writing code and working on a team. Remote work made me realize I absolutely love being a software engineer, i just hated going to the office.
Pls send positive vibes for my upcoming interviews 🙏🏾

Spent 2+ months this year building two new software courses. They've netted me a total of... $17.00

That's 5 cents per hour at 40/hours a week, not bad!!!!

also please fucking tell me how a $49.99 course with 92 enrollments this month earns me a grand total of $93 (even rounding up here for generosity)

creator: $93
udemy: $4506

udemy: "instructor gets 37% of comissions"

yeah okay then where is my fucking $1000+

I mean what in the literal FUCK is going on here

better put: i average a single fucking dollar for each $50 course I sell?

Please kill me and end it all in this mindless race to the bottom

taking a deep dive on this revenue share and then i'm going to fucking get the money i deserve

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.

Proudest bug squash? Probably the time I fixed a few bugs by accident when I was just trying to clean up an ex-coworker's messy code.

So I used to work with a guy who was not a very good programmer. It's hard to explain exactly why other than to say that he never really grew out of the college mindset. He never really learned the importance of critical thinking and problem-solving. He did everything "by the book" to a point where if he ran into an issue that had no textbook solution, he would spin his wheels for weeks while constantly lying to us about his progress until one of us would finally notice and take the problem off his plate. His code was technically functional, but still very bad.

Quick Background: Our team is responsible for deploying and maintaining cloud resources in AWS and Azure. We do this with Terraform, a domain-specific language that lets us define all our infrastructure as code and automate everything.

After he left, I took on the work to modify some of the Terraform code he'd written. In the process, I discovered what I like to call "The Übervariable", a map of at least 80 items, many of them completely unrelated to each other, which were all referenced exactly once in his code and never modified. Basically it was a dynamic collection variable holding 80+ constants. Some of these constants were only used in mathematical expressions with multiple other constants from the same data structure, resulting in a new value that would also be a constant. Some of the constants were identical values that could never possibly differ, but were still stored as separate values in the map.

After I made the modification I was supposed to make, I decided I was so bothered by his shitty code that I would spend some extra time fixing and optimizing it. The end result: one week of work, 800 lines of code deleted, 30 lines added, and a massive increase in efficiency. I deleted the Übervariable and hardcoded most of the values it contained since there was no possible reason for any of them to change in the future. In the process, I accidentally fixed three bugs that had been printing ominous-sounding warnings to the console whenever the code was run.

I have a lot of stories about this guy. I should post some more of them eventually.

I had the oppertunity to join a non profit organization to help them automate stuff instead of serving the army. One of their core applications got rewritten like a year ago from a terrible and very old Symfony stack to Laravel / React.

The guys who were in charge for the rewrite didn't really adapt the mindset of either MVC for Laravel nor the component idea behind React. There are a few controllers in the backend, but they sometimes have functions defined which would clearly belong in a model or service class. They rarely defined relationships on models, instead they're joining the tables together for the same effect. The frontend rendering mostly happens in for loops over the returned array from the API instead of breaking things down into little components. This ends in components which have sometimes over 1000 lines with super-nested logic in it.

But I did find my favorite piece of code today in of the controllers. Some many questions ...

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?

If they followed my suggestion and went straight to debugging the server issues they would have been solved it from week 1 and everyone would have thought the migration had a minor performance hiccup. In fact, we have already done such at least twice before and nobody batted an eye.

Instead they self-labelled the migration a failure on first error, setting the stage for apologizing to the client, and put themselves on the spot for a whole staging / production signoff, replication / backup worfklow, almost a blue-green "seamless" deployment reminiscent of DigitalOcean.

Well they're not DigitalOcean, and anyone who has spent any time understanding users knows they will not participate in "new system" tests long enough to find or report issues.

So of course the migration stretched out to almost three months up until the whole reason for the migration - the rapidly escalating risk of the old provider disappearing - hit like a freight train and now they have to go through the problem of debugging the server like I told them to on week 1. Only this time they've set the client mindset against it, lost any chance of reverting, have had grave risk for data loss, and are under pressure to debug other people's code in real-time.

This is why I don't trust devs to do ops. A dev's first solution to any problem is to throw tech at it.

Once a guru of mine told me,
"A developer is one who can convert his/her ideas to code and doesn't need to depend on external libraries to help him/her"

His words actually have made me a different person. I mean since that day, I actually started developing things on my own. Until then I was hardly good at coding. Wasn't even clear with the basics. But those words of his had a deep impact on me.

Today I suddenly started thinking about that and honestly, I'm so glad to have met him. I'm so glad that he actually said the above thing to me.
Today, I'm at a position where I can legit build anything I want.
From websites to bots, I make my ideas come to life. All thanks to my guru.

Just thought this might be a good thing to share to motivate others. If it motivated me, I'm sure it might motivate atleast one other person in this community.

Reactive Java.

I actually rather like it, I really do. But the shift in mindset required, and the limited advantages (especially with fibres under heavy development) both mean I think it's incredibly unlikely to last.

Encapsulate tasks
To abstract your case,
Full of the catharsis
And exceptions to face.

Didn't commit, oh wait,
More trouble? One reset.
We return and all hail
This programming mindset!

"My code" only exists when you work alone on your precious project. Do not carry over that mindset when you work with a team or you will just ignite another endless holy war

!rant

so the other day i was programming and suddenly i wanted to learn haskell. (i don't know why it hit me so suddenly, maybe because it's a 'pure' functional programming language and these 2 terms i knew nothing about)

and to be honest it's really hard coming from an imperative programming language (C/C++, yes, i know they are different in their ways). it's like learning to program again! you really have to get a different mindset and for me honestly it's hard to grasp the idea that 'variables' are immutable! like, that's soooo weird it still stucks to me. for example how did they define the max or min function without using a while loop? what are monads?

I am just 2 days in but it'll be a fun ride!

In the US, 40% of unsheltered homeless people are employed, either part-time or full-time. “JuSt fInD a jOb” mindset is wrong.

Why is it that virtually all new languages in the last 25 years or so have a C-like syntax?

- Java wanted to sort-of knock off C++.
- C# wanted to be Java but on Microsoft's proprietary stack instead of SUN's (now Oracle's).
- Several other languages such as Vala, Scala, Swift, etc. do only careful evolution, seemingly so as to not alienate the devs used to previous C-like languages.
- Not to speak of everyone's favourite enemy, JavaScript…
- Then there is ReasonML which is basically an alternate, more C-like, syntax for OCaml, and is then compiled to JavaScript.

Now we're slowly arriving at the meat of this rant: back when I started university, the first semester programming lecture used Scheme, and provided a fine introduction to (functional) programming. Scheme, like other variants of Lisp, is a fine language, very flexible, code is data, data is code, but you get somewhat lost in a sea of parentheses, probably worse than the C-like languages' salad of curly braces. But it was a refreshing change from the likes of C, C++, and Java in terms of approach.

But the real enlightenment came when I read through Okasaki's paper on purely functional data structures. The author uses Standard ML in the paper, and after the initial shock (because it's different than most everything else I had seen), and getting used to the notation, I loved the crisp clarity it brings with almost no ceremony at all!

After looking around a bit, I found that nobody seems to use SML anymore, but there are viable alternatives, depending on your taste:

- Pragmatic programmers can use OCaml, which has immutability by default, and tries to guide the programmer to a functional programming mindset, but can accommodate imperative constructs easily when necessary.
- F# was born as OCaml on .NET but has now evolved into its own great thing with many upsides and very few downsides; I recommend every C# developer should give it a try.
- Somewhat more extreme is Haskell, with its ideology of pure functions and lazy evaluation that makes introducing side effects, I/O, and other imperative constructs rather a pain in the arse, and not quite my piece of cake, but learning it can still help you be a better programmer in whatever language you use on a day-to-day basis.

Anyway, the point is that after working with several of these languages developed out of the original Meta Language, it baffles me how anyone can be happy being a curly-braces-language developer without craving something more succinct and to-the-point. Especially when it comes to JavaScript: all the above mentioned ML-like languages can be compiled to JavaScript, so developing directly in JavaScript should hardly be a necessity.

Obviously these curly-braces languages will still be needed for a long time coming, legacy systems and all—just look at COBOL—, but my point stands.

I find it very strange and telling when people tell me that a dev shouldn't "re-invent the wheel", "roll your own" or "leave it to the experts" while simultaneously promoting substandard own-rolled projects by other people that simply got popular.

Kind of a strange elitist double standard that encourages a bad mindset of "I can't be as good as them" and it's toxic.

If you wanna make your own framework / package / etc, just do it, it might even be better.

Lately I stopped being angry at work, maybe because I am already in a “notice mindset”. Tomorrow after my job I have a meeting in another company and I should get an offer for another job. Leaving web development to do some C hardware development.

Otherwise tomorrow I will write the biggest rant ever or I will cry or maybe both.

Hey guys and girls,

follow up rant on my apprenticeship situation. I talked to Jo (my trainer). I told him I need more supervision and either someone who teaches me the stuff I need to know to meet the requirements from Hugo (my department mananger) or some further education. Because otherwise I'm not able to write producion ready code. (Keep in mind: I'm a fucking trainee who started their apprenticeship 6 months ago!)
Jo is more than happy to help me and make sure I'll get everything i need. Sadly he has to speak with Hugo and get his ok.
Hugo thinks 2 das of school/week is enough training. (Regardless of the fact that we don't even learn the same languages there we use in our projects.) I told him that way I won't be able to finish my projects.
I hope he reconsiders. How should I learn if nobody's there to teach me? (My collegues are to occupied fixing bugs and implementing new features/ don't know the languages either.)

If Hugo keeps this mindset I have to contact the IHK (a german institution which keeps an eye on apprenticeships).

Imagine a world that only consists of humans with a developer mindset . Would it be a better or worse world?

Aside from all the food and production problems, let's say we automated it all.

So saw some new cool technology/library (vue 2.0) and suddenly I feel like my codes are rubbish and outdated. major urge to rewrite months worth of codes. Is this self-suicidal mindset normal? please share.

I spent the whole day on git conflicts, I know it happens sometimes. But I do feel like a slow programmer, the boss even said so by comparing me to someone who has 15 years experience by saying I produce less lines of code than than him ( I have 5 years of experience).

So everyday, I have this nagging thoughts; "you are too slow, you can't even program, what are you doing, do something else this isn't for you etc" .

And then when I solve the problem "You are the best, you know everything etc"

A constant battle between self-destructive and positive thoughts.

Today I had a casual chat with my friend and we were discussing how human mind limits the things one can achieve. Like giving up after constant failures, or lack of determination, blaming destiny for failures. I told him I am never easy about the fact that your destiny is pre-written and you can't do anything about it. If you are willing, you can change it. You just need to have the right mindset.
He said I am going to do MBA after engineering. You can't be rich with just engineering. I told him if you work smart and hard enough, and just follow your passion, there is no need for an MBA. And he went on to tell me how top richest persons mostly comprise of businessmen.

I fear for the future. People like this with no goals when take up engineering, they blame everyone but themselves and the stream gets the bad name. People want money, but they don't want to work from the beginning. Even after that they give up too easy.

People like Bill and Mark were not pre-destined. They made themselves. They were just like us, but they never got satisfied with themselves. We all have the capabilities to be them or even better. We just need to keep driving ourselves until we reach there, we don't have to get satisfied. We have to keep improving and learn from our mistakes, then try again.

!dev

I have this urge to get better at coding and software architecture and design. But fuck me if I'm not lazy about it.
All these crazy good books and lectures and here I am, doing jackshit to improve. Can't even finish my own personal projects. Bah.

I know how I'm supposed to go about it, how to keep engaged in a cycle of personal betterment. I lack self-discipline to do it though... Tried meditation for a time, but haven't really stuck to it. Currently trying to follow stoics (Seneca, Marcus Aurelius and some others), but the mindset is not so easy to adopt, and the practical philosophies even harder.

Oh well. Life is hard. Blah-blah-blah. Thanks for reading. Just wanted to vent, really.

"Startup" mindset is invented only to rip off hardworking people, lower your wages, working 16 hrs with no apparent reason, hectic environment to hype mentioned things which is mearely show for the fools. As if people weren't starting up companies centuries ago.

I absolutely hate software to the point where I started converting from sysadmin to becoming more like a dev. That way I could just write my own implementations at will. Easier said than done, that's for sure. And it goes both ways.

I think that in order to be a good dev, you need these skills the most:
- Problem solving skills
- Creativity, you're making stuff
- Logical reasoning
- Connecting the dots
- Reading complex documentation
- Breaking down said documentation
- A strong desire to create order and patterns
- ...

If you don't have the above, you may still be able to become a dev.. but it would be harder for sure, and in some cases acceptance will be lower (seriously, learn to Google!)

One thing I don't think you need in development is mathematics. Sure there's a correlation between it and logic reasoning, but you're not solving big mathematical monsters here. At most you'd probably be dealing with arrays and loops (well.. program logic).

Also, written and spoken English! The language of the internet must be known. If it's not your first language, learn it. All the good (and crucial) documentation out there is in English after all.

One final thing would be security in my opinion, since you're releasing your application to the internet and may even run certain services, and deal with a lot of user data. Making those things secure takes some effort and knowledge on security, but it's so worth it. At the most basic level, it requires a certain mindset: "how would I break this thing I just made?"

I work remotely for a team that works together in an office, and this morning on the conference call a team member said

"one thing i think we need to do with this is stay on task, because while these things that have been added are cool we don't need to be doing anything not outlined in the MVC requirements"

Okay first of all -- this is a completely foreign technology to this team. It's not like I diddled around adding fancy animations and no function. The problem working in a new technology with an old mindset is assuming that it's going to move linearly from step 1 to step 2. And that drives me fucking insane.

- Progress in paid contracted work is done by staying on task.

- Progress in research isn't done linearly. You have to try shit -- and figure out what doesn't work.

I feel bad because I'll chime in and shoot down ideas with a fucking guided missile because I know the answer and I've done the fucking research -- I'm not a dick about it, but replying with a simple "no that's not possible, because of this or that", the call becomes silent for 30 seconds because I've shattered their understanding of the technology because nobody has taken the time to understand anything about how this thing works!!

So until they either listen to me, ask me, or learn the smallest amount to get on my fucking level, I'll keep progressing -- because whether the old world idealists like it or not -- that's my job.

Progress.

</ rant>

I think the one of the more common reason for imposter syndrome is that a lot of smart people constantly get told as children the "you're so smart/capable, you can do everything!" too much, and when you hear it enough times, it gets to you, so you think everything is just easy. And then when they start hitting roadblocks, instead of helping or explaining that it's normal for things to be hard and it's normal to fail, usually parents and teachers and whatnot tell them "Oh it's okay, don't worry about it, you're smart, you'll get it" and so they at first it works, maybe it just takes more time but they manage, but as things get harder and they still put little effort because "don't worry, you're so smart, you learn so fast/easy" and as they find out more and more things they don't umderstand or don't know they start to feel a dissonance, which builds anxiety.
And this is where I thinks it actually starts: at some points there comes a situation where they either share this anxiety with someone or someone notices their worry, and(at least from what I've seen from others) usually the response they get is something along the lines of: "Nah, you're just worrying too much, you're smarter than you think, don't be so down on yourself, you need to worry less", which, maybe I'm wrong, but I'm not sure telling someone that thinks he has a problem that he doesn't have a problem, helps their worrying.
And on one hand the amount if things they don't get/know/understand or fail at grows(cuz you can't just be good at EVERYTHING, so the more things you know about, the more things you don't understand) while mentally still being in that "Wait a minute, you're smarter than this, you should be getting this!" mindset that's been drilled into them, and so at some point the illusion shatters, and they start to think "Maybe I'm not so smart after all", and because they think they were wrong about their level, they feel like they have "oversold" themselves in the past and that makes any past accomplishments feel like lucky accidents instead: "If I'm not actually smart, the things I did manage to achieve must've been just accidental", which makes them feel like they've lied to themselves and everyone else when they "took credit for an accidents" and that their life is just a snowball of pretending.

Now, is that actually a cause or is it another one of my crazy 1AM ramblings? I don't know xD
I'm not an expert in any of this and I don't really know any psychology so hell if I know if that's how any of this works but that's just my theory of one of the reasons why. *shrug*. I've had this theory for years, but I don't know.
It at least makes sense to me, but not everything that makes sense is true soooo.

Anyways, wall of text is over.

Oh, and for anyone struggling with imposter syndrome: I just want you to know, it's okay to fail, and it's okay to not know shit, especially in the dev industry where every "insignificant" detail can have an entire rabbit hole of expertise behind it, nobody can expect to know every part of it. And it doesn't make you any less smart no matter how much you fail. Tnis shit is hard, so I hope you stay strong and I hope you succeed in whatever it is you're struggling with.
*Massive virtual hug* <3

"The show must go on"
Cool mindset

Yo guys, all the ranting aside, I just wanted to remind you that you ALWAYS have a choice, that you should speak up when something bothers you for too long and that you should be aware about all your strengths and unique skills! Just as a reminder ✌️

I wonder what the average lifespan is of a developer.
Is it higher or lower then the average life expectancy?
Does it have to do with our mindset? Or are our clients so terrible that we have more stress? If so does devRant lower our stress?

Seriously, does anyone really use TDD? It sound good in theory, but generally the devs are already used to implementation-first and are not willing/disciplined enough to change their mindset.
I think the biggest disadvantage of TDD is not taking into account how freaking lazy developers are in general.
Or maybe I just wasn't willing enough to make the change.
Thoughts?

How do you turn off work mode when you clock out of your job?

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.

Decided to get myself a new phone as the 2013 model is getting morally obsolete. I can still flash Lineage/Android10 and it will run it. But the apps (e.g. Google Maps) nowadays are such a performance hog it can't cope.
So I've searched through gsmarena, prioritizing smaller phones, picked myself a candidate and had it on my desk after few days.
The 2013 mindset still the same "do the backup before touching the phone in any way". How do you do backup? Unlock bootloader, boot/flash TWRP, run backup.
I've realized only after the unlocking and some googling, that the unlock automatically deletes TA partition and stored DRM keys. So advanced licensed features of the phone are gone. Also there is no way to lock the bootloader again, so I've lost the SafetyNet validation too.

tl;dr: I've fucked up my new phone as a first step after I got it.

I need help and advice!

I currently work as an consultant at a large corporation. Came onboard for 1-2 years to help rebuild one of their platforms. From the beginning the mindset was that the finished product should not be developed based on anything else than customer testimonials and interviews regarding functionality and design. However, they’re building their platform developed and distributed by this other company. Basically they bought a system that is incomplete regarding to being compliant to the specifications brought to them when they decided which system to go with. Now we’re trying to build around all the issue this platform is causing us. The code base for the system is like something a monkey did with their feet. Nothing makes sense and it’s layers on top of layers of 10 year old code. I f-ing hate it. I don’t know what to do. We have some many technical limitation that it’s impossible to create the vision they had from the start.
I’ve been thinking about talking to the highest chief in the department as he has been pissed earlier about project managers not escalating issue to him earlier. But I don’t want to step on anyones toes. Should I leave the project? Should I talk to the chief? What do I do? I’m miserable🤯

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)/

Do you sometimes get into the mindset of considering the GitLab Contributors tab as some sort of scoreboard?

Utterly nonsensical of course, but I feel a youth full of videogames has somewhat trained me in that regard.

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?

Manager: ...

fullstackclown🤡: you are an absolute idiot

Manager: ...

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.

Being a Mobile Developer and seeing corporate companies stuck in a mindset of Web Development. Analytics using Breadcrumb trails. oh, okay then. Makes sense.

Current boss is best boss.

Seriously though, he's a great guy. He has a lot of knowledge technology-wise, especially in electronics and will explain things to you without tiring if you don't understand them.

He lets me run my thing which is cool and letting me run too freely/not taking enough time is probably the only thing I'd criticize.

He seems to have a similar mindset to mine which makes it (most times) enjoyable to work with him. I like him personally - though I'm sometimes not sure whether he gets my somewhat weird humour.

I think I joined the wrong crowd. After the recent Hackathon, I proposed that the team that I was working with, form a company in which we continue building apps, launch and try to profit. Y'know, the whole build fast and die slow kind of thing. Granted, I proposed it late November and we're all gearing up for the holidays. Now its January and everyone has this mindset of "if we don't meet, we don't get anything done" or "discuss face to face only". Guess they don't like the idea of working remotely.

I think I might just quit this venture after a couple of meetings with them before I lose my mind.

Coaches know: it's all about the mindset!
Runtime exception? Mindset!
No video in Teams? Mindeset!
Money got stolen? Mindset!

I have realized that I'm getting nowhere with my boss with my current attitude.

I want to change strategy, but I find it very hard to bite down my tongue and give up on being logical or the attitude of "be competent, do a good job, or gtfo of my way". Like, it's not my place to fix all the issues, neither am I perfect.

I'm not looking for methods of manipulating him, rather I want to change my own perspective and mindset to something that doesn't make me suffer. At least regarding this one person.

How do you mentally check out and stop caring at a toxic job?

Been at this big fintech for 4 months. Small teams, impossible deadlines, undefined tasks, missing specs, constant context switching. Everyone's doing overtime/weekends while management sets you up to fail then blames you. Performance evaluations every 3 months.

Was literally about to quit tomorrow but need the paycheck. So I'm turning this into an experiment - I'm a recovering people-pleaser who's never set boundaries at work. 9 years in my career, never been fired, I left multiple times due to burnout in the past.

Time to see what happens when I stop caring about pleasing incompetent managers and their made-up deadlines. Work at my own pace until they get tired of me. How do you actually do this though?

- How to not give into false sense of urgency induced stress?
- Ask for proper specs without feeling guilty?
- Work slower and not hate yourself for it?
- Push back on unrealistic expectations?

I'm burned out and need to learn how to be strategically as mediocre as possible for my own sanity.

Anyone been through this mindset shift?

If I had a dev superpower, it'd be to put myself in the exact mindset of the author of the code I read, at will, so even the comments that never got written would be understood.

I would learn so much, about code && people!

Changing fron a sysadmim problem solving mindset to a developer' algorithm-oriented mindset

Praying to every deity, I begged to spare me, to never kill my inner child. To never make me grow up into materialistic mindset that punishes curiosity and denies miracles.
It seems like my wish was granted. Am I naive? Sure. Do I have kid ego? Sometimes.
But I never wanted to be someone else.

I'm going to confess: I am the type of developer that creates the ExcruciatinglyLongAndSpecificClassNameObject with the UtterlyDetailedExplanationMethod. It's just a thing I keep doing, despite voiced frustrations from people I've worked with. It just feels right in the mindset of self-documenting code

And while I acknowledge this isn't a flawless process, I see no other way around without losing information. I've tried alternatives, but everything feels like trading one issue for another:

- Abbreviations work as long as they are well known (XML, HTML, ...). As soon as you add your own (even if they make sense in the business context) you can bet your ass someone is going to have no idea what you're talking about. Even remembering your own shit is difficult after X months.

- Removing redundant naming seems fine until it isn't redundant anymore (like when a feature with similar traits gets added). and you can bet your ass no-one is going to refactor the existing part to specify how it differs from the newly added stuff.

- Moving details to namespaces is IMO just moving the problem and pretending it doesn't exist. Also have had folks that just auto-include namespaces in VS without looking if they need the class from namespaceA or namespaceB and then proceed to complain why it doesn't compile.

So, since I am out of ideas, I'd like to ask you folks: Is it possible to reduce class/method name lengths without losing information? Or is self-documenting code just an ideal I'm trying too hard to achieve? Or are long names not a problem at all? I'm looking forward to your answers.

I work at a research institute (part of probably the largest research body in whole Europe). And it's driving me nuts. Forget about the lack of interest to improve yourself in terms of software skills or basic digital hygiene so that others don't have to pick up the mop and clean after you. The ancient mindset is what is making me curse everyday. Only a few years ago we switched to GitLab. Before that versioning, if at all a known term, was done explicitly via email messages - code snippets in the message's body, versions in the subject of message attachments...A freaking nightmare. Constantly broken links to files and folders on our NAS since some people have never heard of relative paths or writing even the tiniest bit of support for configuration files in their software so that a tool does not completely brake the moment you transfer it onto another system or - God forbid - the person leaves and there is no information whatsoever what's where. Everyone is complaining about the clutter on our servers but no one is willing to actually clean their own (not someone else's) crap. If you mention to someone something like "Can you please pack your stuff in this GitLab repo with this folder structure, so that I have an easier time integrating it into the main software that we need to ship to our customers in a few days?" all you get as a response is a blank facial expression and the occasional "I have my own processes. Don't bother me with this!". I have been trying for almost 4 years now and its budging a little bit but the lack of support is abysmal. My boss, as enthusiastic as it is, is incapable of putting his foot down. The fact that I have two heads of my team (one not really but acting like it) does not improve the situation at all especially since both are pulling in a completely different direction. We are literally wasting hundreds of thousands of euros of taxpayers' money to buy new hardware that people are either inadequate to use to its fullest potential (think buying the latest GPU to play Minesweeper) or not having even the smallest clue on what they need it for. And we are always complaining about our budget! You don't invest a couple of hours to investigate how PyTorch can work in a distributed manner on multiple CPUs, GPUs and even systems, yet demand you get a new server for 80K with a more powerful GPU and CPU to run your crap models on so that you can publish a half-ass paper that nobody cares for let alone will ever bother reading (beside the AI reviewers).

Hi fellow ranters,
Its been awhile since I last was here posting stuff..

So, I've commited to my effords getting shit done in golang. And I met a lot of painpoints, and I mean...
A
Lot
Of
Them.

Anyway, most of them are solvable by changing mindset or having some macros set up for no-one-fucking-wanted bloody boilerplate code that is omnipresent fucking EVERYWHERE.. **cough**
Steering back on what I want to rant about.

We with our team have one major problem with golang. There is no standard for docs in code...
Like, Fing legit. Everyone uses notation for closest to theirs heart language, so you get inconsistent-as-fuck notations for parameters / function descriptions.

We have functions that look like
//doSth does something
and also
// doSth
// @Summary does sth
// @Description does something but in more words
// @Param
and so on and so on

And trust me Im getting mild example.

Why this language does not have A F...ING (well defined, using proper definitions) STANDARD YET?

EDIT:
bonus context: We decided that too much of our code is undocumented and we go through efford of documenting it, but everyone sees it differently, and we can't agree on one single standard... So we decided to not refuse PRs due standard, as well, nobody would ever had PR accepted

Most probably the short time pressure and the mindset of "in these x hours/days, I can't do/think/be interested in anything else but the hackathon". It feels like it significantly disrupts my daily flow

How do you shift your sad mood to productive mindset?

Wk88 i basically see "I'm a beta that belittles myself, because everybody else seems to be so much better than me.."

While I certainly know how it feels, that mantra & mindset will lead to void or null.

It's a self-fulfilling prophecy and life's a bitch that'll keep ya down if you let it.

It's gonna be rough, but ye gotta stop calling yourself inadequate and start working on honing your skills.

No great feat happens over night, it takes practice and dedication.

I wonder if people would still post pics on Instagram if Instagram hid the number of likes..
I wonder if people would still buy branded clothes if every item of all the brands both big and small were sold at same rate..
I wonder if people would still pursue their current career (jobs) if all the jobs in the world gave equal wages to every employee..
I wonder if people would still donate if they were not allowed to tell anyone about it or post their contribution on social media..
I wonder if people would still by fairness creams and stuff if we removed the mindset of superiority of whiter tones over the darker ones..
Sometimes , i just wonder...

After 30 years, some developers are still struggling to build websites efficiently. Our hypothesis is that this is due to severe and acute ignorance and due to taking an academic backend-focused software engineering mindset to the frontend without even trying to understand what web design and frontend web development has to offer and why.

The worst part of getting ghosted or a rejection letter is that a scarcity mindset slowly build into you and there’s not much you can do about it.

Seeing success stories from others helps to boost morale a bit, but.. fuck!

What happens as you accrue years of experience is, you feel as if you learned a lot, actually its yes and no, yes because working in an environment with deadlines teaches things, no because the tech is changing.

The fact is tech is changing every few months if not year, one should be having a baby's curiosity to learn and adapt to the new practices.

When I started my tech career I was having a growth mindset, as I went on I felt somehow I got into a fixed mindset and got frustrated often. It's better late than never to realize that you may get wrong more often than right and learn to have an open mind when working.

Finally always take it easy on yourself, learn and move on.

Given an opportunity to develop an application for R&D. What do we do as a team? Let build it exactly the same way our current stack is built. (This app won't actually be used for anything useful, just an exercise for a fun R&D task)

It still amazes me with the number of developers that literally have the mindset, let's just do what we know & don't want to learn anything new.

Let's showcase new technologies? No. Let's create a serverless application? No. Let's create some microservices? No. Let's wrap the application in a Docker container so we can easily spin it up? No. Let's have multiple services that sit behind an API gateway? No. Let's for fucks sake at try a different design pattern? Why would we do that? Can we do anything differently? No.

No innovation, nothing - it just blows my mind. Everyone seems to think that the way the stack is built is how every application is. Sorry but a huge monolithic application that can't scale isn't how the other half live...

I don't know why the lack of wanting to try something new bothers be so much, but it does.

Had a real opportunity to showcase some cool tech, design patterns, new services in the cloud. Show not only other devs but upper management that there are alternative ways to develop. It's not like anything that I put together was "new or shiny" - I just wanted to do anything... Anything that isn't how currently do things.

Full disclosure, I'm not a great Dev - I'm pretty dam average but I'm always willing to try new techniques or approaches.

Brand new day, time to have a new mindset.
I need to finish the big project for the big boss, and fix things with my wife. Wish me luck fellas

Thinking of shaving my beard to remind my wife of when we first met so she will be tricked into loving me for the time being.

Anyone hit the pitfall of not following K.I.S.S.? I have found that programs that are really simple, I make complicated.
And then that mindset goes to the complicated programs no problem. But I stare at the program for a while, because I just know it can't be that simple, but it is.

!rant (kinda)

So I'm currently working on a personal project, where the concept is something, that if I wanted to, I could probably make a decent penny off of it.

The plan is to make it open source, and not charge anything for it, and when I tell this to non-dev people, they're almost shocked! Why would I not take an opportunity to make a lot of money!?

Well basically I think it's awesome to have open-source software, and I really want to "contribute to the society". And only after like 10 minutes, people start understanding my point, to just help people make something new, instead of being a greedy person, and keep it private, making it unavailable for a lot of people.

Hopefully I'm not the only one with this mindset?

Ok so first technical blog post/rant cuz I just reduced a lot of debt... Prolly gonna put this in an email to my boss (he says progress improvement is now a priority but there are some problems as listed below):

So last week, I spent a lot of time investigating db logs manually to figure out a prod issue: tiring, time consuming, and not very effective.

This week I built an app. It took a few days but having the time to design it correctly, it is very powerful.

So in order to really do process improvement, you need to have: dedicated the time, the problem solving mindset (the right people), and the understanding of what the problem is and why so you can build a good solution (time and people).

Figure I can simplify the code if I have the compiler handle *some* of the register allocation.

Eh? What do you mean "NP-hard"? Dafuq's an ENN-PEE?

**frantically reads wiki**

I can proudly say that I understood absolutely nothing; CS stands for cocksucker or rather abysmal failure at the most basic forms of communication, I don't just sit here all day expecting you to flawlessly prove my point with every swallow of breath you draw, yet here we are.

Perhaps one factor involved in producing the generalized cluelessness of my colleagues, I mean their "imposter s*ndrome", has a bit to do with how fucking thick you've formulated this glorified bollocks you call theory. Were not for your incompetence, arcane crackheads like me would simply __not__ be capable of rising to the top of this field entirely via determination and a big salami, therefore I owe you both a debt of gratitude as well as every last word and sign of total disrespect.

As interesting as the study of computational complexity can be, if done correctly that is, you idiots are stuck in a mathematician's abstract mindset in a field entirely devoted to application of ideas rather than *just* the ideas themselves.

To answer my own question, it means there's no known efficient solution. That's it. The part about nondeterministic polynomial convolution of an irreductible rectosigmoid junction can apparently be skipped altogether. Anyway, I solved the problem with the computational equivalent of pizza sticks while you were out in the field mentally jacking off to λ.

Lecture is over, now go clean up the ethereal masturbatory residue if you will, I have mystical el Khwarizmi type-shit to solve via further clubbing of abstraction through liverwurst bologna of immense proportions. ^D

For some reason I find reading tech books a repelling activity. I'd rather spend longer hours googling SO issues, GH/GL tickets, reading blogs than reading a well recommended book on the topic.

But then again.. What is the difference between a series of blog posts and a book...? Not much of it. At least I cannot come up with how blog posts would be superior to a structured and many times reviewed book :) Many posts are lame or just skim through the topic. The same holds true with books too. So maybe it's worth getting that 200pages thin book instead..

!rant

I am learning C# and devRant helps me keep my concentration and attention in check during the day. Helps me stay in the zone longer and interacting with a developer community helps me adopt a mindset which helps me absorb a different way of thinking which is crucial for somebody that comes from an "opposite" field - art and design. I would not have been able to have this community "in real life" otherwise.

+ You guys are soo nice, despite the ranting concept of the app :)

TL;DR: Computers and I go way back, but I don't know how I ended up as a dev - and am still not certain that's what I want to do for the rest of my life.

Rewind to the early 80's. My friends at the time got the Comodore 64 one after the other. I never got one. Heck, we didn't even have a color TV back then. Only a 12/14" small B&W TV. It's easy to conclude that I spent a lot of time at my friends'.

Back then it mostly was about the games. And, living in the rural countryside, the only way to aquire games was to pirate them. Pirating was big. Cassette tape swapping and floppy disk swapping was a big deal, and gamers contacted eachother via classifieds sections in newspapers and magazines. It was crazy.

Anyways. The thing about pirated games back then is that they often got a cracktro, trainer, intro or whatever you want to call them - made by the people who pirated the game. And I found them awesome. Sinus scrollers, 3D text, cool SID-tunes and whatnot. I was hooked.

My best friend and I eventually got tired of just gaming. We found Shoot'Em-Up Construction Kit, which was an easy point-and-click way to create our first little game. We looked into BASIC a bit. And we found a book at the library about C64 programming. It contained source code to create your own assembler, so we started on that. I never completed it, but my friend did.

Fast forward through some epic failure using an Amstrad CPC, an old 486 and hello mid 90's. My first Pentium, my first modem and hello Internet! I instantly fell in love with the Internet and the web. I was still in school, and had planned to enter the creative advertising business. Little did I know about the impact the web would have on the world.

I coded web pages for fun for some years. My first job was as a multimedia designer, and I eventually had to learn Lingo (Macromedia Director, anyone?) And Actionscript.

Now I haven't touched Flash for about 7 years. My experience has evolved back to pure web development. I'm not sure if that's where I will be in the future. I've learned that I certainly don't know how to do everything I want to do - but I have aquired the mindset to identify the tasks and find solutions to the problem.

I never had any affiliation with the pirate scene or the demo scene. But I still get a little tingling whenever I see one of those sinus scrollers.

I am having a shift of mindset, I learnt programming to create solutions that will make impacts in local communities - I live in Africa ... but lately, I just want to make money, alot of it.
I dont have any inspiration to continue any work for < SGD'S IMPACT PROJECT>. I plan to send my resignation letter to all.
I will probably just remodel/replicate another capilalist business model...
When I am rich enough, I can think about making an impact.

Ever since I started out in a programming job, I have always been a sole developer. I have worked in teams before but it was usually me being the mentor, despite my own knowledge being very limited.

However years ago I worked for a successful ecommerce business and it was the first time that I felt like a junior. At the time I was the type that never cared much about front-end and design. But the senior developers there had taught me how design of the website, and how we treat the customers is important. By making sure that we give them the best customer experience, they will come and shop again.

Although I still primarily focus on backend development, I still hold onto what they taught me. Even now at times I give my input to designers and project managers about design, UI/UX, and the customer experience. But more importantly bestow that mindset to my fellow developer co-workers.

I've not coded for quite some time but when people ask me to tell a story about my depression I write a code.

After reading mostly sad (and astonishing!) stories, I didn't really want to share my story.. but still, here I am, trying to contribute a wholesome story.

For me, this whole story started very early. I can't tell how old I was but I'm going to guess I was about 5 or 6, when my mom did websites for a small company, which basically consisted of her and.. that's it. She did pretty impressive stuff (for back then) and I was allowed to watch her do stuff sometimes.
Being also allowed to watch her play Sims and other games, my interest in computer science grew more and more and the wish to create "something that draws some windows on the screen and did stuff" became more real every day.

I started to read books about HTML, CSS and JS when I was around 10 or something. And I remember as it was yesterday: After finishing the HTML book I thought "Well that's easy. Why is this something people pay for?" - Then I started reading about CSS. I did not understand a single thing. Nothing made sense for me. I read the pages over and over again and I couldn't really make any sense of it (Mind you, I didn't have a computer back then, I just had a few hours a week on MOM-PC ^^)
But I really wanted to know how all this pretty-looking stuff worked and I tried to read it again around 1 year later. And I kid you not, it was a whole different book. It all made sense now. And I wrote my first markups with stylings and my dream became more and more reality. But there was one thing lacking. Back in the days, when there was no fancy CSS3. It was JavaScript. Long story short: It - again - made no fucken sense to me what the books told me.

Fast forward a few years, I was about 14. JavaScript was my fucken passion, I loved it. When I had no clue about CSS, I'd always ask my mom for tips. (Side story: These days it's the other way around, she asks me for tips. And it makes me unbelievably proud!)
But there was something missing. All this newschool canvas-stuff wasn't done back then and I wanted more. More possibilities, more performance, more everything.

Stuff begun to become wild. My stepdad (we didn't have the best connection) studied engineering back then, so he had to learn C. With him having this immensely thick book for C, I began to read it and got to know the language. I fell in love again. C was/is fucken awesome.
I made myself some calculators for physics and some other basic stuff and I had much fun using and learning it. I even did some game development, when I heard about people making C-coded games for PSP. Oh boy, the nights I spent in IRCs chatting with people about C, PSP-programming and all that good stuff, I'll never forget it - greatest time of my life!

But I got back to JS more and more and today I do it for money and I love it. I'll never forget my roots and my excurse into the C/C++ world and I'm proud to say, that I was able to more or less grow up with coding and the mindset that comes with it.

So I have a friend. One of few who I can freely speak with using my natural language (so that means, narrow down topics to IT, mix some of my native language, mix in lot of english and mixture of our favourite languages terms (don't ask me how it works, but it works brilantly and its actually easier to communicate)). And its true friend, seriously.

But when we meet, 80% of time we spent together, every, single, fucking time we argue (in cultural maner, its more of discussion) about what enviroment and what languages have advantages against others. And it pisses the fucking hell out of me, when he takes his enviroment, takes his problems with exac his enviroment, and applies his favourite solutions to it, and goes on how they are fucking awesome and brilliant, and than I reply, sure in my enviroment if I ever had XYZ problem, I wouldn't say use mongo DB becouse I can do it my way, and it would work well too, but it's not really the way I really should solve XYZ problem, becouse in my enviroment you dont have it in the first place. And he will fucking go on, but at least he understands my solutions and finds various details where HIS solution works better. His solution to his problem vs my solution to non-existant problem.

But that's actually an example of much grander thing that I want to rant about. You see, that's not all that bad, we keep it civil and we somewhat enjoy these discussions even if often times, they are pointless. It's like playing games and shit like that, so it's not the point, I just used the example to make it clear what I mean later down the line.

So, to the actual point. What the living fucking fuck is wrong with people, for living fucks sake they cannot physically, mentaly, virtually or otherwise change mindset and point of view if they are telling YOU what to fucking do, what's better to do, etc.
What the fuck! You have around 0.1% of context that is in my head, and my solution works with most of it and your bearly manages to deal with your given 0.1%, so kindly please for living hell, fuck off telling me what to do, what is better in my fucking situation etc. You don't know most of shit I know about my own situation (dosent apply to people with coma and heavy mental issues, sorry its not 100% universal) that I know, yet you have something in your brain that fucking allows you (dosent tell you "its no-go lol") to try push thru your shit to me like it was your fucking life. It's not.

And to be clear, before someone gets sad becouse I was to broad and generic. If you giving advice you can do it properly. And there are people who legit have mindset "well, if I was you and known what you told me, I would do XYZ", but for what the living fuck reason most of people I know have more mindset of "Do XYZ coz fuck you if you dont, coz dat is my opinion and shit and I dont give a living fuck if it does what you want"

Is it weird that I hold a high degree of respect for every sector in programming. When we talk about front-end, back-end in websites to the GUI support and logical end in desktop applications to cloud-based microservices, I respect clean, swift, and agile developers who who a structural mindset. For the founding fathers of assembly to high-programming languages like c all the way to high-high level programming languages like C#, JavaScript, Python, I respect them and thank them for their time and dedication in relatively stable libraries. I also thank the creators of OOP and FP as well as the developers that make great use of these paradigms. I come to realization that no one wants to fuck shit up; the great engineers of our past wanted to build some legit, non-trash programming tools, and we can't bash them for that. Respect, courteously critique, and build applications and programming tools to a standard that someone in the future would admire and be grateful for.

I am really having a hard time keeping an "open" mindset with my team...

So when I email you, the junior at your first job and an almost 6 months work experience, with a set of instructions, I do not want inline comments and feedback to the tune of "Yes, I agree. I think we should go ahead" or debates on why, in your opinion.. xyz, because you tested it yourself..

WHERE THE FUCK DID YOU SETUP AND TEST BILLIONS OF ROWS OF DATA ON YOUR MANY MANY MULTI BOX CLUSTER? You live in a data center? Oh, and say "Serverless" one more fucking time....

And so begins the painful process of performance managing you out the door. (You cant fire anybody in South Africa for being a prick. Or useless.)

I am sure there once was a time where you could beat guys like this to within an inch of his life with his own keyboard. If it wasn't wireless I could have strangled him with the cord. Ah, I miss model M's....

Unlimited time is impossible... But I don't wanna ramble.

The one thing that I absolutely miss in my kind of work is something that does exist in dozens of flavors and each existence promises to solve some thing...

It's "bug tracker" / "time management" / "ticket management" / "board" / "kanban" or what ever pervert method you prefer software.

I haven't seen a decent one.

I'd think I'd want to build one - it would be definitely an all time consuming effort, since I would be in dire need of specialists.

The thing with nearly all of the solutions is that they lack ... an associative mindset.

Simply put, what we humans can.

The longer a project exists, the more it's housekeeping (guess that's a better word for it) turns into maintenance nightmare.

I remember quite well the joy of puzzling together eg Jira / Bugzilla / ... complex search formulars trying to find the needle in a planet of hay.

If you're read so far and have had similar experiences, think about how nice it would be if you had a mixture of AI and BI doing exactly that.

BI / Business Intelligence to get meaningful statistics is possible, but without AI it's a lot of work.

The AI would need to do several things...

- Match information (eg version XY was released at XY, so each bugreport after XY belongs to version XY and higher if no version matched)

- Tag and categorize (crashed / faulted / fried / ... - tag crash)

- "do the mundane work": ask nicely if the marching / tagging and so on was right, ask for missing info, require feedback etc.

There's a lot I could write more about that topic. But that's the gist. ;)

Getting back into a development mindset after a vacation is damn hard to do.

I get anxious when I try to learn new things.

I'm not even sure how to describe it. Low self esteem? Low confidence? I dunno.

It feels like stage freight, but there's no audience or stage, it's just me and my computer.

No one really ever watches me, or judges me or anything.

I guess I'm a bit self emasculating because I don't really have a reason for feeling ashamed for trying out something in private.

But I feel that the fear, the stress is very distracting and it's limiting my progress.

Now, there's this project I'm rewriting in my company that I'm taking pride in and think that it has the potential to actually increase profits.

The stack is way better, it's visually better, the load times are better, the product is easier to access and try out, bla bla bla.

I guess I never felt truly proud of anything I've ever done in any company, most of what I did felt like grunt work.

But this one is actually a very well designed improvement.

So I'm hoping that this will be the excuse for not needing to prove myself anymore so that my mindset will be something like:

so what if I abandon another side project?
so what if I publish a game that looks like shit?

I may fail at newer projects, but I did win at that project I did in my company, and it wasn't a victory just because I say so, but also because my coworkers and bosses do too.

I don't know what else could help at this point.

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.

What to do when someone creates anger in me?
How do you guys deal?

I'm in college. Will it be useful in life later if I learn to swallow my anger? or Do I need to develop some mindset so I can't be affected by whatever anybody says to me or insults me.

One of my teachers scolded me in the examination hall because he didn't like my clothes. There were no rules regarding uniforms. I was not wearing revealing or torn clothes, just normal clothes.

I hate it when such things happen. It disturbs me. Even when the whole event is over, the whole thing plays in my mind again and again, sometimes for days.

Dev mindset

The customer wants to drop Agile in favor of their in-house development methodology. They just sent an e-mail describing it...
I think my team needs a room decorated with cotton flowers and small huts to get into the right mindset.

working to overcome decades of cultural and educational training (public schools and college lmao) of being an unquestioning slave who does what they're told

to actually think critically with a product mindset and question is missing from a specification

does anybody have tips

For me coding is a huge part of my mindset. I could be having a conversation with a gf and be debugging an issue in my head. I could wake up in the middle of the night and start coding an idea I had just thought of. Especially if I'm working on something I'm too excited about, I will work hours, days straight and not make time for much else. So I've phased through quite a few relationships this way (especially with normies) 🤷‍♂️ I almost feel like I'd have to be with someone as obsessed as I am for things to work out lol

working at an MNC is like dating the hottest girl in campus. everyone stares at you, but only you know of the tantrums and the expenses that you have to take.

Every random aunty and uncle I come across gets a wide smile on their face when i tell them my company's parent company name. i goto this temple , and there, one uncle was introducing me to his wife "meet X ji's son , he is at Y company" .
previously when i worked at a startup, most of the time , people were like "huh? what does this company do?" and when i would explain them how our DBs are sending billions of notifications and interaction each second, they would be like "oh , so you work at IT" , YES DUDE, YOU WANNA GIVE YOUR DAUGHTER'S HAND NOW?

And this mentality is sick. i loathe the place where i currently work. i loved my previous org and now am just here coz my mom is too scared to let her son live in a different state.

The only reason a person works in a company is money and WLB. Indian service based MNCs don't give a penny more than basic industry standards. and when they want their employees to be available 2 days a week + x number of days when any CEO , ED or other sugar daddy is coming to office, you get an idea of the shitty Work life balance.

my previous company was a b2b startup, it always paid me more than industry standards and we had wfh until a notification came to enforce hybrid working bh end of 2024. till now not a single person from my team has relocated. All i had to do was to *plan* for living in a state and my mom got cold feet :/

i think so much about my future. i earn decent, so i wanna spend it to live and grow.
i wanna go party at friday nights and go on night outs. i wanna meet this cute school crush at anytime after office and don't worry about the 9 pm curfew. i wanna go look for a new home in a different area and get out of this parking hellhole. i wanna prepare for exams and do a hugher studies from aborad.

everything needs money and growth mindset. money makes money and i am trying to earn every minute. but a chained mind cannot fly . a non growth mindset will not let you evolve. and someone needs to tell it to people who control my every . fucking. action

i have seen people switching from one big name to another. i personally feel that you are just too comfortable in the environment of big names and deliberately ignoring the smaller names which are doing the actual build fast and break reality stuff. reward is proportional to risk and if you are okay with just attributing to a big name, then that's on you

I crash and burn during coding interview questions. Every. Time.

I just do. It's terrible. It doesn't matter how much I tell myself to slow down and just think it through first before coding...I end up coding first after a short period of thinking about it. Don't get it right, freak out...and well I crash and burn.

It bums me out. The worst part is that I'm so distraught about it that I take a break, and sit down and solve it in like 10 minutes...of course it doesn't matter since it happens after the interview.

I just need to practice solving these things to get that mindset right.

Woke up early. Drank coffee and my mindset is so ready to do some work. After 30 minutes I'm so sleepy like a literal crash down and will sleep now. Body why you do this? I hate night shifts. It destroys my body clock. I hope weekends and mall hours are night shifts as well.

Also I hate company internal system project when I am assigned to a client and the client don't know that. I can't tell it to the client and my company can't tell also because my hours are 100% committed to the client.

I guess the moment I wanted to become a dev was when I was playing Skyrim and just got curious on what the underlying mechanics of the game looked like (and obviously how they worked). That lead to me embracing math (CS is derived from math and they both exercise logic flow and abstraction) and realized how good it felt solving problems. I get the same euphoric feeling from solving problems in mathematics as I do when I solve problems through code. I can say that I will be happy and have meaning developing software for the rest of my life, but I wouldn't lie and say that'll be my only focus. Along the way I'll definitely pursue other interest, but from my standing and mindset now I'll definitely be
developing things as more than just a hobby in the near future.

I feel like we we not only 'advanced' various fields by pulling people off some lord of the flies island who only wanted to dance around with a severed pig head in reality and training them, but also depleted and destroyed many essential fields by removing all valid motivators from our environment by spreading so much cynicism and unguided lust for power over others in the absence of any of the unifying beliefs of former generations that the professions are going to implode in the years to come.

so I wasn't very experienced when i went to work some place years back. I'd worked on my own. and I was criticized by their 80k per year team lead as having 'only done some simple things'... when his project didn't work, and par for the course their criticisms were coming from people who took a standard backend on a very large project that actually had been designed to function and something else likely needed fixed, to 'HEY LETS USE LINQ TO SQL APPARENTLY WITHOUT TESTING RELATIVE PERFORMANCE !!!!! AND WE'LL THROW SOME AD HOC QUERIES GENERATED BY MICROSOFT AT OUR SERVER INSTALLATION AND WATCH THE PERFORMANCE 'GAINS' THEN WE'LL BACKTRACK AND PUT STORED PROCEDURES BACK AND GENERATE HOOKS TO THEM LIKE A CLASSICAL DAL. JUST USING LINQ TO SQL'S CONTEXT OBJECT ! HURRAY I HAVE A BACHELORS AND 15 YEARS EXPERIENCE !'

There are so many details to fill in teaching the mindset of how to do things right in the first place is kind of expensive to begin with and you don't necessarily learn that in school working on common comp sci projects in academia. But they should have known better. I'm actually embarassed to list linq to sql on my resume as I think back.

> Your concern is entirely valid—naming can significantly affect how intuitive a concept feels. The term "object safe" in Rust might seem odd or even misleading if we approach it from a traditional object‑oriented perspective.

can rust please stop trying to be "different" for the sake of being different. Dumbest thing. Just call things what they are. What's the point of words if you're not actually accurately using them. Especially for a programming language, which is based on math and logical systems. Like how. Why. Stop. Antithesis to the mindset that should be making languages to begin with if you can't do logic with the words that already exist. Horrible sales pitch. Are they trying to confuse people on purpose, make moats so nobody learns it? is this self-sabotage?

---

I have bludgeoned an AI on this matter. I feel kind of bad. It tried to ad hominem me and then tell me I'd get it if I wasn't so new, and that it's a perfectly valid name because it's in the "reference guide". Called it out on appeal to authority and now it's just saying my argument points back at me like it's groveling. Sigh.

And it's hallucinated thinking I'm the whole online community giving critiques on this matter now, therefore my points are valid, lmao

I am not a programmer, but I know a little bit of Python, C# and C++, but mostly basic syntax of latest two. Nevertheless it gives me higher ground, why?

I develop way od thinking which maker my life easier. I Havel intershop in Pharmacy and they print small papers with number which you show to get remaining drugs. Currently is number, 17592 which makes someone to type almost 40k numbers and erase also this amount. I use variable function in Libreoffice Writer and you have to type one number and it autonumber 64 (easily to expand but unnecessary) and save fucktone of time 😃 And this is why I thing that teaching programming is beneficial, because it develops mindset of resolving problems in easier way.

On the other hand in a few hours I wrote program for my girlfriend to draw randomly picture of herbal material (leaf, root, fruit etc) and ask for Latin name of this material, check if is correct and display necessary information. Programming was quick, most of time I prepare data for this software and this feels so fuxkibg awesome that I could use my knowledge to help my girlfriend and make something useful which makes me proud (code looks like blue waffle, but it works 😃). Fucking deadlines, but at least I could finish it 😃

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.

Here is my problem. The team I'm on has developers from other areas that were "put" into a new team. Two use "structured programming" but the requirements make me think we need "domain driven design". How in the world can I get them to evolve into another mindset while still meeting the deadline?

Work: Humans
Laptop: Mindset
Windows 10 update: Religion

effin management always commiting something they didnt think through and now the team suffers the consequences of their stupid actions, one of them is that they fucking commited a night of development phase for a major code revision fuck that shit cause that major revision also came for their fucking lack of analysis and mediocre mindset during the requirements gathering phase fuck that

I went to an interview a few days ago, just out of curiousity, even though i was sure that i won't be getting any "android developer jobs" there . it was a mega job fair. in one company, me and my friend neil(fake name) went. the interviewer guy was willing to give neil a package upto 10LPA (its a great offer for freshers in my country) based on his current skills of php js, react,angular, ... web stuff .
I had this assumption( and neil did too , we both kind off had the same mindset) that a company teaches us things, we just have to be a little famous/accomplished. So i thought why not? i am accomplished. i got 2 apps on playstore, i am an AAD certified Android dev and know a lot of android stuff, i am quite famous. i am equally as deserving as neil.

But what happenned was something different. When my turn came, the interviewer said " If you have no knowledge of phy/js/node/angular, why are you sitting here?" to which i said " i presumed company would teach me, since i bring some level of expertise from other fields"

so he told me some hard truths **"Companies are fast paced. they don't have time to train you in everything. we seek for candidates having some level of knowledge in the domain, so that we could brush up your skills, increase your knowledge to current requirement and push you to production engineer asap, so that you could be worthy of your salary"**

This is completely correct. i have stuck myself in such a career that its very difficult to sell myself for other job profiles. And from what i have seen, companies seek a very high level of proficiency in this field and rarely recruit freshers( or even if they do, salaries will be aweful)

. Now i am so unsure about what to do next:

A.) keep learning more and more of android and look for job in it. And even if am getting an aweful job offer, just sulk and take it
B.) do open source work/gsoc work?( its a good way to earn more recognition/stipend/knowledge and sometimes even job offers)
C.) learn web dev, data sciences, blockchain, cloud or other stuff that i don't yet know
D.) go back to ds algo / competitive? (because having good competitive knowledge is a safe zone. you are assumed as apure fresher with 0 level of practical knowledge but good level of mathemetics)

I know i am going suck in all of the above except maybe (A) or (B) because (C) is something that am unsure would grab my interest (and even if it did, i am sure i need another 1-2 years to be somewhat good at it) and (D) is something i myself know am uncapable of , i am an average shit in maths(but might mug it all up if i pull all nighters for 1 year)

Product designer keeps on changing designs and managers approve it every single time. Totally frustrated to work. Why can't they think of scenarios based on design? Why should they allow me work on something guaranteeing that things won't be changed but change every single time.

I know product specs change, but too much of change frustrates the developer. Why does no body care for developer's mindset?

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 🤔

Honestly I've had good luck, every single boss I've ever had has been great up until the most recent project manager (not people manager) at my latest consultant gig.

Guy was 60+, had the mindset that NOTHING can get done without a meeting, and that your ass in a seat is the most important metric of true productivity.

Coming from a mostly remote background with 50% travel, this was a huge pain in the neck to deal with for the last 2 months.

Luckily he's gone now (no one liked him...who would have thought).

Today is the official Kiki Day — a whole year passed since I discovered that a human is three separate coexisting entities that are physically divided by brain layers (they're three of them), so

1. my seven years old search for a perfect ideology had no sense whatsoever
2. when your feelings contradict each other, you may give two separate answers: one from neocortex (e.g. what you call "yourself") and one from the second layer (e.g. "emotional response")

If you for example dislike women but happen to be in a position that implies hiring people, say "even though I don't feel emotionally comfortable around women, they are equal to myself, so my emotions shouldn't influence my rational decisions".

To some extent, this very mindset is what I can call "kiki".

Need advice:

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.

Mastered NodeJS (my stack has always had node for the past 5-6 years) and I’m finding it difficult to switch to python for machine learning since things are so engraved in my head in javascript.

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.

A good idea will get you in a mindset.

The most productive way of development is going slow and don't make a lot mistakes. Lately, I'm doing the opposite. It's often not your skills or knowledge but just your patience / expectation to be managed. Since I switched from C to Python I got the mindset that everything should be possible to make in short time with low effort. Being used to do a lot of effort because of C development gave me a lot of patience and upgraded me to be a better dev at any language. But sadly, I notice it's a skill you can lose. How to retrain my patience. Doing a lot of C again. But I want to have the patience NOW (retoor said impatiently). What a paradoxale dilemma shit. You have to do patient stuff to be become patient whey really sucks and sucks if you became inpatient.

Very underrated skill that actually says a lot about you as programmer: patience.

With enough patience you can master anything. Without it, you're depending on tools that allow you to. That's OK, but there's always some price to be paid. Many time it's the ignorance not knowing how the tools work and thus how it actually works. Some people can live with that, others don't. Knowing how somethings works is relative anyway. Do you know how it works until the language level? Kernel level? Framework level? Everyone chooses themselves what the limit is I guess. My limit is the C api / kernel interface.

Random thoughts. I'm just bit frustrating performing low lately and speculating about what to do about it. I just don't have a different hobby than programming. Doing something else for a while to give brain a rest would be best but it should be something raising dopemine. TV / gaming doesn't do that for me.

Sigh, how to do absolutely nothing. I did it for a 1,5 year full time but that was because of medication. Now it's impossible.