Starting to wish I never got involved in this industry.

I am working for the most ridiculous, god awful place I have ever had the misfortune of working and I am having a HELL of a time getting out of it because everything wants 5 years fucking exp in some fucking specific framework that is basically the same as every other fucking framework.

Our previous cto was a closeminded totalitarian bully and when she finally left she was replaced by a lecherous fucking dinosaur who has no idea how to code in our code base. He also has barely been showing up to work for the last few months.

For some reason our fucking ceo allows this all to continue and only interjects whenever he can make himself the biggest nuisance (ie design handoffs etc where he has little to no knowledge)

I was already woefully underpaid but was recently 'promoted' to team lead and when I brought up my ridiculous salary (yes I was essentially just funneled into this role) they gave me a neglible raise and ceo told the fucking dinosaur to tell me he 'doesn't like when people ask for raises'

The only reason I am in this position is because we have such ridiculously poor employee retention and I am one of the people after only 2.5 years there that has the ability to provide any kind of knowledge transfer. Most of our dev team consists of people fresh out of school and our code base is just an absolute mess of junior dev spaghetti debauchery.

I have expressed concerns over this and was told that I'm negative and go looking for problems and that 'everywhere is like this'

The ceo has a few people he keeps close because in his words 'they're the only ones who don't disagree with me'

He also refused to hire anyone with experience because they cost too much and he doesn't like people who have opinions.

To make matters worse all the fucking dinosaur does is wander around and talk to the junior devs about video games.

His previous favorite past time was staring at my tits, ranting about his wife and telling me 'he'd offer to give me a back rub but you can't do that now a days'

I caught his fucking wife creeping me on LinkedIn a few months ago for some fucking reason.

Oh and as icing on the cake I had a fucking interview today for an intermediate angular position and a few minutes after I received an email saying that ACCTUALLY they had been informed they were now looking for a senior react dev.

Like seriously what the fuck.

FUCK LINUX

now that I have your attention, and you’re probably angry, too, please, even if you don’t read this rant, never use code.org again. now, onto the rant…

god dammit, code.org sucks. I mean, anyone who created it or associates with it should, well, be considered a terrorist. they’re bombing students futures in computer science with false, useless, bullshit information. not to mention, their sponsors like bill gates, mark zuckerburg, and other rich asses, talk in a video about some boring ass shit that is hard to understand for anyone who doesn’t program, and not to mention, they use a fucking five dollar microphone. ear rape. even if you look at a textual version of it, then read the information on it, it’s practically useless because it's so terribly explained, and also useless. ironically enough, they focus on their animations more than their actual explinations, or their students for that matter. the fact that we had to encode a picture in binary, made me about 50% dumber, give or take a 0 or 1. then, we had to do it in hex, which wasn’t really much better, although more realistic I supposed. what's really the most depressing thing about this class is its application in the real world. I've learnt nothing whatsoever that will help me in the real world, or in computer science. I suppose there's two things that may be useful (that I already knew): hex, and that TCP doesn't lose packets. that's it. those two things. five seconds worth of knowledge from the first quarter of the year. the ideas just make me want to throw up. teaching the main ideas of computer science without actually teaching it? one of the teachers (probably a good one) enrolled her students in an online programming course just so they could understand, because the explanations are just so terrible. this is the only [high school] computer science course offered by code.org, and I signed up because it's an AP computer science class (tried to get into AP Java, the day I was supposed to take the test to get into an upper level class, I was told it didn't count as a tech credit). seriously, fuck code.org. it makes you dumber. their 'app lab' environment is pointless, just like everything else. the app lab is basically where you have a set of commands and have to make a dog bark() or a storm trooper miss() [and that's hell when they haven't introduced while loops yet]. the app lab is literally code.org going out of their way to make everything that their students are learning pointless in the real world. seriously, why can't we just use a <canvas> like an ACTUAL PROGRAMMER would do if they were to make a browser game, not use an app engine so slow it would be faster to update windows and android studio each time I run an 'app' in their 'environment'. their excuse is that the skills "transfer over" to the real world. BITCH! IF I DIDN'T KNOW JAVA, AND I WANTED TO MAKE A GAME IN JAVA, I'M NOT GOING TO LEARN PYTHON, THEN "TRANSFER" THE SKILLS I LEARNT, I'M GOING TO LEARN FUCKING JAVA. AND THAT GOES FOR EVER OTHER LANGUAGE, PROJECT, ETC.

I'm begging you code.org, stop, get help.

Today a new person joined the team.

Started bitching about the entire team for not having documentation for our already written code and software.

Asks the manager for a new task that he can take up so that he can write documentation for all our already coded works.

Manager says Go On.

