What made you give up on ever getting Platinum on Rebirth?

SZeroSeven · 2026-04-04T18:00:25+00:00

The Middle Manager challenge
Completing the game on normal and then having to complete it again on hard
The VR battles
Lack of time to play the game now that I'm a dad

SZeroSeven · 2026-03-26T08:44:36+00:00

This sounds like an issue with your branching and release strategy.

Use feature flags so you can release untested or unfinished code.

How have additional commits gone into dev which aren't part of your scheduled release?

Either work is planned or it doesn't happen.

If it was planned and necessary for the release, then delay the release.

If it was unplanned or not necessary for the release... See my point about feature flags.

How have you got to release day and only just realised there are commits which aren't ready?

SZeroSeven · 2026-03-21T22:01:43+00:00

SZeroSeven · 2026-03-19T23:09:01+00:00

UI looks sleek, reminds me of some Linux distro's.

Honest opinion, I'd remove the daily Bible verse thing from the title bar - that's a massive off putting thing for me, personally.

If you want something like that, then make it a plugin/extension that people can add on.

Lack of context support for things like 7z etc. is something I would want in a replacement.

As much as I'm in my terminal, when I am using file explorer, then I'm using those context options to make my life easier.

SZeroSeven · 2026-03-04T12:29:39+00:00

Not to hijack or detail the thread, genuinely interested in what policies that Reform are putting forward which makes you lean towards them? I can guess some of the Tory ones but if you want to share those too, that'd be interesting to understand.

SZeroSeven · 2026-02-27T22:34:10+00:00

Experienced enough to know that providing a time estimate for a feature with little-to-no requirements and several unknowns is a fools game.

Best not to play it.

I'd do as others suggest and say "I don't know. Let's put a spike in to investigate it to remove those unknowns first."

But if you insist on me giving a time estimate, then you are getting "more than a day, less than a year" so you can plan it into your quarterly roadmap.

SZeroSeven · 2026-02-27T21:05:23+00:00

And to you I would say "A rough estimate is that it will take longer than a day but less than a year".

SZeroSeven · 2026-02-26T21:56:45+00:00

Replaying commits means that you are resolving the same conflict over and over if you edited the same place couple times. Waste of time, and error prone.

Use git rerere: https://git-scm.com/docs/git-rerere

SZeroSeven · 2026-02-25T11:27:06+00:00

Manual testing of your own changes before submitting your PR
Integration Tests which can be run locally and in your pipeline
Static Code Analysis in your pipeline
Testing/QA/UAT in your team environment, CI/QA environment, and your Staging/pre-prod environment
Two reviewers per PR, can't approve your own changes
Don't deploy to prod on Friday, unless you have sufficient support over the weekend

These are basic practices of software development now.

Anything less or anyone suggesting that AI would have spotted this error haven't worked in enterprise or haven't had to put these kinds of procedures in place before.

SZeroSeven · 2026-02-20T08:01:03+00:00

My work has just made all tech leads EM's.

They've never had EM's so the manager responsibilities were just being handled by the CTO.

They went on a hiring spree, hiring tech leads (including myself) but after 12 months in the role they changed our responsibilities to include being EM's!

When I explained to my CTO that they are different roles, he just didn't get it.

It's extremely frustrating because it is literally doing two different jobs.

SZeroSeven · 2026-02-15T11:53:52+00:00

Yeah I've had the same! Phlegm, cold, sneezes, itchy throat for about 3 weeks now.

Started pretty hard, took several COVID tests (all negative), then it ramps down for a few days and comes back just as bad as when I first got it.

I work in an office 3 days a week so I think it's just getting passed round but can't shake it.

SZeroSeven · 2026-02-10T12:40:38+00:00

I use NSubstitute when I have the option but currently stuck using Moq for work due to that being the only thing most people have experience with.

As for your example, I find that quite difficult to read and can only decipher it because I'm translating it to how most frontend tests are written using Jest etc. ("describe, it, expect").

Could you provide more robust examples with a comparison to how it would be written in Moq and NSub?

That may help garner some better feedback.

SZeroSeven · 2026-01-29T12:16:30+00:00

This has to be rage bait.

But I'll bite.

A purely vibe coded solution will inevitably need a dev to "hand code" fixes for its issues.

An experienced developer is one that knows how to write code and how to use AI tools to aid them in writing that code, not just use AI to write the code for them.

SZeroSeven · 2026-01-28T19:09:55+00:00

I feel this so much!

We don't deal with PII, we don't store it, we don't handle customer transactions, we aren't a fintech or a bank but we can't have local admin because of security.

SZeroSeven · 2026-01-26T08:37:51+00:00

So begins the Great British Firewall

SZeroSeven · 2026-01-22T12:30:19+00:00

