1. I join a company.

2. I get deeply involved in "how to run the company", and get nice compliments from both coworkers & management about my skills in conveying startup/scaleup advice & necessities to upper management.

3. With my ego inflated through all the sweet talk, I think "ah, what the hell, let's do this again", and I accept a Lead/CTO promotion. I have to join board meetings, write reports on quarterly plans and progress.

4. I get unhappy/stressed/burned-out because I really just want to be a developer, not a manager/executive.

5. Upper management understands, I give up my lead position, lock myself back into my coding cave.

6. I get annoyed because the requirements I receive become more and more disconnected from reality, half of the teams seem to have decided to stop using agile/scrum, the testing pipeline breaks all the time, I get an updated labor contract from HR by mail which smells like charred flesh, etc

7. The annoyances become too much to do ANY work. I yell at the other devs outside of the entrance of my cave. There is no answer, only a few painful moans and sighs.

8. I emerge from my cave. The city has turned into a desolate wasteland. The office is a burning ruin, the air sharp and heavy with black soot. Disemboweled corpses of developers litter the poisoned soil.

Product Managers dressed in stained ripped suits scream at each other while they try to reinforce concrete barricades with scotch tape and post-its. *THUMP* Something enormous is trying to break through. "Thank God, bittersweet, you're still alive! The stakeholders! They have mutated! We couldn't meet the promised deadlines! We've lost the whole mobile app department, and that kid there is the last of the backenders and he's only an intern! You're here to save us, right? RIGHT?".

In the corner, between the overflowing coffee machine and a withered cactus, a young boy has collapsed onto the floor. His face is covered in moldy coffee grounds, clasping on to his closed macbook for dear life, wide-open eyes staring into the void, mumbling: "didn't backup the database, and It's all gone" over and over.

A severely dented black Tesla with a dragging loose bumper breaks through the dried up vertical herb garden and the smoothiebar, and comes to a halt against the beanbags in a big cloud of styrofoam balls.

The CEO limps out, leaking blood all over the upholstery. He yells to the COO: "The datacenter is completely flooded with sewage! I saved the backup tapes though", holding a large nest of tangled black magnetic tape mixed with clumps of mud above his head.

9. I collect my outstanding salary and sell any rewarded options/shares for a low dumping price, take a 5 month holiday, and ask a recruiter about opportunities in a different city.

*deep breath*

Remain calm, don’t freak out, remain calm, don’t freak out.

*deep breath*

Ok, so my sort of new manager (had a slightly different manger-ish role on the team), has for the third time in as many months, just sent an email criticizing the dev team for our working from home-ness (which for the record has not been that bad, 2/3 or 3/3 have been in everyday for the past month)

In this same period, there has been late nights, weekends, successful releases, I’ve been invited to talk at a conference about my work (not a particularly big one, but still). Point is, everything is going well, very well in fact.

There has been no emails discussing our great work, thanking us for extra work, thanking us for picking up slack from other teams who are down a few people etc. no our major concern it seems is the “optics” of our team not being present in the open space.

Our contracts list flexible working hours, and his boss has frequently told us WFH is fine when things are too busy. But no he is complaining for us to get our hours in the office in line and make sure we are in the office more.

It’s been a particularly long and frustrating week, and I’m very tempted to inform him that if he is concerned about my chair and desk looking empty, that I can put them somewhere for him where they will always be occupied until a surgeon can remove them.

However, thanks to the deep breaths, I’ve managed to restrain myself long enough to run this past you all first and ask advice.

Please help,
Sincerely,
My sanity

Welcome back to practiseSafeHex's new life as a manager.

Episode 2: Why automate when you can spend all day doing it by hand

This is a particularly special episode for me, as these problems are taking up so much of my time with non-sensical bullshit, that i'm delayed with everything else. Some badly require tooling or new products. Some are just unnecessary processes or annoyances that should not need to be handled by another human. So lets jump right in, in no particular order:

- Jira ... nuff said? not quite because somehow some blue moon, planets aligning, act of god style set of circumstances lined up to allow this team to somehow make Jira worse. On one hand we have a gigantic Jira project containing 7 separate sub teams, a million different labels / epics and 4.2 million possible assignees, all making sure the loading page takes as long as possible to open. But the new country we've added support for in the app gets a separate project. So we have product, backend, mobile, design, management etc on one, and mobile-country2 on another. This delightfully means a lot of duplication and copy pasting from one to the other, for literally no reason what so ever.

- Everything on Jira is found through a label. Every time something happens, a new one is created. So I need to check for "iOS", "Android", "iOS-country2", "Android-country2", "mobile-<feature>", "mobile-<feature>-issues", "mobile-<feature>-prod-issues", "mobile-<feature>-existing-issues" and "<project>-July31" ... why July31? Because some fucking moron decided to do a round of testing, and tag all the issues with the current date (despite the fact Jira does that anyway), which somehow still gets used from time to time because nobody pays attention to what they are doing. This means creating and modifying filters on a daily basis ... after spending time trying to figure out what its not in the first one.

- One of my favourite morning rituals I like to call "Jira dumpster diving". This involves me removing all the filters and reading all the tickets. Why would I do such a thing? oh remember the 9000 labels I mentioned earlier? right well its very likely that they actually won't use any of them ... or the wrong ones ... or assign to the wrong person, so I have to go find them and fix them. If I don't, i'll get yelled at, because clearly it's my fault.

- Moving on from Jira. As some of you might have seen in your companies, if you use things like TestFlight, HockeyApp, AppCenter, BuddyBuild etc. that when you release a new app version for testing, each version comes with an automated change-log, listing ticket numbers addressed ...... yeah we don't do that. No we use this shitty service, which is effectively an FTP server and a webpage, that only allows you to host the new versions. Sending out those emails is all manual ... distribution groups?? ... whats that?

- Moving back to Jira. Can't even automate the changelog with a script, because I can't even make sense of the tickets, in order to translate that to a script.

- Moving on from Jira. Me and one of the remote testers play this great game I like to call "tag team ticketing". It's so much fun. Right heres how to play, you'll need a QA and a PM.

*QA creates a ticket, and puts nothing of any use inside it, and assigns to the PM.
*PM fires it back asking for clarification.
*QA adds in what he feels is clarification (hes wrong) and assigns it back to the PM.
*PM sends detailed instructions, with examples as to what is needed and assigns it back.
*QA adds 1 of the 3 things required and assigns it back.
*PM assigns it back saying the one thing added is from the wrong day, and reminds him about the other 2 items.
*QA adds some random piece of unrelated info to the ticket instead, forgetting about the 3 things and assigns it back.

and you just continue doing this for the whole dev / release cycle hahaha. Oh you guys have no idea how much fun it is, seriously give it a go, you'll thank me later ... or kill yourselves, each to their own.

- Moving back to Jira. I decided to take an action of creating a new project for my team (the mobile team) and set it up the way we want and just ignore everything going on around us. Use proper automation, and a kanban board. Maybe only give product a slack bot interface that won't allow them to create a ticket without what we need etc. Spent 25 minutes looking for the "create new project" button before finding the link which says I need to open a ticket with support and wait ... 5 ... fucking ... long ... painful ... unnecessary ... business days.

... Heres hoping my head continues to not have a bullet hole in it by then.

Id love to talk more, but those filters ain't gonna fix themselves. So we'll have to leave it here for today. Tune in again for another episode soon.

And remember to always practiseSafeHex

I feel the need to take a different approach to this week's rant. I think someone needs to defend teachers, for a number of reasons. Obviously this is probably out of place on devRant but it is a kind of rant against those who think they know everything and have nothing to learn.

1) Teachers are not industry specialists. They do not spend their lives keeping on top of the latest framework or project management methodology or code management tool. They are educators and that brings its own set of out of hours challenges and training exercises.

2) They have a course to teach and have probably used the same one for quite some time. Years probably. They (should) teach the fundamentals of programming not a particular language or syntax or quirk. Those fundamentals don't really change. Logic, problem solving, precision, structures, etc.

3) They need to provide a course which will cater for different skill levels. There are always class members who are bored because it's too easy and others who struggle in any subject.

4) Teaching is like any profession - there are really, really good ones, OK ones and there are shit ones.

5) They have probably never developed a detailed project or solution in their lives. They don't know the pitfalls and challenges that teams face in this kind of environment. Should they - maybe. But the probably don't.

I think that's all... I'm not a teacher (although I did fancy the idea at a time) but just feel they get a rough ride sometimes (particularly on here).

How I feel working with code that's been worked on by at least three different teams at three different companies over the past couple of years and not a single person has left any comments or documentation.

*the Company closes a project and splits us in different teams*

Me: *tells the manager for half a year about feeling extremely bad in the new team which is mobbing me, caling the previous project "shit" (it was not, it simply didn't need to be alive anymore cause we found out cheap alternatives) and not letting me do anything*

Company(half a year later): *sends me into a new project* we don't get why you are underperforming lately.

Me: *full burnout after half a year of being treated as living shit* yeah. Wonder why.

TL;DR :

"when i die i want my group project members to lower me into my grave so they can let me down one last time"

STORY TIME

Last year in College, I had two simultaneous projects. Both were semester long projects. One was for a database class an another was for a software engineering class.

As you can guess, the focus of the projects was very different. Databases we made some desktop networked chat application with a user login system and what not in Java. SE we made an app store with an approval system and admin panels and ratings and reviews and all that jazz in Meteor.js.

The DB project we had 4 total people and one of them was someone we'll call Frank. Frank was also in my SE project group. Frank disappeared for several weeks. Not in class, didn't contact us, and at one point the professors didn't know much either. As soon as we noticed it would be an issue, we talked to the professors. Just keeping them in the loop will save you a lot of trouble down the road. I'm assuming there was some medical or family emergency because the professors were very understanding with him once he started coming back to class and they had a chance to talk.

Lesson 1: If you have that guy that doesn't show up or communicate, don't be a jerk to them and communicate with your professor. Also, don't stop trying to contact the rogue partner. Maybe they'll come around sometime.

It sucked to lose 25% of our team for a project, but Frank appreciated that we didn't totally ignore him and throw him under the bus to the point that the last day of class he came up to me and said, "hey, open your book bag and bring it next to mine." He then threw a LARGE bottle of booze in there as a thank you.

Lesson 2: Treat humans as humans. Things go wrong and understanding that will get you a lot farther with people than trying to make them feel terrible about something that may have been out of their control.

Our DB project went really well. We got an A, we demoed, it worked, it was cool. The biggest problem is I was the only person that had taken a networking class so I ended up doing a large portion of the work. I wish I had taken other people's skills into account when we were deciding on a project. Especially because the only requirement was that it needed to have a minimum of 5 tables and we had to use some SQL language (aka, we couldn't use no-SQL).

The SE project had Frank and a music major who wanted to minor in CS (and then 3 other regular CS students aside from me). This assignment was make an app store using any technology you want. But, you had to use agile sprints. So we had weekly meetings with the "customer" (the TA), who would change requirements on us to keep us on our toes and tell us what they wanted done as a priority for the next meeting. Seriously, just like real life. It was so much fun trying to stay ahead of that.

So we met up and tried to decided what to use. One kid said Java because we all had it for school. The big issue is trying to make a Java web app is a pain in the ass. Seriously, there are so many better things to use. Other teams decided to use Django because they all wanted to learn Python. I suggested why not use something with a nice package system to minimize duplicating work that had already been done and tested by someone. Kid 1 didn't like that because he said in the real world you have to make your own software and not use packages. Little did he know that I had worked in SE for a few years already and knew damn well that every good project has code from somewhere else that has already solved a problem you're facing. We went with Java the first week. It failed miserably. Nobody could get the server set up on their computers. Using VCS with it required you to keep the repo outside of the where you wrote code and copy and paste changes in there. It was just a huge flop so everyone else voted to change.

Lesson 3: Be flexible. Be open to learning new things. Don't be afraid to try something new. It'll make you a better developer in the long run.

