Lovely, I got a deadline for some front-end work but the back-end is in shambles right now :D

In the beginning of October, I was around 9% of the dev team. Now with some firing & people leaving, I'm 50% of the dev team.

It might be time to jump ship

A few months ago, we asked an external company to create a simple project since we lack the developers now...

I've just looked into it and the first thing we found was Evil Rick (from Rick & Morty)

I've just received a merge request for a feature that we outsourced. How do you best deal with substandard quality?

It's a merge request for roughly 2k lines of code and I've already noted down 25 comments and I'm only at my first file :(

Yay, merged 30 pull requests on a Friday.

What could go wrong :D

We use a open-source business management software (incl. crm, e-commerce, billing, accounting, warehouse, ...) that is highly customizable.

Previously we had "Company A" that customized it for my company. It was very expensive so they hired something to do the same but cheaper & inhouse. The codebase that "Company A" has written was terrible (confirmed by CTO & the new colleague").

Then the CFO wanted functionality A. Colleague said that this will take 2 weeks to implement. One week later, it was no longer needed & functionality B was now mandatory. Rinse & Repeat.

The CFO: "Why is nothing ever gonna get finished" or "why is the quality so bad?"

So they hired another person for the same position. This person has more experience so it costs them a lot more... And suddenly, everything works well

They contacted a few months later a consultant that analyzed the company. The consultant asked (for good reason) why such a small company has 2 people maintaining the in-house BM software. And suddenly, they wanted to get rid of the worst person. <enter my previous rant>

He is thrown out. Now the head of Operations wants to remove that software because it was not "sexy" enough (her words). So they introduced a glorified spreadsheet with less functionality. That new colleague was offered to take the lead on that project... And thus he fled to another company.

That project failed and now everyone is fired... And they hired back "Company A" to maintain that BM project.

An ex-colleague got accused stealing company property (soda) that he bought with his own money.

He had put his own soda near the other soda of the company (a different brand they never bought). He went home one day and took 1 bottle with him. During that time period, the company offered free drinks (non-alcoholic of course).

WHY WERE THEY EVEN WATCHING THE CAMERAS

I made 3 designs (more like proof of concepts) 2 months ago for a certain feature request.

2 months ago:
I presented to the CTO & CEO and the senior developer.
Senior developer prefers design A
CTO prefers design A with some very minor changes
CEO prefers design C with some major changes (ok, at this point is it more design D)
CTO & senior dev tried to argue for his idea but gave up.
So we decide to implement Design D

Now:
Customers complained that the designs is not clear (UX-wise)
CEO: "I have the idea to make some adjustments" and explained design A.

This happens pretty much for every other feature request since I started doing designs for new features. Previously they implemented it without designs.

I found this on stackoverflow

The management wants to add gamification to our b2b app and our app is not yet officially out... Yay priorities

I'm a junior dev and my senior is not getting around to reviewing my tickets. Now there are multiple months-old tickets that still have to be reviewed. That feature should have been released months ago and it has not yet been reviewed.

Soon the (only) senior dev will go on a holiday and it feels kinda useless to continue to develop stuff that takes forever to be reviewed.

In the past 1 week, there is one ticket reviewed and there are 10 more in review. :')

It's not like it's a big team... 3 devs (The senior, me and another junior (who is on leave for the past 2 weeks for personal reasons).

Yay, I inherited a project with no documentation that is soon to be out of the prototype phase in a tech stack where I have no experience. It is already sold to customers and they expect it soon.

There are so many bugs, never been code reviewed but the main functionality semi-works :(

Recently, our COO left the company and we got a new one. He is, for some reason, a freelancer which I find very odd as a C-level employee.

Anyway, fast forward 3 months and we the scrum master (or project manager), 60% of our dev team, one tech guy responsible for installations and our intern IT support department all got fired.

Now they gave me the decision for a raise, extra training (that they pay) but I have to find/figure out or an e-bike. Does anyone have some advice?

Recently, our backend team has gotten smaller. The company has stopped the collaboration with the company of the backend lead developer.

We are currently lacking backend developers while we have way too many frontend developers right now (compared to backend).

How can I, as a front-end developer, switch to back-end?

Last year, my company has added the functionality for users to reset their passwords.

The company was then 5y old and already had to reset thousands of passwords. Oh well...

I started my first IT job nearly 2 years ago, and since then I have already had 4 different "project/scrum" managers for my team.

I don't know how I should feel about it

My team lead wants all tickets reviewed but it takes them forever to review them. The 2 juniors (incl. me) have now 6 tickets in review each.

"Scrum master" (if we can call it that) assigns all tickets upon creation. There are currently no unassigned tickets left in the backlog that I can start with.

Half of my dev team has decided to leave. Back-end decreases with 75% and front-end team decreases with 20%.

This is the fourth time that half or more of the dev team has to be replaced in my companies existing (which is less than 10y).

Small start-up story:

The company hired independent foreign devs. The tech lead developer has decided to leave (due to some disputes with the boss(es)). The rest of his team are subcontractors/other independent devs that are good friends with the lead dev. We also recently adopted a 'scrum' which they really dislike.

So I guess there is a small change we will have a back-end team in the near future.

What should you do if the project manager is not assigning you any new work after the backlog already has been cleaned up?

I currently work as a junior front-end dev. For the past few weeks, the 2 juniors (incl. me) are lacking tickets. For example, I got 2.5 days of work assigned during our 3-week sprint. We already followed some courses, read some books & created some designs for upcoming features (that have no "functional specifications" written down).