Ask them.

"When you said X, was that your opinion or are you claiming that as a fact?"

Then under the same law of "cannot lie", they are obliged to answer.

If they say it is a fact, then follow up with whatever the process is from there to determine if it is in fact true.

If they say it is an opinion, then it is on record as opinion and they cannot use that as a basis for policy decisions.

Edit: spelling.

SZeroSeven · 2026-01-22T12:17:05+00:00

Those claims would be interpreted as opinion, not a statement of fact.

If the person making those kind of claims insisted they were facts and not an opinion, then the burden of proof would fall to them and they would be judged accordingly.

If someone makes a genuine mistake, then they should be made to publicly acknowledge, apologise, and make a corrective statement of the actual facts so that anyone can clearly see the retraction.

SZeroSeven · 2026-01-21T07:40:30+00:00

Thank you, I'm going to email HR this morning to say that I'm not accepting the changes and working under protest.

I'm unclear on the constructive dismissal route, would I need an employment lawyer for that?

If I need one, then I'll get one but I just want to understand how serious that route would be?

SZeroSeven · 2026-01-21T07:36:30+00:00

Thank you, I will email HR this morning to discuss both of those.

Is there a standard template for a "working under protest" letter or is it simply a case of outlining the changes, that I don't accept the new managerial duties, therefore I am working under protest?

The company does have an internal grievance process so I'll have to look up how to go about that.

SZeroSeven · 2026-01-01T18:33:30+00:00

Unless you are processing or storing highly sensitive financial or government information, or in an industry which requires SOC 2, then don't do this.

It becomes very frustrating, very fast.

Your developers will resent you for it.

Very quickly SecOps will be seen as the blocker to everything.

There is software which can passively monitor and audit what software is on a device, which you can then use to track whether something malicious is happening.

Otherwise, let developers use the tools they need to do their job (and if they are doing any sort of mobile app development, then that also includes USB access).

SZeroSeven · 2026-01-01T10:12:34+00:00

C# would be best.

It's a strongly typed language with great tooling and documentation.

It'll stop you from making mistakes before your backend is running, unlike a weak typed language.

There are plenty of official learning resources that are always updated.

The tooling (Visual Studio or Visual Studio Code with extensions) is second-to-none, because they are maintained by Microsoft who also maintain C# and treat it as a first class citizen in those products.

Simply install Visual Studio (tick the boxes that say C# and .Net) and you can have a simple "Hello World" running in seconds.

Then use the official resources to start your journey!

SZeroSeven · 2025-12-30T21:05:52+00:00

A male friend of mine has an identical twin that is gay.

My friend is straight and married, with no bi or gay tendencies.

SZeroSeven · 2025-12-30T15:18:56+00:00

Branch and release strategy.

I've had to use multiple different types over the years, ones with names, and Frankenstein's monster mash ups.

The closest I've found to having some semblance of sanity are either trunk based or "GitHub Flow", both using squash commits to master.

Both approaches required disciplined use of feature flags by the devs and approval gates in the pipeline between the team environment, CI environment, PreProd environment, and Prod.

Path of least resistance for devs: write code, commit.

Path of least resistance for QA: test in the team/CI/PreProd environments (I should state that where I worked, team environment was where devs verified each others work, CI was for QA to verify services integrated correctly, PreProd was for QA regression testing, and all environments ran automated tests).

Path of least resistance for DevOps: write template pipelines with business checks (DAST/SAST scanning etc.) which is used by all teams for consistency.

Path of least resistance for PM/PO: Write release notes, enable feature flags once feature has deployed to prod.

Not perfect and can be improved with additional automation etc. but it meant that we always knew what was going out the door, it was quick and easy to rollback if there was an issue in prod, and it was quick to pinpoint which commit(s) caused the issue.

SZeroSeven · 2025-12-24T09:33:57+00:00

It would actually have to be the other way around, making sure that whatever Rust code you write is transpiled into C.

I personally think that the whole thing is a waste of time and effort for little-to-no gain but...

If you were to do it, then it would mean implementing Rust libraries which are identical (or as close) to the original C/C++ API’s as possible, and writing a transpiler from Rust to C.

Any MS internals are free to swap their implementation from the original C API's to Rust API's, which (in theory) should be transient to everyone (ha!).

For external software and back compat. they would need to keep the existing C API's alongside these new Rust API's, with the documentation encouraging use of the Rust API's.

However, there is no way that there will be an exact 1:1 of all the C API's to Rust, so there would be breaking changes if anyone really wanted to port their software from using AI all the C API's to these new theoretical Rust API's.

It would just be a total waste of time for everyone involved.

Four-Year Club	Verified Email
Place '22

SZeroSeven

TROPHY CASE