So we ended up using Meteor. Why? We all figured we could pick up javascript super easy.Two of us already knew it. And the real time thing would make for some cool effects when an app got a approved or a comment was made. We got to work and the one kid was still pissed. I just checked the repo and the only thing he committed was fixing the spelling of on word in the readme.

We sat down one day and worked for 4 straight hours. We finished the whole project in that time. While other teams were figuring out how to layout their homepage, we had a working user system and admin page and everything. Our TA was trying to throw us for loops by asking for crazy things and we still came through. We had tests that ran along side the application as you used it. It was friggin cool.

Lesson 4: If possible, pick the right tool for the job. Not the tool you know. Everything in CS has a purpose. If you use it for its purpose, you will save days off of a project.

At my previous job I was told by "senior" devs that my interest in learning new things and knowing more is not a good thing. And that I should learn to increase my depth in the programming of the product that was being used.
As part of my job I was asked to analyze the product's architecture. I found out that it was needlessly complicated and performed horribly. The senior devs that were on that product for a while had been hiding their mess from the rest of the teams. Needless to say, my report didn't make me very popular with them.
I was asked to help come up with a strategy for testing.
A guy who had just joined our company out of college and me worked really hard for a few weeks and managed to bring testing down from 3 months to around 3weeks. Our reward: he was fired(albeit for different reasons. The company was trying to restructure)
My yearly review was terrible and I was put on 2 months probation. So I quit.
It sucked. And made me question my ability as a programmer for a while. I've floated my own firm and though money is hard sometimes, it so much more rewarding.

A lot of engineering fads go in circle.

Architecture in the 80s: Mainframe and clients.

Architecture in the 90s: Software systems connected by an ESB.

Architecture in the 2000s: Big central service and everyone connects to it for everything

Architecture in the 2010s: Decentralized microservices that communicate with queues.

Current: RabbitMQ and Kafka.

... Can't we just go back to the 90s?

I hate fads.
I hate when I have to get some data, and it's scattered on 20 different servers, and to load a fucking account page, a convoluted network of 40 apps have to be activated, some in PHP, others in JS, others on Java, that are developed by different teams, connected to different tiny ass DBs, all on huge clusters of tiny ass virtual machines that get 30% load at peak hours, 90% of which comes from serializing and parsing messages. 40 people maintaining this nightmare, that could've been just 7 people making a small monolithic system that easily handles this workload on a 4-core server with 32GB of RAM.
Tripple it, put it behind a load balancer, proper DB replication (use fucking CockroachDB if you really want survivability), and you've got zero downtime at a fraction of the cost.

Just because something's cool now, doesn't mean that everybody has to blindly follow it for fucks sake!

Same rant goes for functional vs OOP and all that crap. Going blindly with any of these is just a stupid fad, and the main reason why companies need refactoring of legacy code.

There's so many posts on here that say fuck apple or Microsoft only real programmers or computer users run Linux. Maybe step back and reflect why these companies got big. Maybe the programmers in their development teams are actually good. Maybe variety and competition and different focuses is good for us and consumers.

Why do people have to lie? I am seriously getting tired of it.

Context: While I was on vacation the company hired some guy we’ll call Bob.
Bob is a senior with 10+ years of experience. 5 of those years in React (supposedly).
I got back from vacation and was told I’d be working on a project with Bob.
I’ve worked in teams before so I thought no problem.

Now I am aware that different people have different styles, so that’s why we agreed on a lint config with some fancy git hooks.

I was excited at first because the project actually seems nice, but my excitement soon turned into terror.

First of all, Bob doesn’t seem to understand Git…fair enough, I’ll give him a quick guide…

Mf calls me at 11pm on a Friday because he can’t push because the tests are failling.

Now tests. Bob doesn’t write those. Great.

We had created a few components to use throughout the project.

Bob seems to consistently forget what components are and why you write them and just imports the defaults from the UI library we’re using.

Bob also has a kink for hardcoding values for some reason.

I talked to Bob multiple times about this and he just tells me he’ll change it but in the end the PR stays open for 5 days, before it’s actually me who goes in and fixes it. Oh and yeah this shit keeps happening over and over again.

Now I know some of us devs hate meetings but for the love of God Bob just show up. You don’t even have to speak. Or at least answer a message that corresponds to the working hours and not in the middle of the night.

I am getting tired of this behavior and am seriously holding back from reporting this to the management. It’s been a month and I am seriously worried about the project. I have my own stuff to do but it takes time for me to clean up his absolute mess that doesn’t even pass the CI.

Call me an asshole I don’t care. It’s been a month and I’m legit worried about the future of the project.

People/companies talking about ooh we want gender diversity we want more female software developers, IT professionals etc

You talk the talk, do you know how to walk the walk?? Do you know how to deal with female engineers?

I am a hardcore engineer worked and studied majorly with men for years. I lead, managed teams had my own company worked as a consultant for years.

Then I got into the IT industry as developer later. I was completely against the idea of being female would make any difference or you would be treated differently.

Finally I had my own enlightenment and stopped resisting that idea.

Some treatments made me think what are these guys doing? Don’t treat me like your sister. I am not your sister. Don’t see the femininity or looks. I am not a Merrilyn Monroe to say oooh you are great you know soo much. I am not paid for that act, I do my job! It’s same as yours mate.

Don’t underestimate me or try to preach me as if I am a cute little girl. Don’t show off and boost your ego next to other guys.

Now I regretfully I agree the ladies ranting about male dominance and getting different treatment in IT.

I am literally trying to avoid red nail polishes or red lipstick god forbid. Maybe I should put some fake beard and a belly, loose jeans with an energy drink in hand. Here comes the expert IT professional, already ticking a box.

Honestly you are not taken seriously most of the time. If you are a guy then they are all ears..And those guys talk about they want gender diversity blah blah

You feel like a ghost when you express your opinion. You are not taken into account even when you have a comment or suggestion.

Even humiliated by a guy giving me a speech about how to be a good developer next to a manager. Look buddy I am not a yesterday’s child. I am at your age. I haven’t come to this position by jumping around picking flowers in a field. If I was a man, would you dare saying those to me? There could be a street fight coming.

LinkedIn selfie takers with body show offs putting ooh I am an IT recruiter as a female I got into IT. You can do it too. (don’t get me wrong I respect that achievement that’s good) but those girls get thousands of likes and applauses, you are working in IT for years people say they are seeking for. Your technical post doesn’t even get 20 likes. Your encouraging comment on a guy’s post isn’t even acknowledged. You are not even taken into account. Am I a ghost or something?

Honestly I don’t understand.

What do you mean by gender diversity? What do you want here?

Leave this gender bullshit. Look at the knowledge you don’t even know what equality means. It’s not having even numbers of genders. It is respecting knowledge and hard work regardless. Listening and acknowledging without judgement. Looking beyond male, female or others

Companies that say we want to have more females, you don’t come and knock on my door either. You are already stating a difference there. Attract with indifference don’t come and tell me you are a female we want more females here.

I’m telling you this sector is not getting proper gender equality for 25 years. Talk is there but mentality is not yet there.

I am super pissed off and discouraged today. I don’t even get discouraged that easily. Now I understand some women in IT talking about insecurities. I am on the edge of having one, such a shame.

Don’t come at me now I would bite!

This is my generalisation yes. Exceptions apply and how good it would have been if those exceptions were dominant.

Seeing there are many people (including me) that cant acces the hackathot, I thitk, it would be nice if we as community could hold an unoficial remote hackathon.

My ideas:

-5 days to code
-github / skype
-chess engines which have to compete eachothers to find the winner
-5 teams
-should be compatible with windows, linex, mac (either an interpreted language or different recompiled versions)

Tell me what you think in the comments

My favorite thing is my nerf gun. In my office different teams are organized in different pods. You never know when a war will break out between the teams, you need to be able to defend yourself! Also not bad for getting someone's attention who has headphones on...

This week actually. We had an Innovation Week. I was tired of waiting for the company's collaboration tech team to give us some kind of virtual whiteboard system (they also won't let us use things like Google Hangouts or Microsoft One Note, etc...so they make remote collaboration and planning almost impossible)

Anyways long story aside I proposed we make a virtual whiteboard we could host internally as a web app using STOMP over Websocket. They said "there's no way you can finish that in a week". I did.

And it came out great. It even supports pressure sensitivity and different brush textures. Everyone loves it and teams are like...wow we could use this member facing too. Had like 5 people around my desk connected to it drawing dicks for like 30 minutes. Then our boss joined remotely and saw the dicks. They laughed their ass off.

tldr; was told there was no way I would complete an ambitious innovation project...completed it with style. Damn I am good.

i genuinely like programming. it's like solving logical puzzles for me, challenges on a smaller or bigger scale, and this is fun.
i always feel this when working on something on my own, i.e. a full stack project where i take care of everything.

but i'm so sick and tired of corporate software development.
i'm tired of scrum, all these scrum meetings, it feels like they are sucking my life energy away. if at least i had the feeling that i work in a team where everybody contributes, the team work is nice and also project management is aligned.
i'm tired of having too many different tasks in too many different areas or projects and never having the feeling to be able to really concentrate on one thing, to be able to do a job well enough so that i'm content with it.
i'm tired of this feeling that what i'm working on is not meaningful. the feeling that my team is not part of a bigger story where everyone contributes their part and where there is a sense of productive collaboration between teams. the feeling that mismanagement will result in a lot of money being burned, because of work being thrown away or becoming irrelevant, or because of miscommunication, making promises that can impossibly be delivered on.
this feeling that i cannot really improve or fix the ship we are sailing with, but rather being handed a bucket and being told to constantly remove the leaking water and put it back in the ocean, but always at multiple sites of the ship all at once.
i'm tired of being the only female dev and altogether feeling so different from the rest of the team, feeling that i do not belong there.

even though i need to make a living, i just can't imagine anymore to spend so much of my lifetime for something that makes me feel so bad...

Worst collaboration experience story?

I was not directly involved, it was a Delphi -> C# conversion of our customer returns application.

The dev manager was out to prove waterfall was the only development methodology that could make convert the monolith app to a lean, multi-tier, enterprise-worthy application.

Starting out with a team of 7 (3 devs, 2 dbas, team mgr, and the dev department mgr), they spent around 3 months designing, meetings, and more meetings. Armed with 50+ page specification Word document (not counting the countless Visio workflow diagrams and Microsoft Project timeline/ghantt charts), the team was ready to start coding.
The database design, workflow, and UI design (using Visio), was well done/thought out, but problems started on day one.
- Team mgr and Dev mgr split up the 3 devs, 1 dev wrote the database access library tier, 1 wrote the service tier, the other dev wrote the UI (I'll add this was the dev's first experience with WPF).
- Per the specification, all the layers wouldn't be integrated until all of them met the standards (unit tested, free from errors from VS's code analyzer, etc)
- By the time the devs where ready to code, the DBAs were already tasked with other projects, so the Returns app was prioritized to "when we get around to it"

Fast forward 6 months later, all the devs were 'done' coding, having very little/no communication with one another, then the integration. The service and database layers assumed different design patterns and different database relationships and the UI layer required functionality neither layers anticipated (ex. multi-users and the service maintaining some sort of state between them).

Those issues took about a month to work out, then the app began beta testing with real end users. App didn't make it 10 minutes before users gave up. Numerous UI logic errors, runtime errors, and overall app stability. Because the UI was so bad, the dev mgr brought in one of the web developers (she was pretty good at UI design). You might guess how useful someone is being dropped in on complex project , months after-the-fact and being told "Fix it!".

Couple of months of UI re-design and many other changes, the app was ready for beta testing.

In the mean time, the company hired a new customer service manager. When he saw the application, he rejected the app because he re-designed the entire returns process to be more efficient. The application UI was written to the exact step-by-step old returns process with little/no deviation.

With a tremendous amount of push-back (TL;DR), the dev mgr promised to change the app, but only after it was deployed into production (using "we can fix it later" excuse).

