Reputation
944
Top tag
Next privilege 1,000 Rep.
See votes, expandable usercard
Badges
4 12
Newest
 Yearling
Impact
~45k people reached

Feb
25
awarded  Yearling
Feb
22
awarded  Nice Answer
Jan
26
awarded  Notable Question
Dec
8
comment Keeping git repositories on different hosts in sync
You might want to mention in your answer that the first thing you do is delete an existing local directory with $REPO_NAME. This seems important and might prevent data loss for people who simply copy your solution.
Nov
25
comment Workflow for chains of dependent pull requests to projects that depend on other projects
well in .Net world you use NuGet, where every dependency package has a version that uses SemVer. So you only need to version your dependencies and everything 'just works'.
Nov
25
comment Workflow for chains of dependent pull requests to projects that depend on other projects
Some words on importance of versioning dependencies might help... B 2.1 needs A 3.11 and adding A 4.0 doesn't break B since B 2.1 still uses A 3.11 until it's updated.
Nov
25
comment Workflow for chains of dependent pull requests to projects that depend on other projects
You did not add a java tag, so .. in C# world, you would just create a NuGet package from A that is consumed by B. B would use the original (or latest compatible) NuGet until you updated B to use the new one. So B never breaks because it will still use the previous dependency until you actually update B.
Nov
5
comment Is this avoiding inheritance correctly?
As @shudder pointed out, it's much better to only inject what you directly need. If you inject EventManager, your object only has a dependency on that. If you inject ServiceManager but only need it to get EventManager, you still add the dependency to both service and eventmanager and make your code uglier (the additional getter).
Nov
2
comment How is this pattern called?
It seems to me the question is about the forward to the next-higher version, not the overloading itself (1 param => 2 param => 3 param).
Nov
2
comment How to do peer reviews on GitHub pull requests?
Write a comment to your prq, and highlight @whoever you want to get a notification. Reviewer can add tags to show their review opinion.
Oct
26
comment Justification for different code bases on different branches in the same repo?
It's one of the few things where I think GitHub chose a bad solution. A separate pages repo would be so much cleaner. Why should I bloat a nice small code repo with images and html? It makes no sense.
Sep
29
comment Does implicit and explicit cast operator overloading violate the D in SOLID principles of OO?
Interfaces make operators second class citizens.
Sep
11
answered How to consume standard routed API in a clean way?
Aug
27
comment When to use interfaces (unit testing, IoC?)
I disagree. Not writing an interface for any object that is passed around (even if there's only one implementation) feels sloppy to me. The interface is not overhead, it improves code readability (clear small interface > class with implementation details), helps testing and counting it as code duplication requires some ...shaky... assumptions.
Aug
27
comment When to use interfaces (unit testing, IoC?)
-1, since often you don't know how many implementors you need when you first write the code. If you use an interface from the start, you don't have to change clients when writing additional implementors.
Aug
21
comment Automatically reverting commits that fail the build
It seems you are using git in a strange way. Generally, people should be working on their own repos in their own branches, and only push to main once CI for their personal build verified that the changes are OK.
Jul
30
comment What exactly is copyrighted, the text of the code itself, or the design?
A nice solution might be to release your personal project as bsd-style open source, and then ask your employer if you could use it as backend (since it already contains part of the functionality you would have to reimplement in work-time).
Jul
21
comment My algorithm that extracts the largest box that can be made from smaller boxes, is too slow
Full nodes can be merged in the sense that all 8 children can become part of a single larger box. This larger box will not have to be split later on, but it might be merged. The hierarchy allows you to quickly merge lots of boxes, completely filled nodes allow you to jump up a level without further testing.
Jul
21
answered My algorithm that extracts the largest box that can be made from smaller boxes, is too slow
Jun
17
comment Appropriate developer permissions on a dev server?
These days it's probably easiest to set up a VM with exactly what you need and hand the VM to your IT.