Troubles me with 400 questions every 3 minutes in the name of Knowledge Transfer for writing his documentation.

Sends a proud mail to the team for writing this new documentation that no one else had time to do.
He is a newbie and had no other task to do anyway.

I seriously don't know if I should feel proud of him, for writing new documentation,
Or if he's doing this to defame me.

The team is filled with snakes.

The management brought some devs from another outsourcing company into our project to overcome the fact that we, the existing developers, are retarded. We are retarded because they change the scope continously (aka daily) and we can’t keep track with their requests. They want something and after we implement it, they want it changed. Completely.

Instead of getting the project and deep dive into it using the materials (setup, architecture etc.) I prepared along the way, their PM said that we have to make some low level knowledge transfer. This knowledge transfer session happened on Friday.

The presenters were me and one of my colleagues. After 2 hours of training, we found out that the supposed senior devs don’t know how to use GIT, they don’t have a clue about Spring nor Angular (nor any SPA framework), their only questions were ‘why didn’t you use X?’ (where X = bootstrap, jQuery etc.) etc.

What is even funnier: during the presentation we were asked to keep a screen sharing opened during working hours for a couple of days just so the new devs could see how we are working.

Guess what happened with the scope on Friday evening: it changed again because ‘you got new devs so there will be multiple resources to handle tasks’.

2 more weeks and i’m out of there...

Today, i have never been embarrassed like this in my life.

I started onboarding sessions with this guy. We were on teams call. It was a knowledge transfer session. Hes explaining how the system works. Then tells me which programs to install.

I was searching through allowed programs to install. Installed notepad++ (who tf uses that in 2024?) Installed snaggit. Then had to install putty. Instead of writing putty i unconsciously without thinking wrote pussy

..............
💀💀💀💀💀💀
😞😞😞😞

he then said "yea you can find that too but not on this website lmfaoooooo🤣😹😹😹😹"

🫥🫥🫥🫥🫥😶‍🌫️😶‍🌫️😶‍🌫️😶‍🌫️😶‍🌫️😶‍🌫️

Please

oh, it got better!

One year ago I got fed up with my daily chores at work and decided to build a robot that does them, and does them better and with higher accuracy than I could ever do (or either of my teammates). So I did it. And since it was my personal initiative, I wasn't given any spare time to work on it. So that leaves gaps between my BAU tasks and personal time after working hours.

Regardless, I spent countless hours building the thing. It's not very large, ~50k LoC, but for a single person with very little time, it's quite a project to make.

The result is a pure-Java slack-bot and a REST API that's utilized by the bot. The bot knows how to parse natural language, how to reply responses in human-friendly format and how to shout out errors in human-friendly manner. Also supports conversation contexts (e.g. asks for additional details if needed before starting some task), and some other bells and whistles. It's a pretty cool automaton with a human-friendly human-like UI.

A year goes by. Management decides that another team should take this project over. Well okay, they are the client, the code is technically theirs.

The team asks me to do the knowledge transfer. Sounds reasonable. Okay.. I'll do it. It's my baby, you are taking it over - sure, I'll teach you how to have fun with it.

Then they announce they will want to port this codebase to use an excessive, completely rudimentary framework (in this project) and hog of resources - Spring. I was startled... They have a perfectly running lightweight pure-java solution, suitable for lambdas (starts up in 0.3sec), having complete control over all the parts of the machinery. And they want to turn it into a clunky, slow monster, riddled with Reflection, limited by the framework, allowing (and often encouraging) bad coding practices.

When I asked "what problem does this codebase have that Spring is going to solve" they replied me with "none, it's just that we're more used to maintaining Spring projects"

sure... why not... My baby is too pretty and too powerful for you - make it disgusting first thing in the morning! You own it anyway..

Then I am asked to consult them on how is it best to make the port. How to destroy my perfectly isolated handlers and merge them into monstrous @Controller classes with shared contexts and stuff. So you not only want to kill my baby - you want me to advise you on how to do it best.

sure... why not...

I did what I was asked until they ran into classloader conflicts (Spring context has its own classloaders). A few months later the port is not yet complete - the Spring version does not boot up. And they accidentally mention that a demo is coming. They'll be demoing that degenerate abomination to the VP.
The port was far from ready, so they were going to use my original version. And once again they asked me "what do you think we should show in the demo?"

You took my baby. You want to mutilate it. You want me to advise on how to do that best. And now you want me to advise on "which angle would it be best to look at it".

I wasn't invited to the demo, but my colleagues were. After the demo they told me mgmt asked those devs "why are you porting it to Spring?" and they answered with "because Spring will open us lots of possibilities for maintenance and extension of this project"