Still plagued with numerous bugs, the app was finally deployed. In attempts to save face, there was a company-wide party to celebrate the 'death' of the "old Delphi returns app" and the birth of the new. Cake, drinks, certificates of achievements for the devs, etc.

By the end of the project, the devs hated each other. Finger pointing, petty squabbles, out-right "FU!"s across the cube walls, etc. All the team members were re-assigned to other teams to separate them, leaving a single new hire to fix all the issues.

Microsoft Teams can burn.

Who the fuck thought it would be an excellent workflow, when you want to COLLABORATE IN TEAMS between users in different domains, that each sorry bastard needs to manually log in to a second Teams tenant and loose all the context from their main Teams tenant !?

On random occasions the fucking authentication token expires. I send messages to my team mate in another domain. Three days later I am pissed off because they don't answer. It turns out their authentication token has expired so when they are on their main tenant they don't get any notifications before they manually log in to our tenant as a guest. HOW FUCKING GREAT IS THAT AS A NOTIFICATION SYSTEM ??!

Would it be that fucking difficult to maintain a notification bar with all tenants and note with an exclamation mark or something REALLY FUCKING SIMPLE to hint about an expired token ? It's not like this is magic, Slack does it already.

FUCK !

Test server not working as expected - check with test team.
Test team experiencing the same problem - report to dev.
Dev team says the issue is not on their side - check with the service owners.
Service owner says it might be a problem with the request and gives me another point of contact - send an email with all the info.
POC says it doesn't have anything to do with him and copies "the right person".
Next person says to ask a different team.

Get reprimanded for asking too many teams.

Jeez idk, maybe if you stopped passing on the blame like a hot potato and actually helped me out I wouldn't need to.

So I recently had a university project which focuses video game audio. We had to work in groups of 3 students and the task was to create a video game which uses audio as a gameplay mechanic.

Our idea was to create a game where you collect different audio samples which get looped as background music, and you have to select the correct ones to have a nice tune. To make it a bit more challenging we had enemies, guns and grenades plus doors which only open if the correct music is playing.

The guns fire on-beat, and the grenades always explode on the first beat of the next bar.
It was quite challenging to get things synced since even small offsets are noticable.

I wrote some nice code and theoretically it should have worked but for some reason the gun shots and the grenades didn't quite hit the beat of the music.

I tweaked stuff, created workarounds, optimized lot's of code to get execution times down but it still only worked sometimes.

I tweaked more and more only to realize that the timing drifted over time.

At that time I worked 20-30 hours on tweaking and trying to get it perfectly timed.

After recalculating some numbers I realized that all the audio samples are recorded at 135 bpm, but the guys who did the recordings said it was 130bpm.

I asked them if it could be the case that the samples are 135bpm and they said:
"yes, they are at 135 bpm as we told you"

I scrolled back in the telegram conversation only to see that they said 130.
Changing the number to 135 resolved all the problems and all of my workarounds and tweaks weren't needed.

So I worked for nearly 30 hours just because they didn't notice their fault and even when they realized that the timing is off sometimes (which took forever because they never played the game), they didn't even consider that they might have given me the wrong numbers.

This all wouldn't be that bad if both of my teammates had worked for more than 15 hours but they didn't. I did all the hard work and the only single thing they did fucked up my workflow. It fucked up the system I created and it fucked up the gameplay as things got unpredictable. Because of their fucking fault I worked as much as both of them combined IN ADDITION to all the other work I did (built 3 maps, coded everything, created animations, ...)

I love working in teams, but only if the whole team is motivated. Those two fuckers were the exact opposite.
Luckily i found the error so I could fix it, but guess with whom I'll never ever work together again?

For the first time I am feeling like.... I hate my job.

Agile and Scrum can be fucked, but at least there is a work methodology. I was hired by a company being run the old school way.

These guys never heard of git??
- Fuck you. We never used git and neither should you.

Client company does not want to give me push/pull access to their gitlab instance??
- Fuck you, you can use our RDP server for that.

Project planning features be damned, they've got email, Teams and videocalls!

Can I develop in peace? Fuck no, I have to give IT support to the guy who hired me.

Our timeline is defined IN A FUCKING WORD DOCUMENT FOR FUCKS SAKE. I can't connect Issues to milestones in a Word doc

Oh, and the customer is running everything on prem. If there is a need to scale up, FUCK ME. I should have specified 20 machines from the get go or gtfo. We're using 2 machines to run 8 different services that are going to be ingesting and computing data.

They want state of the art on a cheapskate.

And I have nothing else lined up at the moment. Although I am soon to renew the contract... This contract binds me with professional responsibility for a project being ran by people who do not give a single fuck about optimizing the work process.

Old rant here. Took place ~2 years ago and just remembered it recently:

For some reason our company decided to disable incognito mode in Chrome... Wtf, who comes up with that shit?!
Our team has different certificates to test our application and therefore the private mode comes in quite useful. Otherwise you would need to close and reopen all browser instances again.

At least, after a shitstorm from various teams they unblocked incognito again.

Mother fucking cunts should be shot into the sun...

It's worse enough when you have to deal with many things at once...

But how the fuck can 3 people from 3 different teams have the same bullshit idea to disturb a meeting and just start talking like it's the most normal thing.

YEAH. INTERRUPTING MEETING AND JUST BLABBERING ON AND ON...

Then fucking laughing how funny it is.

Upper management found it absolutely not funny.

Working from home prevented a mass murder today.

Just over heard, Dev A was reviewing another team's code ...
Senior Dev A: "I don't understand this teams code. I hate WebAPI. Wish we could use X."
Senior Dev B: "Why can't we use X?"
Senior Dev A: "It's frowned upon."
Senior Dev B: "By whom?"
- couple of seconds of silence -
Senior Dev A: "X is not a Microsoft technology"
- few more seconds of awkward silence -
Senior Dev A: "X is magnitudes slower than WebAPI anyway."
Senior Dev C: "What? How much slower?"
- caught off guard..didn't know Senior Dev C didn't have his headphones on -
Senior Dev A: "Um...I don't know, that is what you told me."
Senior Dev C: "I never said that. I've never used X. I prefer WebAPI anyway, but both WebAPI and X use REST based protocols, I doubt X is magnitudes slower. Actually, I think you told me WebAPI was slower."
Senior Dev A: "Different paradigm."
- second or two of silence -
Senior Dev B: "What?"
Senior Dev A: "Hey, did you see on twitter ..."

Have no idea where he thought that conversation was going. Maybe he was hoping the other devs would dog-pile/attack the code. Pretty funny it backfired. His face when Dev C said 'I never said that' was priceless. Like "Oh -bleep- ..how do I lie out of this one? ...quick, distract with random words or a twitter post"

As a software house, we have many teams on different projects. One project was due to a Thursday, and the PM asked the team 1 week before if they could work over the weekend since there's a lot of things to do.

On the Friday before, one of the devs showed up a bit later than usual (around 10am), but ok...

After lunch he asked to talk to HR and also the boss. They talked for around 2h, then he started to say "goodbye and good luck" for everyone.

The project was on fire and he just... leave.

On the next 2 months another 4 people leave the company. All from the same team/project (but not with a big surprise like him).

Apparently, the team was constantly complaining to PM and boss about unrealistic deadlines and constant requirements changes, but they didn't did anything about it. Just when more than half this team had left the company they started to rethink this actions to this project and the others on the company.

I'm so fed up of this shitty ultra-ortodox industry

I've worked on many different projects, been in many different teams. It's an ever changing industry, but, surprisingly, it's so orthodox. Dev industry nowadays have some rules, that everybody adopts them as "best practices". You have to work on pull requests, and several of your teammates have to review your shit (as if they have nothing better to do).
I'm sick of people using fucking DTOs in shitty frameworks like Laravel. Using DTOs in Laravel is like putting mustard in a fucking chocolate cake.
I'm so fed up of SPAs and node.js. I've yet so see a single SPA that handles jwt tokens correctly. I'm tired of spending hours and hours, days and days, struggling with thousandls of layers of abstractions instead of being productive and getting the shit done.
Because end customers don't give a shit about your "best practices": They have a problem and you are getting paid for it to be solved, not for spending hours and hours struggling with stupid Javascript and its crazy async nature and their crappy libraries.

Damnit. I say. Now. I now feel better. Thanks for listening :)

I've been a programmer for almost 19 years but I actually think the best code I've ever written is something that while it provides value to other people I'm the only one who actually uses it. In the company where I work we have major events that have to be supported by a number of different teams across about 5 time zones and each engineer has a limited set of roles that they can perform during the event. Anyway it was painful just watching people trying to create a schedule so I wrote something with Linear Programming to automatically generate the schedule. It ensures that people don't work for longer than 4 hours in a row, don't work from more than 8 hours from the first hour to the last hour on call, get 12 hours rest between engagements and the work load is evenly distributed across the team. Creating conditions in Linear Programming is weird, imagine trying to turn a series of linear equations into boolean logic, it can be done and once you can wrap your head around it it's really fun. It was my first time writing anything in it and I don't see it coming up a lot in my career. My favourite part of this project is that the end result was that engineers were less exhausted. I really hope that doesn't remain the best code I ever wrote, I don't think it will but it will require a conscious intention.

Our project at work goes live in 3 weeks.

The code base has no automated tests, breaks very often, has never had any level of manual testing

will not be releasing with any form of enforced roles or permissions in our first release now due to no time to enforce, however there is a whole admin api where you can literally change anything in our database including roles.

We also have teams in various countries all working separately on the same solution using microservices with shared nuget packages and they aren't using them properly.

Our pull requests are so big - as much as, 75 file changes - in our fe app that I can't keep up with it and I honestly have no idea if it even works or not due to no automated tests and no time to manually test.

We have no testing team, or qa team of any sort.

Every request into the system has to hit a minimum of 3 different databases via 3 different microservices so 1 request = 4 requests with the load on the servers.

We don't use any file streams so everything is just shoved in the buffer on the server.

Most of the people working on the angular apps cba to learn angular, no one across 2 teams cba to learn git. We use git so they constantly face problems. The guy in charge has 0 experience in angular but makes me do things how he wants architecturally so half the patterns make no sense.

No one looks at the pull requests, they just click approve so they may as well push directly to master.

Unfinished work gets put in for pull request so we don't know if the app is in a release state since aall teams are working independently, but on the same code base.

I sat down and tested the app myself for an hour and found 25 fe only issues, and 5 breaking cross browser issues.

Most of our databases are not normalised. Most of our databases make no sense. 99% of our tables have no indexing since there is no expertise with free time to do it.

No one there understands css properly. Or javascript.

Our. Net core microservices all directly use ef in the controller actions so there is no shared code there.

Our customer facing fe app is not dry because no tests so it was decided it was better this way.

Management has no idea on code state, it seems team lead is lieing to them about things like having any level of tests.

Management hire devs that claim to be experts but then it turns out they have basically no knowledge of what they were hired to do, even don't know what json is or the framework or language they are hired for, but we just leave them to get on with it and again make prs too big to review.

Honestly I have no hope that this will go well now but I am morbidly curious to watch. I've never seen anything like the train wreck that we are about to get experience.

Blue Robotics

This company makes underwater thrusters for submarine applications. With their first thruster they made it easy to make a homemade submarine. The motor was powerful, the thruster just worked. They even had a promotional where they created an automated surfboard that made it from hawaii to somewhere in california with one of their thrusters pushing it there the entire way. It was a great product.

Then they created the next version. This was the same thruster, but it had an ESC(Electronic Speed Controller) sealed in an aluminum puck on top of the motor. This ESC could be controlled by servo controls, or by plugging it into an i2c bus. You could pull different stats off of the motor over i2c it sounded great. So my robotics team trusted this company and bought 8 motors at $220 - $250 bucks each. We lightly tested them since we had not even finished the robot yet. One week before the competition our robot got completely put together and we did our first few tests.

