Works for the devil and then complains it’s evil.

Kind of on you, buddy. If you can get a job there, you can get a job many places and not be complicit in this.

I don’t mind asset restriction and branding but with that, they should allow you to swap out assets and brand names. No freedom to distribute.

TIL. Thanks for the explanation.

“Source available” is the accepted term. Without a legitimate well tested open source license, it isn’t free to distribute and therefore doesn’t meet the one of the 4 principles of open source.".

Is this tech news or public relations? We already know they gone all in on AI bullshit.

OpenSuse Tumbleweed is a great balance between stable and updates (rolling updates). Worth considering if Debian doesn’t work out.

Delayed response, but raise a ticket in retros saying retros should be cancelled. Andvwhrn asked why, say nothing is followed upon or learn so there is no point doing them.

Then you can talk shit about them and make clear without change, you won’t commit time to next one as there is no point.

Could be fun to see what the response is.

Lol, who outsources 1 piece of work like that. Never seen it done. Onboarding and exposure of code to outside world are big risks.

I don’t know those guys so they can say what they want. We don’t just ship. We code, review, test and only then deploy. I will build this the only way I can see and it’ll take 3 days. Want me to start this?

You’re trusting a PO to decide on how you build? They ain’t coders. They decide on value, you estimate and build and they prioritise based on the information you provide. POs aren’t the boss of devs. That’s usually engineering managers. You are both specialists in your field. You don’t lecture them on value and how pointless a feature is, you size it, and using velocity they can anticipate how much will likely be delivered in next sprint. If they really object, “if you feel you can build it in 1 day, go ahead, ill give you access. I have no idea how that could be done”

PO wouldn’t like it during live incident when shit goes wrong that you suggest “I did highlight the risk of this occurring and proposed mitigation steps but was overruled”.

“True. It’ll be perfectly fine, and because of that, you won’t need me on call when it all goes dramatically wrong. If you need access to the repo, I’ll add you in though. Good luck.”

Or, if you’ve worked together a while “like I overthought it when we worked on x, and y went wrong, and I called it before it happened. Turns out I’m quite good at seeing car crashes in advance.”

Mad? In a professional workplace?

“If you can give me that issue free codebase, I’m happy to do that, but failing that, it takes 3 days to add that feature that is akin to the leaning tower of Piza taped together with duct tape. There is only so much tech debt you can pile on until you are in code hell, and unfortunately, we are.”

If they do some weird ass schedule “well, you can write down that if you wish, feel free to write down that my other car is a Bugatti, if we are just theorising on a perfect unicorn world”.

No. Nothing does. There are about 1.4bn children over 5. Over 200m play per month. If you factor in economic information like those without devices, that’s huge. One in 7 kids. In a class of 30, that’s 4 players. Considering some countries will have low saturation, developed countries will have significant player population. It’s huge. Unrivaled in gaming.

“Why are we only learning about this now? I think we need to look into the process that work comes into the team otherwise, if we don’t learn, we are going to take the website down and cost the company thousands/millions”. There is a reason retros exist.

“You ask me how long it’ll take, and it’s 3 days. You probably need to manage expectations on this. Maybe let them know the risks of x, y and z and why it will take this long”.

“I only know 1 (credible) way to build it. I’ll take x days. I’ll go right ahead with that.”

How can they block? Usually they cannot code so cannot do it themselves. Working in a place that micromanages you this badly must by soul destroying and degrading. Job sites are a good option.

I find project managers don’t want to be responsible for building shit that is flaky on prod. Either the consultancy reputation or team reputation becomes mud and their promotion opportunities vanish.

Then you don’t give another option and only give estimates for doing it correctly.

If you’re saying “I could hack it in for you this way”, you’re a cowboy dev.

Depends where you work.

If you’re good and they respect you , you’ll get away with “no” or, “I’ll build it, but if it goes wrong, I’m not fixing this evening and weekends”. Safest option is “in all honesty, I cannot see another credible option, no” and if you’re fed up of the follow up, drop the word credible.

Then if you trust your team, have dev meetings and don’t give alternatives. Make it clear there is one way to do it and it’ll take x days long.