That hurts.
I can take a lot. But man, that hurts.

I wonder what else have they planned for me...

So as some of you know, I gave notice. my current company has me for 4 more days.

Why has my manager not given me someone to knowledge transfer to? Do they think I am bluffing? He even admits there is shit only I know!

Whenever I message him about it, he just ignores me. I guess if he wants me to do it later, I can in the weekends for $50 an hour? 🤔🤔

So here I am in class with just two weeks of knowledge in coding and this douchebag level 300 comes in like, 'Hey i'm a hacker and mid tier programmer and i can see you struggling with your basic code can i be of help?'... so I'm like, 'yh man. I'm a transfer biology student and i don't know a sh*t about coding but i have managed to buid a fine website of just two pages but i would also like to try hacking but first what programming languages do you know?' Guess what......the lil f*cker said HTML. I mean I may not know much but i know that can and will never be a programming language.

Knowledge Transfer

"No you can't ask a question"

"CTO" here.
Two week ago the CEO informs me that the "investor" want to put me in contact urgently with an external software house to help me with my "bottlenecks".
The investor goes immediately on holiday, so it's not available for explanations. The CEO doesn't know much.

Today I meet the software house CTO and CEO.
They tell me that I should do a transfer of knowledge with them. That they will respect my requirements, my schedule and that they want to help me.

During the meeting the business consultant explains "his" vision. Some new development nobody understand. Not even the CEO. The other cofounder is probably in disagreement but stay silent.

I agree to cooperate with them in due time and with due scope and planning.

It appears they already signed a contract with the investor. The investor is offering to us 40 days of a senior developer, for "free".
The CEO doesn't even know the economical details of the contract and he is surprised that has been signed.He also didn't know that a person will come over for 40 (?) days and that we will have to pay the transfer expenses.

I try to be friendly. I explain to them the issues I need to solve. I say specifically that I need help on certain tasks and that my wish is that nothing "new" will start until we fix some obvious problems.

After leaving, in the evening I receive an email from the software house guy, telling me that next week I MUST allocate a slot for technical transfer and the 2 weeks after for on site training. Like that. He also mention we "agreed" on that which is false. We agreed on me deciding the timing.

We are only 2 developers, at the moment and the other one will be on holiday next week, so I'm trying to get from him a lot of things I don't know because I don't know everything.

I'm not even sure I'll be able to explain how to prepare all the environment.
Worst thing is that I don't know what will be the scope of the project.

I really don't know how to behave.
I wrote back setting my conditions. I have holiday too. I have to prepare "documentation", explanation, etc.

I don't want the "senior dev" coming when I'm not present.
Maybe I was too weak answering and I should have started a fight immediately. Because he actually AGREED to let me decide and after that he set conditions on me immediately.

I don't know.
My stomach is burning, I had a very bad digestion with fever and headache, feel like puking, plus I spent several evening hours fixing the fucking Linux kernel bug.

I want to survive. I don't want to let them oust me in this stupid way. I want to fight.
I know that if I will explode, scream or whatever I will be at fault and I'll accelerate my demise.
When I try to be "diplomatic" actually I end up being weak.
When I try to be assertive I'm in fact rude and hysterical.
I can't think anything else.

This is what burnout looks like.

This was not exactly the worst work culture because the employees, it was because the upper level of the organization chart on the IT department.

I'm not quite sure how to translate the exact positions of that chart, but lets say that there is a General Manager, a couple of Area Managers (Infrastructure, Development), some Area Supervisors (2 or 3, by each area), and the grunts (that were us). Anyway, anything on the "Manager" was the source of all the toxicity on the department.

First and foremost, there was a lack of training for almost any employee. We were expected to know everything since day-1. Yes, the new employees had a (very) brief explanation about the technologies/languages were used, but they were expected to perform as a senior employee almost since the moment they cross the door. And forget about having some KT (Knowledge Transfer) sessions, they were none existent and if they existed, were only to solve a very immediate issue (now imagine what happened when someone quit*).

The general culture that they have to always say "yes" to the client/customer to almost anything without consulting to the development teams if that what was being asked to do was doable, or even feasible. And forget about doing a proper documentation about that change/development, as "that was needed yesterday and it needs to be done to be implemented tomorrow" (you know what I mean). This contributes to the previous point, as we didn't have enough time to train someone new because we had this absurd deadlines.

And because they cannot/wanted to say "NO", there were days when they came with an amount of new requirements that needed to be done and it didn't matter that we had other things to do. And the worst was that, until a couple of years (more or less), there was almost impossible to gather the correct requirements from the client/user, as they (managers) "had already" that requirement, and as they "know better" what the user wants, it was their vision what was being described on the requirements, not the users'...