Long story short, Us and 22 other teams did roughly the same thing. We bought these motors expecting them to work, but instead the potted aluminum ESCs were found defective. Water somehow got into the completely resin sealed aluminum puck and destroyed the ESC. We didn't qualify that year due to trusting a competition sponsor to deliver a good product. I will admit that it was our fault for not testing them before going to the competition. Lessons were learned and an inherent distrust of every product I come across was developed.

Big-time Microsoft fan who claims they've been using licensed versions of Windows since Windows 3.0. Still has all old versions of Windows on different machines / hard-disks. They use only Microsoft Surface devices. They still use Nokia Lumia (with Windows Phone 10). They were working with an organization that used Office365 for enterprise email and collaboration. They used Microsoft Teams for team collaboration when the rest of the organization was comfortable with Atlassian tools like jira, confluence and bitbucket.

One fine day, news spreads that the organization is moving into GSuite for enterprise email and collaboration. They are devastated. They quit citing personal and family reasons, but we knew the real reason.

Why even is Microsoft Teams?

Why does it suck so bad? Why is it a memory hog? Why does the ELECTRON desktop app not have native ARM64 support neither on Windows nor macOS? Why is it even an Electron app? Why the web version does not work with Safari (then again, barely anything more complex than my portfolio site works on Safari)? Why is the UI from 2016? Why is it preinstalled with Windows 11? Why the pre-installed Windows 11 version is a completely different entity? Why the preinstalled Windows 11 version does not work with school/work version of Teams calls?

We where designing next generation of standard PC platform. In the project we wanted to have input from different teams, what was important to them and it was the representative from Human Resourse to speakup,
"I would like to have round bobbles", it took us a while to figure out that he wanted, he wanted to change the shape of all dialog boxes.......
HR has often strange ways if looking at things.

For all my friends here who have known me for years can easily notice there has been a drastic change in me.

I used to be confident. That shit was hollow but I used to laugh in the face of fear. I was ignorant and that ignorance fueled a lot of the much needed confidence.

Over the years, I learned a lot. The more I know, the more I realised how much I don't know. And for all that I know, I have to use the brain power to retain and implement it, else it rusts.

This image is of my 2021 goals that I drafted last December. Wasn't able to achieve the first, the last and the art one. But surely got myself surrounded by some of the smartest people I have ever worked with.

Now they have rightly said, be careful with what you wish for.

MY CONFIDENCE IS SHATTERED.

I feel dumb. Constant imposter syndrome. While I am learning every moment and there is no measure to it, I feel incompetent to an extent that I have started questioning how did I even reach this far?!

While, yet again I am the youngest in my team, my manager is bit micromanaging and agressive with OKRs/KPIs and tech team isn't very supportive creating constant friction (something I never faced with developers in my life because devs are my best friends), I fear how much more time will I take to ramp up in this new job and feel confident enough to tackle things on my own without constant nudge from leadership or different teams?

Or is it just that I have burnt out firefighting and lost the motivation I had?

After all, what does this all even mean?

I started a new job about a week ago in an R&D software house which is a completely different world from what I am used to.

I worked as a coder in small teams, sometimes with Agile but always sunk in multiple projects at once - requiring constant switching of sprint goals week to week.

Now, I am alone (first person in a "maybe-in-the-future" team), doing research and preparing a demo for the client. It's hella lot of responsibility yet I found it weirdly liberating - being on my own, in control of what I do.

It may change in the future when project will inevitebly grow, but for right now, a week in, I started smiling while coding and learning, which I apparently haven't done in years.

What do you tell interviewers as a "Senior developer" when they ask you what you do at your current job.

I've been with my current for almost 8 years, since graduating... Few different time but not very well managed (semi/barely agile). Hasn't really provided any skill growth opportunities. Mostly fixing production issues, chasing other teams.

The projects I've worked on are in many different languages either enhancements or some standalone stuff. But nothing that's huge and I don't think I've learned anything from them. I usually apply what I learn and practice outside of work to work.

So to me I can probably list a whole lot of projects but to me their not that amazing, I didn't learn anything from them.

Also about those algorithm questions. I've never used any of this stuff actually at work. Concepts yes but not how do you implement ... And honestly I've never once had a situation that required algorithmic thinking other than maybe writing recursive functions in rare occasions...

But to me I've never once done anything harder or new which I haven't already done on my own....

Sorry for the disorderly rambling this turned into... which is sorta a problem too.

Everytime I think about interviews, I want to give rants about we technical questions are BS, how I probably have enough real experience to tackle any problem and come up with a good plan/solution (in a realistic timeframe, not 20 minutes from design to implementation)

College is worse than cancer.

Worse than tumor.

Worse than any (un)imaginable death or torture.

I feel dull.

I feel DUMBED DOWN.

I FEEL DUMBER AFTER 6 YEARS OF COLLEGE COMPARED TO BEFORE STARTING COLLEGE.

6 fucking years of wrecking my healthy brain in college.

Has now became unhealthy and mentally unstable.

I forgot almost EVERYTHING i knew about coding.

Because in a "COMPUTER SCIENCE" college they teach everything BUT coding.

The professors and assistants have no morals.

They are INHUMANE.

Professors are ready to walk across a fucking corpse.

If your mother gets cancer and you are unable to come to class or study, the professors dont give a FUCK, they will drop you down so you have to study for exams again instead of helping your ill mother.

Professors have NO COMPASSION.

NO DIGNITY.

They are just BRAINLESS robots.

Sentients, agents working for the matrix.

They keep reading the same script every year and call that a successful career.

IF PROFESSORS AND ASSISTANTS AT COLLEGE ACTUALLY KNEW TO DO ANYTHING USEFUL IN LIFE, THEY WOULD NOT BE PROFESSORS AND ASSISTANTS FOR THE MAJORITY (OR WHOLE) OF THEIR LIFE.

I gave my maximum effort.

I SACRIFICED MY LIFE FOR SCHOOL.

Just to end up with school spitting on my face.

I feel DUMBED down.

Robotic.

Procedural minded.

As some brainless retard who has to follow orders as if im a 6 year old who doesn't know what to do.

Like a computer.

Because of college - i have no will to live.

Because of college - i no longer have passion for coding.

Because of college - i no longer know what is my purpose in life.

Because of college - i feel like im floating in cosmos, somewhere far deep into the space, without knowing where im going, what im doing, why im doing what im doing...

I feel void inside me.

I also feel vengeance inside me.

SCHOOL HAS RUINED MY LIFE.

It made me mentally insane.

It made me mentally so sick that i had to watch head decapitation gore videos to calm myself down, so i can imagine the victims being murdered are the professors and assistants from my college.

PROFESSORS AND ASSISTANTS HAVE 0 UNDERSTANDING FOR OTHER HUMAN LIFE.

MILLIONS of people have private problems going on in their lives every day.

What if someone cant pass an exam because of private problems that's going on in their life?

What if the student is abused by a family member?

What if the student has ANY non-self destructive negative event happening to them, which they're not at fault, and can not control?

What if the student got cancer and cant study for exams, is he supposed to fail?

What if the student came home and the police knocked on his door and said "sorry for your loss, your whole family just died in car accident" and student falls into depression and cant study for exams, is he supposed to fail???

There are infinite multitude of random events this damned universe can do to a human life.

BUT PROFESSORS AND ASSISTANTS;
DO
NOT
GIVE
A
FUCK.

I feel soulless.

I feel like i signed a contract with the devil when i started college by selling him my soul.

School (when i say school, i also mean college, because its the same fucking shit under a different name) is supposed to represent "education".

Lets talk about it.

What exactly are we being "EDUCATED" in school?

To memorize pdf slides?

Memorize textbook?

Memorize notes?

Memorize formulas?

Memorize memorize memorize???

First of all, all of what we're "studying" is BULLSHIT, second of all MEMORIZING all of this means you're gonna forget 60% of it tomorrow, 80% in the next 2 days and you'll forget 100% of what you "learned" by the 7th day.

SOCIETY TOLD YOU TO MEMORIZE USELESS BULLSHIT AND TOLD YOU THAT YOU'RE BEING EDUCATED THAT WAY. YOU MUST BE FUCKING DUMB TO BELIEVE THAT.

If memorizing == education, then i do NOT want to be a part of this "education".

BEFORE starting college i coded many projects.

I self-learned everything.

6 years of college and it taught me LESS THAN ZERO.

NOT EVEN ZERO.

LESS THAN ZERO because i got dumbed down, below the underground, and had to dig myself up on the surface.

I built software for an american real estate agency and sold it for 5 figures.

I built software for 3 people from New York for another 5 figures.

I even got offers to work in local software companies without having a degree.

At internship i was given a task to finish in 2 weeks. I finished it in 3 days. They were shocked and wanted to hire me for further work.

At another internship there was 4 of us working together as a team. At the end company contacted only ME and told me i showed the best results on their list out of ALL the teams and the team members that were with me.

Ever since i had to study for disgusting college i had to stop working.

Because of college, i have no source of income for MONTHS now.

Because of college, i had several mental breakdowns.

---

To all professors and assistants:

I pray that karma ruins your life with lethal outcome, and your kids die of cancer in pain.

Why is Teams such a pile of shit? Slows my machine to a crawl and makes my fan go nuts whenever I'm on a call, has never heard of UX when it comes to chats and channels, and for some unknown fucking reason uses entirely different device config for livestreams.

Fuck you Microsoft. Only you could develop such a bloated, ugly abomination.

I don't scream because my teams are in a different country and we communicate by IM and email.

I do write long ranting/passive-aggressive emails or type really quick replies when I'm pissed though. .

An example of the latter:

Boss: I need you to make a "quick" fix...
Me: hmm ok sounds like we should implement it like ...
Boss: I was thinking something like this... since it's a temp fix
Need: (typing faster) why is it a temp fix... why not builds it properly so it can be reused
Boss: but that takes time, this is quicker
Me: it's bad design because ... (Typing so fast I'm making typos)... Anyway I can do it. This is better...
Boss: ... ok fine... if you can finish it before deadline

Working on an Android app for a client who has a dev team that is developing a web app in with ember js / rails. These folks are "in charge" of the endpoints our app needs to function. Now as a native developer, I'm not a hater of a web apps way of doing things but with this particular app their dev teams seems to think that all programming languages can parse json as dynamically as javascript...

Exhibit A:

- Sample Endpoint Documentation
* GetImportantInfo
* Params: $id // id of info to get details of
* Endpoint: get-info/$id
* Method: GET
* Entity Return {SampleInfoModel}

- Example API calls in desktop REST client
* get-info/1
- response
{
"a" : 0,
"b" : false,
"c" : null
}
* get-info/2
- response
{
"a" : [null, "random date stamp"],
"b" : 3.14,
"c" : {
"z" : false,
"y" : 0.5
}
}
* get-info/3
- response
{
"a" : "false" // yes as a string
"b" : "yellow"
"c" : 1.75
}

Look, I get that js and ruby have dynamic types and a string can become a float can become a Boolean can become a cat can become an anvil. But that mess is very difficult to parse and make sense of in a stack that relies on static types.

After writing a million switch statements with cases like "is Float" or "is String" from kotlin's Any type // alias for java.Object, I throw my hands in the air and tell my boss we need to get on the phone with these folks. He agrees and we schedules a day that their main developer can come to our shop to "show us the ropes".

So the day comes and this guy shows up with his mac book pro and skinny jeans. We begin showing him the different data types coming back and explain how its bad for performance and can lead to bugs in the future if the model structure changes between different call params. He matter of factually has an epiphany and exclaims "OHHHHHH! I got you covered dawg!" and begins click clacking on his laptop to make sense of it all. We decide not to disturb him any more so he can keep working.

3 hours goes by...

He burst out of our conference room shouting "I am the greatest coder in the world! There's no problem I can't solve! Test it now!"

Weary, we begin testing the endpoints in our REST clients....

His magic fix, every single response is a quoted string of json:

example:
- old response
{
"foo" : "bar"
}
- new "improved" response
"{ \"foo\" : \"bar\" }"

smh....

I don't profess to know the whole story, but what is it with the (what seems to me to be) overly-fragile, cry-bully mentality of the Node.js community and its various branches? The current mess is not the first time strongly opinioned, overly zealous loud-mouths have driven the ship.

Throughout the history of time, teams/groups of people have been made up of different characters. Some are nice, some aren't really and everyone has varied characteristics. There seems to be a drive to completely flatten the behaviour, beliefs and attitudes of any sort of gathering, and it makes me so mad. Some people are so obsessed with their ideas of equality, diversity, inclusivity and safe spaces that they can't see how negative and discriminating those attitudes actually are.

I fully accept that certain behaviours should not be tolerated and should be called out. And communities and societies will organically decide what those are.

But when you raise an issue, approach it like grown up and thrash it out to a resolution - don't throw your toys out of the pram and put on a real public show, targeting and scapegoating other individuals when you don't get your way! This is childish and narcissistic. If this is your only course of action, you should realise you haven't a strong argument.

I've ranted here before about how the mainly social media discussions on any subject drive us all to extreme ends. And this is just another example. It's wrong and narrow minded and not remotely progressive - the opposite of what those who should loudest claim to be.

Storytime!

(I just posted this in a shorter form as a comment but wanted to write it as a post too)

TL;DR, smarts are important, but so is how you work.

My first 'real' job was a lucky break in the .com era working tech support. This was pretty high end / professional / well respected and really well paid work.

I've never been a super fast learner, I was HORRIBLE in school. I was not a good student until I was ~40 (and then I loved it, but no longer have the time :( )

At work I really felt like so many folks around me did a better job / knew more than me. And straight up I know that was true. I was competent, but I was not the best by far.

However .... when things got ugly, I got assigned to the big cases. Particularly when I transferred to a group that dealt with some fancy smancy networking equipment.

The reason I was assigned? Engineering (another department) asked I be assigned. Even when it would take me a while to pickup the case and catch up on what was going on, they wanted the super smart tech support guys off the case, and me on it.

At first this was a bit perplexing as this engineering team were some ultra smart guys, custom chip designers, great education, and guys you could almost see were running a mental simulation of the chip as you described what you observed on the network...

What was also amusing was how ego-less these guys seemed to be (I don't pretend to know if they really were). I knew for a fact that recruiting teams tried to recruit some of these guys for years from other companies before they'd jump ship from one company to the next ... and yet when I met them in person it was like some random meeting on the street (there's a whole other story there that I wish I understood more about Indian Americans (many of them) and American engineers treat status / behave).

I eventually figured out that the reason I was assigned / requested was simple:

1. Support management couldn't refuse, in fact several valley managers very much didn't like me / did not want to give me those cases .... but nobody could refuse the almighty ASIC engineers. No joke, ASIC engineers requests were all but handed down on stone tablets and smote any idols you might have.

2. The engineers trusted me. It was that simple.

They liked to read my notes before going into a meeting / high pressure conference call. I could tell from talking to them on the phone (I was remote) if their mental model was seizing up, or if they just wanted more data, and we could have quick and effective conversations before meetings ;)

I always qualified my answers. If I didn't know I said so (this was HUGE) and I would go find out. In fact my notes often included a list of unknowns (I knew they'd ask), and a list of questions I had sent to / pending for the customer.

The super smart tech support guys, they had egos, didn't want to say they didn't know, and they'd send eng down the rabbit hole. Truth be told most of what the smarter than me tech support guy's knew was memorization. I don't want to sound like I'm knocking that because for the most part memorization would quickly solve a good chunk of tech support calls for sure... no question those guys solved problems. I wish I was able to memorize like those guys.

But memorization did NOT help anyone solve off the wall bugs, sort of emergent behavior, recognize patterns (network traffic and bugs all have patterns / smells). Memorization also wouldn't lead you to the right path to finding ANYTHING new / new methods to find things that you don't anticipate.

In fact relying on memorization like some support folks did meant that they often assumed that if bit 1 was on... they couldn't imagine what would happen if that didn't work, even if they saw a problem where ... bro obviously bit 1 is on but that thing ain't happening, that means A, B, C.

Being careful, asking questions, making lists of what you know / don't know, iterating LOGICALLY (for the love of god change one thing at a time). That's how you solved big problems I found.

Sometimes your skills aren't super smarts, super flashy code, sometimes, knowing every method off the top of your head, sometimes you can excel just being more careful, thinking different.

I AM IN RAGE !!! MY MANAGER IS A FUCKIN SNAKE ASSHOLE!

FUCKER RATED ME 3/5 !
i feel like destroying my laptop and putting my papers right away. this is absolute shit hole of a company where corporste bullshit and multi level hierarchy runs the system, ass licking is the norm and still me, a lowly sde dev 1 was giving my 200% covering their bullshit to deliver outputs on time.

let me tell you some stats.

- our app has grown by 2x installs and 5x mau.

- only 3 devs worked on the app. the other 2 can vouch for my competence.

- we were handled an app with ugliest possible code full of duplication, random bugs and sudden ANRs. we improved the app to a good level of working

- my manager/tl is such a crappy person that if asked about a feature out of random, he will reply "huh?" and will need 2 mins to tell anything about it.

- there is so much dependency with other teams and they want us to talk to them personally. like hell i care why backend is giving wrong responses. but i cared, i gpt so good handling all these shit that people would directly contact me instead of himal and i would contact them. all work was getting done coz 1 stupid fellow was spending 90% of his time in coordinations

- i don't even know how to work with incompetence. my focus is : to do my task, fix anything that is broken that will relate to my task in any way and gather all the stuff needed to complete my task

i am done. i cannot change this company because its name is good and i am already feeling guilty about switching my previous jobs in 1 year but this is painful.

in my first company i happily took a 10% hike coz i was out of college and still learning.
in my 2nd company, i left due to change in policies ( they went from wfh to wfo and they were in a different state) , but even while leaving they gave a nice 30% hike
in my current company idk wjat the no. 3 equates to , but its extremely frustrating knowing a QA who was so incompetent, he nearly costed us a DDOS got the same rating as me

------
PS : GIVE ME TIPS ON HOW TO BE INCOMPETENT WITHOUT GETTING CAUGHT

2 hour meeting to brainstorm ideas to improve our system health monitoring (logging, alerting, monitoring, and metrics)

Never got past the alerting part. Piss poor excuses for human being managers kept 'blaming' our logging infrastructure for allowing them to log exceptions as 'Warnings', purposely by-passing the alerting system.

Then the d-head tried to 'educate' everyone the difference between error and exception …frack-wad…the difference isn't philosophical…shut up.

The B manager kept referring to our old logging system (like we stopped using it 5 years ago) and if it were written correctly, the legacy code would be easier to migrate. Fracking lying B….shut the frack up.

The fracking idiots then wanted to add direct-bypass of the alerting system (I purposely made the code to bypass alerting painful to write)

Mgr1: "The only way this will work is if you, by default, allow errors to bypass the alerting system. When all of our code is migrated, we'll change a config or something to enable alerting. That shouldn't be too hard."
Me: "Not going to happen. I made by-passing the alert system painful on purpose. If I make it easy, you'll never go back and change code."
Mgr2: "Oh, yes we will. Just mark that method as obsolete. That way, it will force us to fix the code."
Me: "The by-pass method is already obsolete and the teams are already ignoring the build warnings."
Mgr1: "No, that is not correct. We have a process to fix all build warnings related to obsolete methods."
Mgr2: "Yes. It won't be like the old system. We just never had time to go back and fix that code."
Me: "The method has been obsolete for almost a year. If your teams haven't fixed their code by now, it's not going to be fixed."
Mgr1: "You're expecting everything to be changed in one day. Our code base is way too big and there are too many changes to make. All we are asking for is a simple change that will give us the time we need to make the system better. We all want to make the system better…right?"
Me: "We made the changes to the core system over two years ago, and we had this same conversation, remember? If your team hasn't made any changes by now, they aren't going to. The only way they will change code to the new standard is if we make the old way painful. Sorry, that's the truth."
Mgr2: "Why did we make changes to the logging system? Why weren't any of us involved? If there were going to be all these changes, our team should have been part of the process."
Me: "You were and declined every meeting and every attempt to include your area. Considering the massive amount of infrastructure changes there was zero code changes required by your team. The new system simply worked. You can't take advantage of the new features which is why we're here today. I'm here to offer my help in any way I can with the transition."
Mgr1: "The new logging doesn't support logging of the different web page areas. Until you can make that change, we can't begin changing our code."
Me: "Logging properties is just a name+value pair dictionary. All you need to do is standardize on a name and how you add it to the collection."
Mgr2: "So, it's not a standard field? How difficult would it be to change the core assembly? This has to be standard across all our areas and shouldn't be up to the developers to type in anything they want."
- Frack wads smile and nod to each other like fracking chickens in a feeding frenzy
Me: "It can, but what will you call this property? What controls its value?"
- The look I got from both the d-bags I could tell a blood vessel popped.
Mgr1: "Oh…um….I don't know…Area? Yea … Area."
Mgr2: "Um…that's not specific enough. How about Page?"
Mgr1: "Well, pages can cross different areas, and areas cross different pages…what do you think?"
Me: "Don't know, don't care. It's up to you. I just need a name."
Mgr2: "Modules! Our MVC framework is broken up in Modules."
DevMgr: "We already have a field for Module. It's how we're segmenting the different business processes"
Mgr1: "Doesn't matter, we'll come up with a name later. Until then, we won't make any changes until there is a name."
DevMgr: "So what did we accomplish?"
Me: "That we need to review the web's logging and alerting process and make sure we're capturing errors being hidden as warnings."
Mgr1: "Nooo….we didn't accomplish anything. This meeting had no agenda and no purpose. We should have been included in the logging process changes from day one."
Mgr2: "I agree, I'm not sure why we're here"
Me: "This was a brainstorming meeting as listed in the agenda. We've accomplished 2 of the 4 items. I think we've established your commitment to making the system better. Thank you all for coming."

- Mgr1 and 2 left without looking at me or saying a word.

Yesterday, my team had a react crash-course workshop.
It was like "you have to import a couple of libs, use 'em in different react elements you pull up and Tadaaaa! Magic is happening and your app works".
This workshop was the pinnacle of "intense".

I understood 60% of the stuff.
My team-mates about 15%.

So react is the front-end technology of choice after our architectural-team. The other teams have to use this the technology for their UIs.
This will be a lot of fun ^^

Asked to implement a feature in a mobile app that wasn't actually supported by the backend. Feature had 3 possible values in the backend, only 1 and 2 were properly implemented. Below was the backend teams solution to support the third option.

- If the key is missing in API response A, means the user is not allowed access this feature.
- If the key is present in API response A, and missing from API response B, that means it hasn't been set.
- If both are the same value, user has that value.
- It will never be the case that both return option 3.
- If both are different values, one of them being option 3, display option 3.

this ... monstrosity, is in production to this very day.

I am so sick of a senior developer that has no idea how to be a manager. I've been a manager before and it is not that hard. I came into this job thinking that it was going to be a fresh start, but instead all the haunting projects from incompetent developers that worked before me followed me to this team as well... (we are in the same company, just different teams) My boss thinks I'm an "expert" in everything, and everyone else on the team has no idea what is going on. I have to spend all of my time babysitting every other developer, and I don't get any coding done myself, yet I'm still expected to make my deadlines.

I need a new gig so bad I'm sick. The stress level is getting pretty bad. I've already had cancer once. I don't want to go through it again... Plz hlp