And all that caused that, in a common basis, didn't have enough time to do all this stuff (mainly because the User Support) causing that we needed to do overtime, which almost always went unpaid (because a very ambiguous clause of the contract, and that we were "non-union workers"**). And this is my favorite point of this list, because, almost any overtime went unpaid, so basically we were expected to be working for free after the end of the work day (lets say, after the 17:00). Leaving "early" was almost a sin for the managers, as they always expected that we give more time to work that the indicated on the contract, and if not, they could raise a report to HR because the ambiguous clause allowed them to do it (among other childish things that they do).

Finally, the jewel of the crown, is that they never, but never acknowledge that they made a mistake. Never. That was impossible! If something failed on the things/systems/applications that they had assigned*** it was always our fault.

- "A report for the Finance Department is giving wrong information? It's the DBA's fault**** because although he manages that report, he couldn't imagine that I have an undocumented service (that runs before the creation the report) crashed because I modified a hidden and undocumented temporal table and forgot to update that service."

But, well, at least that's on the past. And although those aren't all the things that made that workplace so toxic, for me those were the most prominent ones.

-

* Well, here we I live it's very common to don't say anything about leaving the company until the very last day. Yes, I know that there are people that leave their "2-days notice", but it's not common (IMHO, of course). And yes, there are some of us that give a 1 or 2-weeks notice, but still it's not a common practice.

** I don't know how to translate this... We have a concept called "trusted employee", which is mainly used to describe any administrative employee, and that commonly is expected to give the 110% of what the contract says (unpaid overtimes, extra stuff to do, etc) and sadly it's an accepted condition (for whatever reasons). I chose "non-union workers" because in comparison with an union worker, we have less protections (besides the legal ways) regarding what I've described before. Curiously, there are also "operative workers", that doesn't belong to an union, but they have (sometimes) better protections that the administrative ones.

*** Yes, they were in charge of several systems, because they didn't trust us to handle/maintain them. And I'm sure that they still don't trust in their developers.

**** One of the managers, and the DBA are the only ones that handle some stuff (specially the one that involves "money"). The thing that allows to use the DBA as scapegoat is that such manager have more privileges and permissions than the DBA, as he was the previous DBA

So....
I was asked to transfer a spaghetti Android/iOS project to xamarin for a bank client yesterday because "that's what they use".

This is a crm/loyalty app that has been around for 2+ years now (you can imagine the mess). On top of that I have no knowledge of c#, .net or xamarin.

So I ask: "When is this supposed to be delivered?"

Boss: "It was scheduled for 2 weeks ago but let's say 2 weeks from now"

Me: "..... This is a huge remake it won't be even close to ready in 2 weeks"

Boss: "Let's check on the progress in 2 weeks and see how it goes"

Why is it hard for bosses to provide an actual timeframe???

He's been pulling the same crap with junior devs for years and of course they get nervous and create more spaghetti code...

Anyway long story short (not) I have an interview Monday!

Let's hope it's not more of the same!

P.S.: to junior devs: When you are given a deadline... IGNORE IT.

them: welcome new project members, this is our CI/CD pipeline which is completely different from the rest of the company, there won't be any great knowledge transfer, we just expect you to be able to know and use everything. but also, we expect you to work on your tasks and don't waste any time.
me: okay, so my tasks aren't going as fast as expected, because I need to invest some learning so i can set up my project correctly.
later: some help would be nice, i'm stuck right now
coworker: *helps me to fix my problems, which were partly due to misconfigured build servers* i know it's a lot, and unfortunately, for this topic sources on the web aren't so good. i can really recommend this book, this will give a deeper understanding of the topic.
me: okay, yeah i mean, tbh, i'll read the book if the project invests some time for me so i can learn everything that's required, but this won't happen. also, some initial workshop on the topic or anything would have been nice.
coworker: well, i mean, i am a software developer. for me, it is normal that i learn all that stuff in my free time. and i think that's what the PM expects from us.
me: okay, that's fine for you, i mean, if i'm interested in a topic, i will invest my private time. but in this case, PM would just expect me to do unpaid labor, to gain knowledge and skills that i can use in this specific project. i'm not willing to do that.
coworker: ...
me: ...

it's not that i don't want to learn. the thing is that there isn't any energy left by the end of the day. i'm actually trying to find some work life balance, because i don't feel balanced right now, haven't felt since i started this job.
also, this is only one of several projects i'm working on. it's like they expect me this project has top priority in my life. if it wasn't so annoying on different levels, maybe i'd have a more positive attitude towards it.

also, at the moment i find it fucking annoying that i have to invest so much time in this dev ops bullshit and this keeps me from doing my actual work.

if they are unhappy with my skills, either they can invest in my learning or kick me out. at this point, either is fine for me..

Never had full time mentors, just some great examples from great people:

Some years ago, I was new on the job. They sent me to see a colleague for the "transfer of knowledge" as he was leaving and I had to take over his projects.

He greeted me with a big smile and said:
"Oh, look, I just spilled very accidentally a cup of coffee on my pc so I've lost all information. Only thing I remember is that you have a call with this project today at 14 o'clock. I'll be gone by then but don't worry, just say we are late with delivery and it will be fine. I hope you all the best with your new job!"

I'll always remember him. I learned the value of improvisation, the utility of a cup of coffee and how to take things easy.

I always dream of doing what I learned from him sooner or later.

To quote Charles Bukowski:
"and when nobody wakes you up in the morning, and when nobody waits for you at night, and when you can do whatever you want. what do you call it, freedom or loneliness?"
I always have tendency to fall into feeling lonely and abandoned, but these days my life is tossing some of the wildest curve balls more than ever before.
The latest one yet just happened this Monday. My manager quit and there was no knowledge transfer, and it was not on the good terms with the company.
Now I'm the only member of my team, and I have to take care of some of the projects that I've never worked on.
Don't get me wrong, I'm not setup for failure, and there are no expectations for me to know how everything works, quiet the opposite. But working with our clients and debugging the projects that I literally setting up on the fly had been a rollercoaster.
Second time in this company I will be looking for a manager in my department, and teaching them how everything works. Fun times.. fun times never change..

Last week: Resigned from my current job as a front end dev, mostly due to incompetence in upper middle management.

Yesterday: knowledge transfer to backend dev who aspires to become full stack.
"
- So how does the designer deliver the CSS to the code ?
- He doesn't, he just sends the prototype, we make it work...
- The manager told me that the front end team did not touch CSS.
*fuzzy find ". styles"*
- So these are the 40 some files that appeared here magically.'
"

Today:
New git flow policy's in place. Pull requests are now outside the flow and are entirely optional.

This is gonna be the tits...

So I've been working on automating a project's regression tests for several months.

I'm not even experienced as a tester but as a developer it's more satisfying to script than to do everything manually.

Someone had been working on the project before but their test object repository was a mess. The senior that picked up the project while I was learning asked to be moved out two months later because it was too frustrating for him.

So there I am trying to fix the whole thing by myself. My boss notices a lot of the tests were failing and asked me to fix it before scripting new ones. I spend like a month doing that and then I hear rumours about cancelling the automation project.
Later I get told that I'm going to be rolled off the project due to low productivity. A few weeks later a new manager steps in and while I'm giving the knowledge transfer to my boss and manager they come to the realization that this clusterfuck isn't something a single person should be doing.

The manager talks with the client asking to keep me working on the project and asks for two more resources to speed things up.

Now I'm coaching three people.

i've got my first job after getting out of college. not a great package. I'm learning more, will get experience. i have plans for freelancing and seek a better job. I'm an Indian.

what really upsets me is that I just discovered that I've no knowledge in finance. I'm feeling insecure, afraid and depressed. I'm browsing for some youtube channels, books and podcasts to get some some knowledge about finance and real estate.

all I have is a saving account in SBI bank, I just know how to take money out of it with my debit card and transfer money with online banking

how do u guys do ur finance, where do u invest. do u invest in stock market. insurance?? help me out. i'm fucked.

never thought i can be so stupid, I hate myself, never even thought I'll need financial intelligence.

are there more people like me.

i'm just so down and feeling suicidal.

Few days before vacations ...

PM : "Project must absolutly be finished before your 3 weeks vacations."

ME : "We have to clarify the technical solution with the architect and the analyst before I can write the code."

PM : "No. Just do it and make sure you transfer the knowledge, it's urgent for the business."

... 3 weeks later, back from my vacations ...

Total of 0 commit(s) to repo...