Well... instead of imposter syndrome I think I have something more alike "I can't fucking tell if I'm smarter than everyone around me or if I'm so dumb I have no clue what's going on"-syndrome.
And trying to be rational, I usually consider the second option to be more probabile... right?
Or maybe, the way my brain processes things is just so different from the people I know that It creates a layer of incomunicability, so that others can't understand my reasoning as much as I can't understand theirs.
The usual speaking-through-jargon-all-the-time trend I've encountered is also not helping.
So I strive daily to align myself to what's going on, trying not to slow anybody down, but that drains my mental energies so much I end up getting done so little... and then I realize _everybody_ has done a similar amount of work.
Are maybe my standards too high?
Or it's normal for teamwork to slow everybody down THIS much?

I used to work much better alone, or in teams with proper separation of tasks between people. Like - we agree on a common interface and then everybody goes his own way implementing his part, and as long as the contract is respected and nothing breaks, nobody cares about what's inside the boxes.

But I don't see it coming again anytime soon, and people seem to have an averagely-good opinion of my work. So well, if I get paid and things cruise along fine, there should be nothing to complain about.

Shit, I've let my flow of consciousness out.

My companies org is in a serious state of disrepair when it comes to project management.

Everything is tracked via conference. Each level of management (CTO, EVP, SVP, BP, S DIRECTOR, DIRECTOR, S MANAGER, MANAGER) all have a different tracking page that all say slightly different things.

To organize things there's a technical project manager who isn't just new to the team, he's new to the field. He's not technical, or experienced in project management. He's never worked within a scrum before.

He's dictating how to organize the teams scrum, and he's getting it very wrong. Decided to organize efforts in all the confluence pages by creating another one for him, again it's different.

When the work in confluence page 3/16 isn't done by a due date anybody knew about, the engineers have to hop on a call and get a Micky mouse solution out the door by the of day so upper management doesn't think the projects off the rails.

In the mean time I've taken a small group of more junior devs and shielding them. We have a side scrum that we manage and is going great, and I'm blocking the BS.

CORPORATE SUCKS. Golden handcuffs are a thing. I might set sail for greener pastures once i don't have to pay back my signing bonus if I leave.

This is more of a story than a rant, but it has some rant-ey elements, so whetever...

I work for a pretty big company. Several departments, teams, many different markets...so it's a big orchestration. The programming department (aprox. 5% of all employees) is the core of the whole company, because everybody else uses software we've written...(a bit off topic, the point is there are a lot of people)

So today, I got assigned with a side-project. The project spec arrives, and as I read through it, I start realizing that upper-management whats me to build an app to fire people instead for them. The app is supposed to track salary, connect with Trello (for departments that use it) to track finished tasks, track sick days, work attendence...a lot of stuff, and at the end, if the situation requires, spit out a person that is of least benefit to the company, to be fired...

Now from coding perspective, this will be very interesting and fun to build, but from a moral standpoint, I'm a bit woried...simply because, indirectly, I'm firing those people. Because, the way I tune the the app(specifically the algorithm that weighs the value of an employee to the company) will cause certain people to get fired...

So I'm woried I'm gonna have a small breakdown when the app goes live and I see someone saying goodbye to theie colegues of something similar...heck, the app might even spit out my name some day(I should probably add a tiny if statement somewhere in there :) )
What do you guys think about this, from a moral standpoint? Would you be okay with building something like this?

(Sorry for the long post :/ )

There is an "SA" who doesn't know anything about different architectures used around, does not ask if he doesn't know and assumes stuff and puts us in those cringe-worthy moments where everyone in the meeting kind of becomes quiet because he is uttering obvious bullshit. He does this in meetings with senior managers and developers from other teams which clearly puts our team down!

Working at a different company for a few weeks before getting back to my usual work.
I'm using everything I hate: ReactJS, factories, style through JS, Jira, Teams, TDD...

The only good thing is I'm using TypeScript...

One of our team mates is based out of the US office. We are physically distant, but after our manager's departure, we lost touch because our scope of work was different.

Me and two other team members work closely with each other from India and dude is alone, working out of the US.

Super smart, very polite, and a fun person to work and be with. Even when our interaction was less, I learnt so much from him.

Since, I am facing some challenges, I decide to use it as an excuse to connect with him for a coffee and also seek his guidance because he is senior to me.

Some things he mentioned,

1. Our new line manager asks him to do things on spot with no heads up. He has to drop everything and complete the ask.

2. Often times, poor guy, is asked to join meetings on immediate basis. Even while he is having his lunch.

3. He never got support from our new manager. Infact, based on the conversation, I realised that the manager supports me more.

4. He is facing same, if not more, issues with tech. And he didn't have any guidance on how to handle the issue.

5. A lot of times he is facing process and system problems which he isn't able to solve because the org culture is that of working in Silos. And he doesn't get any support from manager.

6. Tech has clearly pushed him back when he asked for help and other teams never respond to him.

My man was still smiling bright and was looking things from a positive lens that all of this is interesting and adds to the learning experience which will be valued when we decide to move on from this job.

These are the people who inspire me. Smiling in the time of adversity.

Even when he had his own challenges, he was ready to guide me and hear my frustrations. I offered him help and will make sure to stay connected so he doesn't feel left out and alone in the team only because we don't work together in physical space.

One thing I have learned over time is, while I am facing problems, someone out there is facing more and difficult problems then me. I always tend to blow up my problems out of proportion then what they actually are.

I am the dumbest person that I know and mark my words, I'll die because of my empathy. I wish I could help my team mate in any possible way.

Today I had a full-day job interview for a junior data scientist position.

First I met the team which was only like half of everyone because apparently everyone was gone on Fridays. However the few there were really nice.

First task is to do some basic data analysis stuff even though I already spent a week on the coding challenge and sent them all my code/tasks. I log into my machine and create a new virtual environment but can't for the life of me figure out how to use the command line in windows to install packages. Turns out there is some problem with their proxy and they have to log me in on that. Then I am struggling on the keyboard because it's for a language different that my mother tongue and it takes me 3x as long to so the most simple things. All my shortcuts are out the window. Haven't a hard time typing parentheses and brackets. Start freaking out and have a panic attack mid task. I'm sweating bullets. I didn't even make it to the simple visualization tasks much less the models at the end. Time gets called and we all go to lunch and I'm freaking out on the inside the entire time. Angry at myself because I know I am better and just couldn't think.

After lunch I present my code and results from a coding challenge I did weeks prior. People from other teams get invited and I end up getting grilled for 2 hours by 15 people. Questions are flying in from all sides. They ask me almost everything I know about machine learning and some more. Under stress I forgot the name of the optimizer I used and couldn't answer some easy stuff because my mind was racing.

Right now I am on the train home and my body physically hurts. I am disappointed with myself and wish I could have shown up better. Never really froze up like this before.

Seriously guys, how do you deal when remotely collaborating with lets say not the most motivated and competent devs?

Our scrum team got formed about 6 months ago from leftover devs of other teams, choosing a couple competent devs at the core and other devs who were kinda gotten rid of by their old teams, and after 6 months of working together I can see why.

Situation is that we are 7 devs in our team and 4 of devs are not pulling their weight. They are seniors on paper, but in reality not really.

They rarely take something complex to work on and even if they do, they make sure they take as much time as possible. Two of them are contractors who I imagine decided to treat the job as a paycheck and nothing more. There is no initiative, no push to make things better and in general attitude is to do bare minimum: only what is being asked and then delaying the hell out of tasks.

Im not exaggareting: Im talking about every possible way of dragging out the tasks: delaying communication, sitting around for a few days while not asking for new tasks to work on if they are blocked, also avoiding standups. Working for days on very basic comments in their MR's. Getting "sick" for a couple days on deadline when things get tough, so that someone else would come in, refactor and save the day. Once or twice it could be a coincidence, but nowadays I can already guess ahead of time what kind of trick they will pull now.

Our project is an android app where we have to support few different tablets, so the most recent new trick that I witnessed is devs avoiding hardware delivers, sometimes for months. Idea seems to be if you dont ping your team that you dont have hardware, then you can avoid working on related tasks with that hardware.

Worst part is that they get away with it. Our teamlead is a senior dev who is first time teamlead, doesnt code anymore and doesnt want to rock the boat. He is the type of teamlead who sets arbitrary deadlines, makes it sound that they are urgent and takes a few days off in the middle of chaos just before deadline. Restrospectives don't help at all and if I try to bring up stuff directly to him he tells me to bring it up during retrospectives. We discuss issues, rant a bit ant then continue carying on like nothing happened and nothing changes.

So little by little in the past 6 months we came to this point where 2-3 devs are carrying the weight of the team and are in a constant crunch mode, while others are allowed to slack. Its becoming ridiculous.

Problem is that this is starting to affect our morale. Only way that is left to keep my sanity right now is to pull away sometimes and also slack. Then I come back at full capacity, give my best for a couple weeks until I have to go and fix some basic leftover task that has been purposefully dragged out for 2 months and left unfinished, then I just want to scream and I know that its time to disconnect again.

TL;DR: This year I changed job to a quite toxic company and because I have to work for two different clients in parallel I'm burning out. I need suggestions about telling about my mental health to my employer or request to change clients because of their incompatibility

----