Ok fellow dev's, the engineering head said that he had to let me go because apparently I'm a very talented engineer but I have a bad attitude. All of this because he claims I don't seem too interested in meetings and all that bs.
So from Monday on it's Knowledge transfer time since major parts of our product have been written by me.Wish the head had some balls, and told me he was firing me because I wont suck up to him and be a yes man, bastard thinks you can hire and fire good dev's just like that (he can) .Plus he has never appreciated folks for the effort and the work they do. :(

if someone dedicates sometime, even if it is fucking 30 seconds to share knowledge with you, appreciate it !! fuck! I hate presenting KTs !!

A client's representative (was an operations manager maybe; non technical guy) was explaining his legacy project (a knowledge transfer session), mentioned about using Azure for their new system.
One of the senior .net developer in the room interrupts this guy and asks "can you explain what do you mean by azure?"
I was like "what the fuck! did I hear it wrong"

Two (2) senior developers and one (1) senior tester left our team and I am left with two (2) Java legacy applications that are hard to maintain. Here is a list of things I hate about these old webapps (let's call them app A and B):

1. App A depends on 80% web services. If one web service for a product or warehouse goes down, work flow is impeded while prod support team checks with the core services team for repair

2. App B is a maven project with multiple modules dependent on libraries that are dependent on company's internal libraries. So if we want to upgrade to OpenJdk 9 and up, the project will definitely produce a lot of errors due to deprecated/unsupported codes

3. App A is dependent on Tibco and I have no experience on that

4. App B's continuous integration build tool is Jenkins and the jobs that build it has a shell script that wasn't updated during the tech upgrade enhancement. The previous developer who did the knowledge transfer to me didn't tell me about this (it should be considered a defect on her part but she already resigned)

5. App A when loaded in eclipse IDE is a pain to work with since it is only allowed to build a war file using ant. I have to lookup in quick search instead of calling shortcuts (call hierarchy) because the project wasn't compiled via eclipse.

6. It's impossible to debug app A because of #5

7. Both applications have high priority and complex enhancements and I have no other teammates to help me

8. You never know what else can go wrong anytime

The worst guy I worked with: Ex Military from USA, psychopath creating SaaS, B2B solution. The business idea was good and also got funding. He was so fucking racist.

When I joined his project there were 4 developers already working for him. One by one they all leave. I worked for the first 3 months taking over all the project.

Between the next 3-4 months I onboard 10-15 different developers and do knowledge transfer for all 10-15. Nobody works with him for more than 2 weeks.

He wants to developer do fucking 4 hours of meeting each day, repeating the same thing each time and expecting 8 hours of output. hire 3 project managers in 6-8 months. each one left.

I also told him i want to leave the project. By different ways he manages to keep me approx. 1 year. At end I told him this is my last month find another developer, So I can hand over the project. He was not able to find one. I leave the project he fucked up my profile.

Till date he has been looking for a developer, even trying to onboard developers in profit sharing.

what happened on TI today?
recently the company the I worked update me to a new cybersec analysis position. that's we'll but no money no nothing just more work and more responsabilities that fine to.
the really depressed thing is the training the transfer knowledge ropes and drills the manager was sleeping and singing Rhianna songs, was the most whit out a doubt "the most depressing training that I've ever had and ist a very well company that I work even he had the courage that told me that" this is the most depressing training ever gave, so by the way the training was about some reports some areas to work whit tickets links basic tools no even related whit cybersec so what it's that the new. way of training really I feel angry depressed and I thought was a lost of time.

Went into the office today to turn in my badge and gun (security badge/parking pass and yubikeys really) since I'm pretty much being given my last week before changing jobs to do brain dumps for knowledge transfer, and fuck all else.

Found a jar of moonshine in a closet when I went to take my things. IT said I could keep it. Not a bad parting gift.

So I joined this digital agency where they are working on this ad-tech product and right from day one, I was given a task to implement a new feature on the product. No knowledge transfer. No onboarding process. So, I had given estimation about the task and apparently it took longer than expected. But what were they expecting. Anyways, my manager asked me to have a KT with the only senior guy that has been working there for last couple of years. And man, since the KT started, it's been hell for me. The guy is such an asshole and won't even give me a basic walkthrough of the system. He only took one call and that ended within 30 minutes. On top of that he went ahead and told the product manager that I am not keeping up and am not ready. And my product manager apparently wants me to take his place within a month. It's been only two months since I joined. I have already pushed two major features, tried to understand the system architecture, codebase and everything on my own. On top of that, I got yelled at by that senior dev in a meeting about a PR. I was quite confident guy when I joined and now I am anxious everyday at work and i am scared that they'll let me go because I won't be able to meet their unrealistic expectations. I also can't stand this senior dev and he can't stand me which makes me really demotivated to work. I have anxiety issues and now I am thinking if I stay, I am gonna mess up big time and they'll fire me or worse. I might break something in production because I didn't have proper onboarding.

Completely forgot to update what was going on with my potential role shift. Long story short, it was approved by the damagement. That’s nice.

I only have to get to a major milestone in my current giant of an IaC project and transfer enough knowledge to leave it in my current team mates’ hands. Looks like we’ll be there pretty much next week and I can switch at the start of 2023. Life’s good.

... worst drunk coding experience?
none. or to be more precise, all of the three of them I had. I can't code drunk, i hate doing it, i hatw even thinking about doing it when drunk.

so after those initial three attempts i don't try to do it again, ever.

BUT, best coding experience while high?
ALL OF THEM.
some of the best pieces of code I wrote i did when I was high. my mind goes into overdrive at those times, and my thinking is not lines/threads of thought, but TREES of thought, branching and branching, all nodes of each layer of the tree coming to me AT ONCE, one packet == whole layer across all of the branches.

and the best was when one day, in about 14 hour marathon of coding while high, i wrote from scratch a whole vertical slice of my AI system that i've been toying around in my head for several years prior, and I had all of the high-level concepts ALMOST down, but could never specify them into concrete implementations.

and I do mean MY ai system, my own design, from the ground up, mixing principles of neural networks and neuropsychology/human brain that I still haven't seen even mentioned anywhere.

autonomous game ai which percieves and explores its environment and tools within it via code reflection, remembers and learns, uses tools, makes decisions for itself for its own well-being.

in the end, i had a testbed with person, zombie and shotgun.
all they had pre-defined in their brains were concepts of hunger and health. nothing more.

upon launching it, zombie realized it wants to feed, approached oblivious person, and started eating it.

at which point, purely out of how the system worked, person realized: "this hurts, the hurt is caused by zombie, therefore i hate zombie, therefore i want to hurt it", then looked around, saw the shotgun, inspected its class by reflection, realized "this can hurt stuff", picked the shotgun up, and shot the zombie.

remembered all of that, and upon seeing another zombie, shot it immediately.

it was a complete system, all it needed to become full-fledged thing was adding more concepts and usable objects, and it would automatically be able to create complex multi-stage, multi-element plans to achieve its goals/needs/wants and execute them. and the system was designed in such a way that by just adding a dictionary of natural language words for the concept objects on top of it, it should have been able to generate (crude but functional) english sentences to "talk" about its memories, explain what happened when, how it reacted, what it did and why, just by exploring the memory graph the same way as when it was doing its decision process... and by reversing the function, it should have been able to recieve (crude) english sentences that would make it learn what happened somewhere else in the gameworld to someone else, how to use stuff and tell it what to do, as in, actually transfer actual actionable usable knowledge to it...

it felt amazing to code for 14 hours straight, with no testruns during that, run it for the first time after those 14 hours, and see that happen.

and it did, i swear! while i was coding, i was routinely just realizing typos and mistakes i did 5-20 minutes ago, 4 files/classes ago! the kind you (and i) usually notice only when you try to run the thing and it bugs out.

it was a transcendental experience.

and then, two days later, i don't remember anymore what happened, but i lost all of that code.

and since then, i never mustered enough strength and resolve to try and write the whole thing again.

... that was like 4 years ago.
i hope that miracle will happen again one day...

Long post, TLDR: Given a large team building large enterprise apps with many parts (mini-projects/processes), how do you reduce the bus-factor and the # of Brent's (Phoenix Project)?

# The detailed version #

We have a lot of people making changes, building in new processes to support new flows or changes in the requirements and data.

But we also have to support these except when it gets into Production there is little information to quickly understand:
- how it works
- what it does/supposed to do
- what the inputs and dependencies are

So often times, if there's an issue, I have to reverse engineer whatever logic I can find out of a huge mess.

I guess the saying goes: the only people that know how it works is whoever wrote it and God.

I'm a senior dev but i spend a lot of time digging thru source code and PROD issues to figure out why ... is broken and how to maybe fix it.

I think in Agile there's supposed to be artifacts during development but never seen em.

Personally whenever i work on a new project, I write down notes and create design diagrams so i can confirm things and have easy to use references while working.

I don't think anyone else does that. And afterwards, I don't have anywhere to put it/share it. There is no central repo for this stuff other than our Wiki but for the most part, is like a dumping ground. You have to dig for information and hoping there's something useful.

And when people leave, information is lost forever and well... we hire a lot of monkeys... so again I feel a lot of times i m trying to recover information from a corrupted hard drive...

The only way real information is transferred is thru word of mouth, special knowledge transfer sessions.

Ideally I would like anything that goes into PROD to have design docs as well as usage instructions in order for anyone to be able to quickly pick it up as needed but I'm not sure if that's realistic.

Even unit tests don't seem to help much as they just test specific functions but don't give much detail about how a whole process is supposed to work.

Fuck companies that want you to build new systems that are a superset of what they already have when they can't even tell you what they have now. Fuck you with your bullshit, nonsensical, self-contradicting, third-assed diagrams--some half-UML, half-clip-art, half-pie-chart drivel. If you're the CTO of a company and you want me to think long and hard about rebuilding your distributed systems, you can think long and hard about expressing what you already have. And NO: a verbal explanation pow-pow WebEx over your DSL connection with your protege that mumbles worse than an Atlantan rapper doesn't count as fucking "knowledge transfer" of your fucking architecture, FOR FUCKS SAKE.

Today is the last day of my placement.

Over the past year, I began working on small front end bugs, to becoming the sole front end developer on the project, to being full stack.

Back in July, I and the other dev on the project released the app into the wild. It now is reaching 100 users.

The app has a lot of external dependencies (10+), one of which could cripple it entirely should it cut us off (which they can do at any time, it's a free API).

I was given, effectively a week and a two days to do a complete handover/transfer of knowledge to the placement student that will be taking my place. They hadn't touched front end (like me) when starting, but also had no experience in node/js.

As of this, I can't leave feeling like I've fully completed my work, and I feel bad leaving the new guy with these clients. Undoubtedly I'll be doing some off-the-record help.

That feeling when the feature your team developed needs to be transferred to the other site team. Someone's taking our baby 😭.

I am supposed to join a new team next week. And I'm an intern for clarification. The boss is overloading me with work, while I have to juggle with an ongoing knowledge transfer in current team. I've brought home work laptop for the 3rd time this week, and I'm literally working most of the time. What makes this worse, is I feel guilty because boss is in another country and needs me there.

While, I would've been happy to go there, but I feel burdened that I'm being sent to a different place for my skills; and still, I'm not doing my tasks properly.

I'm anxious and haven't had a proper sleep in 3 days.

Is short, quality rant for y'all.

So happy, a former colleague, now friend, of mine decided to join my project, he has a lot of experience and helped me out a ton in my first professional years to gain knowledge about optimization, performance, architecture and countless more stuff.(--> wk73 best dev teacher I had)
The only downside, in this case very minor downside, is that I now have to go back to something I despise: project management... I need to properly format and transfer all my scribblings and thoughts into a roadmap and a rough specification, so he has a good start into the project.
Overall though I am really looking forward to this collab, since I love to work in a team, especially with such great support.

Co own a service with another team.

Service is something me or my team have hardly worked on. Other team have far more knowledge on it. There is no active development that we do on it so no opportunity to really learn on it.

Some months back was involved in migrating the tests of this service to run on another system. I was unsuccessful and asked this other team a lot for help. This was just migrating, nothing to make you more familiar with code etc but just seeing the config and wondering what to change. The CID team then said we could temporarily add this service to use old system for builds.

Now get request from CID team they're diagnosing the issue for the service and that if they need help if we'd be able to help. I said other team better as they understand better. Manager of other team then replies with big message tagging my manager and PO and frankly says why the fuck am I forwarding this to other team, we should learn the service too as co owned. While I get their point, shouldn't stop assisting another team for the sake of knowledge transfer, should have other dedicated sessions for that.

Would be open to hear thoughts, is she in the right here? Frankly we already own loads of other stuff and never have time to look at this service that somehow the team owns

So I'm being asked to move to a different country for a couple of months. While, this would have generally been a fun thing, the deadline's pretty tight. Add to it the fact that the knowledge transfer is going painfully slow and I'm already being asked to finish tasks on tech/stack I've never ever seen before. It's a mess!

For me it's definitely teaching. Whether I teach coding or any mathematical or even theoretical subjects. I find that when you teach someone you learn how to communicate better and transfer knowledge effectively. Communication is key in client relationships.

Secondly when you teach someone a concept you think you understand you tend to find flaws in the way you understand that subject matter by forcing you to hear your explanation out loud. This in turn will make you delve deeper into that subject matter and make you understand it better, rearranging your own perceptions and correcting those flaws.

Switching jobs is part of our career growth and as a developer, we do this every two years on average.
I know that after announcing my resignation my colleagues won't treat me the same.

It's like I'm an entity in the system that you don't have to query it anymore but you have to exhaust its knowledge transfer limit within the notice period.

All the facades and presenter layers will fade out and you will know which models care about you and want to keep the existent associations. Those models only deserve to publish your contact payload with them.

My requests will be faced by slow response HR endpoints and I'll have to rely on a retriable solution to access the required document data.

I was mentally ready for it but it's still painful as I have to endure this for 2 months, yes, the EU has longer notice periods.

Do you guys have tips to share from your experience?

Does a role reassignment necessarily mean I am on the chopping block/going to be laid off? I was hired as a Junior Software Architect and I ended up doing more infrastructure work (think DevOps) but I wanted to do more actual C++ coding. An email was sent out to the manager/HR by my supervisor and I think for the most part I will still retain the same title - the email just states what my next tasks are (knowledge transfer to other employees) and what my new role will be.