At the begin of this year I changed work from a small startup (which was nice, but they didn't pay very much) to a consulting company and since then I'm experiencing my first burnout.

Just to give some context, the first month or two months in this new position were nice: the project I've been put on was difficult, but the other people in the team were very kind and helped me navigate through the codebase. After there quiet months, I've been put on a second project (in parallel with the first one), same domain but different client and the two clients must not know that I work for other clients. This doesn't work particularly well because both of the clients require me a full--time presence and both the teams have the tendency to call you without any warning and without setting up a meeting on calendar and beacuse of this I pass 3/4 of my day on such useless meetings (which many of them I have to be present at the same time, and sometimes one meeting is in English and one in Italian) without getting any job done and now both my leads are getting frustrated by my delays.

To make it all worse, when I was contacted from the headhunter it was for a mobile developer position, but because of my previous position my employer thought that I could temporary work on one java project because there was scarcity of developers and I could be a nice fit.

I'm not sure if I sum up my situation clearly of it's confused (I'm sorry about that), but tomorrow I plan to call my employer to tell him that I can't take it anymore and something has to change, I just don't know if I should put it on the incompatibility of the two clients, my mental health or both

During the course of my career I've stumbled on like 6-7 people I've worked with and it was really great. Every now and then we meet up and chat how it'd be great to form a team again and work on something (we're all in different companies atm).

Lately we've been mentioning that even more and are considering whether to start working on a product/find clients and form an agency/join some other company.

We have experience with both outsource and products. Our profiles range from development, design, marketing, UX, HR, PM.

Any road we take has pros and cons. We're least fit to start on a product because we'd need more profiles, have to figure out finance and would probably have to work alongside our current jobs.

I've been thinking of writing a joint letter when I hear a company is opening up an office in our city. When that happens, usually whole teams are formed and most of the profiles I mentioned are needed.

Do you think that's even possible? Is there another way we're overseeing? Have you heard of or attempted something similar?

Any advice is truly appreciated.

This Pull Requests requires code reviews from four different teams, and most people in those teams are in timezones where they're already off work and I just started. 😩

My programming paradigms unit has decided to explore different teaching/learning environments by creating lecture/workshops. Imagine a massive room with big projector screens at the front and smaller screens lined up against the wall at the back. The lecture room seats are designed around tables that are gradually elevated so it’s similar to a lecture hall but you’re sitting at discussion tables.

There’s the usual lecture with all the slides up around everywhere, there’s nice wheelie chairs and dimmer lighting... can’t tell if we’re at a conference or some awards night. Then all of a sudden, we’re coding in teams (tables) and uploading our work on to forums to discuss with the rest of the lecture hall. WHAAAAAAAT

Really different and quite enjoyable experience, there’s more than one tutor walking around to help, there’s mics for people to present.

Just sharing my new experience of forward learning environments that didn’t cause feelings of anxiousness for once or boredom. It was kind of mind blowing, wish it was always like this.

when you go through 3 different teams and nobody can explain why a certain item is linked to a subscription and there's no linking row in any of the usual database tables

fml

Ok so I love being a programmer, but I've been programming for about 6-7 years now and to this day, have nothing to show for it.

I hate that I'm a no compromise sort of person but it means I just can't settle for something, I want to deliver a flawless and engaging product with plenty of polished features, but I'm 1 person trying to do what teams of devs do.

I even have a couple programmer friends that a couple years ago were begging to collaborate with me for there project but as soon as I ask them about collaborating they suddenly have a different view -,-

What do you guys do when motivation and moral starts wearing thin? :-/
Not having anything get completed is really bringing me down!

Story of my first successful project

Being part of a great team, I've shared in a lot of successes, one I am particularly proud of is my first attempt to use agile methodologies in a deeply waterfall-managment culture.

Time was June/July-ish and we applied for a national quality award where one key element in the application stated how well we handled customer complaint resolution.
While somewhat true (our customer service is the top-shelf good stuff), we did not have a systematic process in resolving customer complaints. Long story short,
the VP lied on her section of the application. Then came the 'emergency', borderline panic meeting (several VPs, managers, etc) to develop a process to better manage
complaints before the in-house inspection in December.
As most top priority projects go, the dev manager allocated 3 developers, 2 DBAs, and any/all network admins we would need (plus all the bureaucratic management that wanted their thumb in the pie).
Fast forward to August, after many, many planning meetings, lost interest, new shiny bouncing balls, I was the only one left on the project. The VP runs into the dev manager in the hallway and asks "Is my program done yet? If its not ready before December with report-able data, we will not win the award."
The <bleep> hit the fan...dev manager comes by...
Frank: "How the application coming along? Almost done?"
Me:"No, haven't really started coding. You moved Jake and Tom over to James's team, Tina quit, and you've had me sidetracked helping other teams because the DBAs are too busy."
Frank: "So, it's excuses. You really think the national quality award auditors care about your excuses? The specification design document has been done for months. This is unacceptable."
Me: "The VP finished up her section yesterday and according to the process, we can't start coding until the document is signed off."
Frank: "Holy f<bleep>ing sh<bleep>t! No one told you *you* couldn't start. You know how to create tables and write code."
Me: "There is no specification to write to. The design document is all about how they plan on reporting the data, not how call agents will be using the application to serve customers."
Frank: "The f<bleep> it isn't. F<bleep>ing monkeys could code against that specification, I helped write it! NO MORE F<bleep>ING EXCUSES! This is your top priority from now on!"

I was 'cleared' to work directly with the call center manager and the VP to develop a fully integrated customer complaint management system before December (by-passing any of the waterfall processes that would get in the way).

I had heard about this 'agile' stuff, attended a few conference tracks on the subject, read the manifesto, and thought "I could do this.".

Over the next month, I had my own 'sprints' and 'scrums' with the manager (at the time, 'agile' was a dirty word so I had to be careful of my words and what info I shared) and by the 2nd iteration had a working prototype.
Feature here, feature there (documenting the 'whys' and 'whats' along the way), and by October, had a full deployed application.

Not thinking I would get a parade or anything, the dev manager came back from a meeting where the VP was showing off the new app to the other VPs (and how she didn't really 'lie' on the application)

Frank: "Everyone is pleased how well the project turned out, except one thing. Erin said you bothered him too much with too many questions."
Me: "Bothered? Did he really say that?"
Frank: "No, not directly, but he said you would stop by his office every day to show him your progress and if he needed you to change anything. You shouldn't have done that."
Me: "Erin really seemed to like the continuous feedback. What we have now is very different than what we started with."
Frank: "Yes, probably because you kept bothering him and not following the specification document. That is why we spend so much time up front in design is so we don't waste management's time, which is exactly what you did."
Me: "We beat the deadline by two months, so I don't think I wasted anyone's time. In fact, this is kind of a big win for us, right?"
Frank: "Not really. There was breakdown in the process. We need better focus on the process, not in these one-hit-wonders."

End the end, the company won the award (mgmt team got to meet the vice president, yes the #2 guy). I know I played a very small, somewhat insignificant role in that victory, I was extremely proud to be part of the team.

My company boss wants to reorganise the team structures drastically.

Currently we have different teams for each product. And in that team we have a lead, frontend and backend developers working in sync.

The boss wants to split the teams not based on product.. but based on technology / frontend backend. Then assign the members to products based on demand.

Not sure how that is gonna turn out..

One of the guys were tasked to implement a button with a functionality.
When I clicked the button, I got an error. Asked the guy why, and he said that fixing the functionality was not part of the task. What? So basically he just put a nice little button that does nothing? And our team lead just approved his merge request?!
I can't comprehend this logic at all.

Another story, I overheard a different guy debugging a pointer array (C++) with a senior. I couldn't keep my face straight when he seems to struggle to dereference a pointer and iterating through an array. He can't do that and he calls himself a mid-level engineer?!

The more I stay in this company, the more I realize that many people in my teams are clowns.

Anybody have tips on surviving a company restructuring where your team could get split and members+manager shuffled to different teams?

Besides looking for another job, since you might as well try to get a raise by jumping ship.

The sheer amount of information to be gained in this field, and in my case specifically at my job, is mind boggling. Maybe it's just the week of fatigue talking here but I feel I'm way in over my head. Learning business, teamwork, development strategies, progress tracking, the code base itself, how different teams work together, how different sectors work together, overarching goals, individual goals, and then going home and having a social life, good nights rest, and somehow exercise in there?

It's certainly overwhelming. I know being new makes it seem worse than it likely is but I don't see how people even manage to amass so much knowledge in such a short amount of time. It's honestly so exhausting to keep track of everything and try not to make mistakes that it's nauseating. I'm still gonna try but good lord does it feel impossible.

Our team moved to scrum a while back. But everybody still does story point estimation by mentally assigning 1 story point for each day of work it would require. :/
On top of that, management compares the performance of two *different* scrum teams based on the story points they finish in a sprint. ://

Just got an Android app project from friends, but already have a bad feeling about it.

It already start with 11 freaking screen, an input activity with 17 field(include spinners, date picker, location picker, and a freaking table). 3 different account type, each has different item and function visible to the user. 5 main feature, one of it include *chat* that supports multimedia, A freaking alarm system, both scheduled and automatic based on certain parameter with push notification, and deadline at January 1st with teams of 3 people :)

So it’s promotion season in my org and once again I got passed up. Manager says “you’re right there just a little bit longer” but he’s been saying that for the better part of a year. I’ve consistently done the job not in my job description but the job of the position above me. Some of my senior engineers and staff engineers have told me personally that they are shocked that I haven’t been promoted yet. And I know I should be patient but hearing other people (albeit in different teams) get recognized when you work just as hard if not harder than they do, and you go to conferences and you volunteer to be on call and you lead meetings and when you’re one of the technical anchors of the team… I don’t know. I shouldn’t take it personally I get it but it’s a huge blow to my confidence and my mental health. I work hard and when I see news like this I work harder and get burned out and when I still see news like this it makes me work even harder and get even more burnt out until I reach a mental breaking point. Makes me feel like I’ll never be good enough.

Idk.

Currently on a project to use AI as music recommending model, an interactive AI model generator and researching on Distributed Systems altogether in three different teams for each thing...

Seems I'm the dirty fish of their team.. 😖

Fucking wasting the time all along the day...

Like Why the Fuck am I degrading my own potential, quality and what not...

Oh god Fucking pick me to the hell NOWWW

Worst project I worked on was fixing up and optimizing a clients legacy Magento app. this thing had leftover code from a few different development teams, and then my company had to make it run better. We outsourced much of it, and it wasn't using a proper git setup. in order to do absorb at all, we had to SSH to a dev server, work directly, and pray another person on the team want working on the same file or breaking something else.

So I have to mimic some codes that I was not given any explanation because it's from a team that is, like, the only one that does not like the others and we have to work with them.

All the teams do codes with similar coding rules
and then there is this team. Weirdly enough, they are the most strict on their rules.

Why are non-technical people put in charge of technical people? I get there's a stereotype that programmers aren't good with people, but that's not really my experience. How can I fail to achieve expectations when you don't outline any? How is "I didn't see you run enough scripts" a valid criticism when they're run locally from my machine with no record being created? Especially when those scripts are only for very specific processes I generally don't deal with? Seriously I was on the team less than 5 months come my yearly review and I'm already under-performing? I can't even switch teams because in-house recruiters always request the last performance review and mine sucks thanks to that asshole. Nevermind the one before that I excelled, but different role doesn't matter I guess. Some days I'm so tempted to cash out that 401k and just hope I find a better job within a year. Anyone have advice on dealing with this shit?

I have done it!

I have discovered my biggest irritant when it comes to the tech world and that is fragmentation and visual disorganisation and once again, Microsoft and Google are the fucking worst for it, all applications have different design languages in play, their OS's are disjointed (Chrome OS shits me just because of how much android is leaking in yet they refuse to use similar navigation and the like)...

Apple did it right, oh we are redesigning our mobile platform and desktop platform at the same time, oh I know! Let's make them follow the same fucking design...

I'm just some random 20 year old and have so many ideas that almost everyone will agree make both teams products so much user appealing -,-

We have procedures in place, but nothing has been Enacted as of yet other than travel bans and inter division meeting. Pushing for all meetings to be phone or web. Day to day team internals have not been affected yet. There is discussion to split the teams up so not everyone in the office is at the office at the same time. Split via “shifts” so different project groups would work during different shifts to reduce contact with others. And then also working from home, some like it , I don’t because all my stuff I need is at the office, and the internet at my house isn’t capable of what I need. So the shifting works best for me. Kinda nice I like the 3rd shift option for software.

I am having an introspective moment as a junior dev.

I am working in my 3rd company now and have spent the avg amount of time i would spent in a company ( 1- 1.5 years)

I find myself in similar problems and trajectories:

1. The companies i worked for were startups of various scales : an edtech platform, an insurance company (branch of an mnc) and a b2b analytics company

2. These people hire developers based on domain knowledge and not innovative thinking , and expect them to build anything that the PMs deem as growth/engagement worthy ( For eg, i am bad at those memory time optimising programming/ ds/algo, but i can make any kind of android screen/component, so me and people like me get hired here)

3. These people hire new PMs based on expertise in revenue generation and again , not on the basis of innovative thinking, coz most of the time these folks make tickets to experiment with buttons and text colors to increase engagement/growth

4. The system goes into chaos mode soon since their are so many cross operating teams and the PMs running around trying to boss every dev , qa and designer to add their changes in the app.

5. meanwhile due to multiple different teams working on different aspects, their is no common data center with up to date info of all flows, products and features. the product soon becomes a Frankenstein monster.

6. Thus these companies require more and more devs and QAs which are cogs in the system then innovative thinkers . the cogs in the system will simply come, dimwittingly add whatever feature is needed and goto home.

7. the cogs in system which also start taking the pain of tracking the changes and learning about the product itself becomes "load bearing cogs" : i.e the devs with so much knowledge of the product that they can be helpful in every aspect of feature lifecycle .

8. such devs find themselves in no need for proving themselves , in no need for doing innovative work and are simply promoted based on their domain knowledge and impact.

My question is simply this : are we as a dev just destined to be load bearing cogs?

we are doing the work which ideally a manager should be doing, ie maintaining confluence docs with end to end technical as well as business logic info of every feature/flow.

So is that the only definition of a Software Engineer in a technical product?

then how come innovations happen in companies like meta Microsoft google open ai etc?

if i have to guess as a far observer, i would say their diversity in different fields helps them mix and match stuff and lead to innovative stuff.

For eg, the android os team in google has helped add many innovative things in google cloud product and vice versa.

same is with azure and windows . windows is now optomissed to run in cloud machines when at one point it was just a horrible memory hogging and slow pc OS

for small companies, 1 ideology/product/domain is their hero ideology/product/domain .

an insurance company tries to experiment with stuff related to insurances,health,vehicles,and the best innovations they come up with is "lets give user a discount in premium if they do 5000 steps a day for an year".

edtech would say "lets do live streaming for children apart from static videos"

but Android team at google said , "since ai team is doing so well, lets include ai in various system apps and support device level models" ~ a much larger innovation as 2 domains combined to make a product

The small companies are not aiming to be an innovative product, they are just aiming to be a monopoly product. and this is kinda sad

I just joined my company as a fresher in graduate developer, we will be going around in different teams over the course of next 6-7 months. My question is even though i joined as a " software developer" as of yet i am in a performance testing team, is it a good start or should i move to other team like development, QA testing etc ?

Anybody know of any enterprise software for password storage and sharing?

We have an issue where multiple people across different teams use the same accounts and need them to be able to access certain login information but not all login information.

I’m hoping for something free/open source but at this point I’m open to anything. Must have the ability to give users privileges.

I don't want to answer my manager. Each SCRUM, each SPRINT retrospective is becoming so long. Everyone in my team works on different projects, it's no use listening to all that and wait for your turn and on top of that your manager bombards you with the questions that you really know the answers to but he always questions again like give me estimates, like if I haven't ever worked on something how am I supposed to give you the estimates.
My english is just lowering it's standard day by day, I try to think smarter words but no it is sucking bad.
I am not frustrated as I am learning how to see all this as a part of my learning. I am a good developer I know but I haven't worked on code for like 3 months, everything needs to be investigated, contacting the other teams etc. I am just thinking to close on the projects that I have right now and leave.
In 1:1s my manager said something else but in team meeting asked me to do something else.
I haven't coded in more than 2 months even before that it was at least 3 months gap. I want to take leave for a week and work on the code. But fuck it, open source is not allowed in my company. WTH WTH WTH!!!
I switched the company for growth and I definitely did not have any technical growth.

!dev
Assuming your office is not against workplace dating, how would you feel/react if a colleague asks you to a date on Slack?
Scenario 1: you guys work in the same team.
Scenario 2: you guys work in totally different teams.

Just had a memory popup about my uni days about 5 years ago. I was in my Junior year in business school and was doing a "consulting" project involving the whole Class (200 students). Groups of 4 were assigned an international company in either Europe, Asia, or South America. We'd visit them (as well as do some sightseeing) and learn about them (performance, market positions, products) during Spring Break and come up with a real proposal. We would then compete with other teams, and the winning pitchs for each would be presented in the school auditorium in front the entire class.

Our team didn't get that far but that's not the point. We did win the individual classroom competition. Our company was Deutsche Telekom (owner of T-Mobile).

This was in 2010, when the iPhone/smart-phones started to become mainstream... And our team's idea was location-based advertising.

Looking back, we basically predicted the future... though we got the wrong industry...

It's also sort of funny though because I remember the main reason we came up with the idea was to be different.

All other teams just went with some expansion plan to a neighboring country or cutting costs.... pure MBA/business plan. But I guess I was being a natural techie so thought of a tech idea instead.

We had a meeting with our professor after he picked us and he told us he had a history of spotting future hits. We were like "hm... ok... let's give it a shot... we definitely got an A!" but at that point I was sort of skeptical if this would actually work in real-life (the basic idea was they would sell ads to local businesses and if you were nearby, you would get a text message with an offer).

But guess he was pretty right... we just needed to have Google or Facebook to have been our company... though Groupon or Yelp works too... basically a tech company with larger scale rather than a mobile carrier...

I work at a corporation with dozens of different products and different legal units and teams working with different products. As many of the products are business acquisitions and not internally developed, they've retained whatever (cloud) architecture they had to begin with... some hosted on AWS, others on Azure and yet others on GCP.... Yet the core products are all on the same provider's platform, so all the documentation for some unexplainable reason assumes every other product is on that platform, too, and does not take into account interprovider communication problems, so integration becomes a major pain in the arse when the product you're working on (like mine) is not hosted on that one cloud provider's platform... Whole week I've felt like banging my head repeatedly to the wall.

Error reporting. Yeah it is a pain to come up with something that users will understand. As devs we need meaningful stacktraces so we can diagnose the problem but the normal person doesn't care. Also not having consistent messages looks terrible for the user's experience.

I hate it when there is no standardized error messages and/or json structure between teams or individual members of said teams. Why should we have 10+ different structures to code for in our apps? There is RFC 7807 for a reason. It has a defined structure plus accounts for custom properties. If you are a c# developer, check out the ProblemDetails class. It has made my life easier and I can guarantee everyone that all of my team's projects return this structure.

Design in Motion: Real-Time Rendering's Impact on Architecture

Architecture, a discipline that once relied heavily on blueprints, models, and lengthy render times, has undergone a revolutionary transformation in recent years. The advent of real-time rendering technology has fundamentally altered the way architects visualize, present, and interact with their designs. This paradigm shift has not only enhanced the creative process but has also empowered architects to make more informed decisions and create immersive experiences for clients and stakeholders.

Real-time rendering, a technological marvel that harnesses the power of high-performance graphics hardware and advanced software algorithms, allows architects to generate photorealistic visualizations of their designs in a matter of milliseconds. Gone are the days of waiting hours or even days for a single rendering to complete. This acceleration in rendering time has not only expedited the design process but has also encouraged architects to explore multiple design iterations rapidly.

One of the most significant impacts of real-time rendering on architecture is the ability to visualize a design in various lighting conditions and environmental settings. Architects can now instantly switch between daytime and nighttime lighting scenarios, experiment with different materials, and observe how their designs respond to different seasons or weather conditions. This level of dynamic visualization offers insights into how a building's appearance and functionality evolve throughout the day, contributing to more holistic and thoughtful design solutions.

Moreover, real-time rendering has transformed client presentations. Architectural concepts can now be communicated with unprecedented clarity and realism. Clients can virtually walk through spaces, observing intricate details, exploring different angles, and even experiencing the play of light and shadow in real-time. This immersive experience fosters a deeper understanding of the design intent, enabling clients to provide more targeted feedback and make informed decisions.

The impact of real-time rendering on collaboration within architectural teams cannot be overstated. Traditionally, architects and designers would need to wait for a rendering to complete before discussing design changes or improvements. With real-time rendering, team members can make adjustments on the fly, observing the immediate effects of their decisions. This seamless collaboration not only enhances efficiency but also encourages interdisciplinary collaboration as architects, engineers, and other stakeholders can work together in real-time to refine designs.

The integration of virtual reality (VR) and augmented reality (AR) into the architectural workflow is another transformative aspect of real-time rendering. Architects can now create VR environments that allow clients to step inside their designs and explore every nook and cranny. This not only enhances client engagement but also enables architects to identify potential design flaws or spatial issues that might not be apparent in 2D drawings. AR, on the other hand, overlays digital information onto the physical world, facilitating on-site decision-making and construction supervision.

Real-time rendering's impact extends beyond the design phase. It has proven to be a valuable tool for public engagement and community involvement in architectural projects. By creating virtual walkthroughs of proposed structures, architects can offer the public an opportunity to experience the design before construction begins. This transparency fosters a sense of ownership and allows for constructive feedback, contributing to the development of designs that resonate with the community's needs and aspirations.

The environmental implications of real-time rendering are also noteworthy. The ability to visualize designs in various environmental contexts contributes to more sustainable architecture. Architects can assess how natural light interacts with interior spaces, optimizing energy efficiency and reducing the need for artificial lighting during the day.

In conclusion, real-time rendering has ushered in a new era of architectural design, propelling the industry into a realm of dynamic visualization, immersive experiences, and enhanced collaboration. The ability to witness designs in motion, explore different lighting conditions, and interact with virtual environments has redefined how architects approach their craft. From facilitating client presentations to fostering sustainable design solutions, real-time rendering's impact on architecture is profound and multifaceted. As the technology continues to evolve, architects have an unprecedented opportunity to push the boundaries of creativity, efficiency, and sustainability in the built environment.

So my current company held a dev showcase last week. It was an event to show the different projects/tech stacks that different teams are working on/with. There's about 12-14 teams in our company. My team lead and I were brainstorming ideas on what to show on our booth. And I told him, I have an Intel RealSense developer kit that we can use. Anyway, fast forward to the day before the event, I was still developing our app/game for the booth. Just an emotion detector and you have to trick the app with your facial expressions. (Weird and fun, I know). The head honcho walked past the team lead and I and looked over the demo that I was playing around and he said that: "That's not work. You're wasting time again."

We were both irritated by his comments because he's one of the top dogs in the company and he surely knows about the event. Also, it's our way of showing to him that we're flexible in doing fun stuff instead of just enterprise and internal systems!

What a fucking kill joy!

What is the general rule/idea around meetings outside of your work hours?

It has happened several times that I wasn't able to join some meetings that were outside of my work hours. I try to join but some thing or the other comes up and then I miss it. I make sure to join any meeting that's highly important or if it's about anything related to my work (or if I'm required to attend).
I work with people in different time zones and there was a meeting set after 8:30pm my time, and I wasn't able to join. My coworker messaged me, in a passive aggressive way (seemingly), asking if he needs to remind me before every meeting in my calendar so that I would join.

I feel like I'm not being paid enough for the work that I do, and I work around 8-9 hours (sometimes 10 and I don't get paid for overtime).
On top of that, am I obligated to attend every meeting and not have anything planned or unplanned to do after work hours? (I don't think I should have any obligation)
I don't have previous experience of working with international teams/clients before, so I'm not sure what I should do here.

It seems that my barometer for whether I would stay long in a company is roughly 1.5 years. Because apparently that's how long it takes to gauge if:

(a) The work I'm doing is fulfilling or self-satisfying
(b) My colleagues make work a fun and challenging experience
(c) My bosses are people I can be proud to work for.

Right now, the tally thus far:

(a) The work is half crap, supporting old code (fuck Swig and Architect, by the way) or fixing bugs on old projects. New projects are always mismanaged, and I mean ALWAYS (let's do Agile and create tickets but hey the requirements are still in progress so do start anyway and we'll file everything as bug tickets until they're done)

(b) I'm sure it's an effect of going remote working for the last few months, but I'm feeling detached from my team. It's fine I guess.

(c) My manager is okay, he's a good guy who listens and is also technical so we get along. But his boss (who oversees several teams. including ours) is a total prick who loves to insult people at their expense as a joke. He knows nobody's gonna talk smack back so he just does it without repercussions.

I'll probably see if I can move around internally to a different division since the pandemic makes it difficult to find work externally. I'm grateful I have a job, but I shouldn't have to feel like I owe the company for that at the cost of my personal happiness.

Just gotta #survive2020 I suppose.

Tltr: Apperenticeship -> Job -> Promotion -> They pay for my bachelor

So I started my apperenticeship back in July 2014...
After a year of basic training I worked in different teams accros the company.
I finished my apperenticeship june 2018. Two teams offered me permanent positions early in 2018.
The team I decided to join, had a (back theb new) boss and I felt like she would be cool to work with. (I don't know how to describe this more accuratly... I just liked her visions, plans and what she told me about the work).

Fast forward half a year

I was preparing for the meeting where we would discuss my goals.
(I was preparing to ask for raise...)
Then she goes:
- "Hey NeedToRoll, can I have 10 minutes of your time, its serious!"
* "Sure"
- "Do you habe any Idea why I would wonna talk to you"
* "No" Thinking: What did I fuck up that badly
- "I would Like to thank you for your amazing work, and HR agreed to a 10% raise as per next month."
* "Thanks!"

Fast forward to now:
1. I will reducing to a 50% position (per my request)
2. They are paying for my bachelor s degree I am going to get. (Studying part time)

My team works as a growth team. So, I have to start with different documentations from different teams each time I start a project.
The thing is documentation is badly written and you have to dig a lot to find a small thing.
At the same time, culture of the company urges us to go deep before contacting another team.
Each team's documentation is different and some people force on reading the documentation before contacting them. Growing technically has become a lot more challenging me and honestly I don't want to do this anymore.