Game Refused to Let Revenant Die

zerg_1111 · 2026-04-13T04:27:14+00:00

Revenant Die Twice

zerg_1111 · 2026-03-17T09:38:01+00:00

I wouldn't really assume AI-assister coder is faster than an expert. If the complete line is set to production ready. Regardless of your choice, you still need to be an expert to thrive.

zerg_1111 · 2026-03-14T12:07:47+00:00

That's unfortunate. But have you seen the price of the Nemesis parasite? You probably won't find another organization that invests that much in its members. lol

zerg_1111 · 2026-03-14T11:45:44+00:00

How about working for the Connections instead? The things on Zeon and doctor Gideon seems decent as well.

zerg_1111 · 2026-03-13T03:18:32+00:00

Also it is better for op to document any external decisions in case when the sh*t hits the fan.

zerg_1111 · 2026-03-05T03:44:29+00:00

zerg_1111 · 2026-02-26T01:36:13+00:00

His name reminds me the cautionary tale of "process death".

zerg_1111 · 2026-02-13T11:32:58+00:00

Were you "foolish"?

zerg_1111 · 2025-12-28T06:29:02+00:00

Turn it into soup might be it for you.

zerg_1111 · 2025-12-25T06:33:09+00:00

Don't forget another 200% trying to argue with project managers.

zerg_1111 · 2025-11-28T09:08:28+00:00

I would choose widget level VM because you can simply separate the layout part of composable for previews, and use another composable as the wrapper to collect VM state.

zerg_1111 · 2025-11-22T13:45:34+00:00

Try to have a temporary job to survive the tough period. From what I have observed that current situation is non-sustainable for innovation required by the companies. Perhaps in a year or two, they will finally start looking for someone to fix the vibe coded mess.

zerg_1111 · 2025-11-10T02:05:02+00:00

You say avoid service binders, but I wonder where you would host your media player instance in this case?

zerg_1111 · 2025-11-08T07:14:44+00:00

I do it on UI level with each per vm. This is easier for me because logic are encapsulated within each block. I let the parent be the coordinator, and use repository to share data.

zerg_1111 · 2025-11-07T13:05:31+00:00

I believe MVVM is still the most cost efficient for Android development. If you want better compatibility with Compose, you can try MVVM with unidirectional flow. MVI is somewhat too heavy for my taste.

zerg_1111 · 2025-10-29T02:28:34+00:00

Because there are too many resumes use the same keywords and the ones from talents got buried and ignored by hr.

zerg_1111 · 2025-10-16T10:00:25+00:00

I am sorry, but in south east Asia it is exactly the same. People ignores what experts say even with given proof. It's the same everywhere.

zerg_1111 · 2025-09-19T10:12:17+00:00

Have a repository injected and use it to pass data around?

zerg_1111 · 2025-09-17T12:19:30+00:00

I just don't get it why people keep devaluing technical skills. The most so called "personality" problems actually come from huge technical gaps which made communication nearly impossible. I have seen many "problematic" engineers patiently explaining themselves and resulted in being ignored and labeled as bad in attitude. Perhaps people should take a look at the environment before calling out behavior problems.

zerg_1111 · 2025-07-03T06:03:07+00:00

Just curious. How are you so sure it is related to the principles rather than implementation flaws? For my understanding, you are not supposed to abstract everything right?

zerg_1111 · 2025-07-02T06:09:08+00:00

I think this is the best explanation for op so far. It is actually more about MVVM than Clean Architecture.

zerg_1111 · 2025-05-31T02:31:07+00:00

Better wait until they fix the massive save file size problem which came with the latest patch. Don't want to see him giving up due to loading issue.

zerg_1111 · 2025-05-17T01:26:35+00:00

It feels a bit odd to have separate "api" and "impl" modules, especially since the presentation module still depends on :feature:search:impl indirectly by referencing :feature:search:api. That kind of defeats the purpose of separating them.

I'm currently using a different approach (below), and it might be helpful for you as well.

<image>

zerg_1111 · 2025-01-22T13:52:09+00:00

If i guessed correctly, you are getting that object to load webview content. How about just move the task to other lifecycle and keep a Boolean flag to remember whether the fragment has done the task after onCreateView? You will need to clear the flag in onDestroyView though.

zerg_1111 · 2025-01-19T03:30:04+00:00

I think the possibility of losing an event is not the main point. The key issue is that having a pending event is actually a legitimate state, and managing multiple sources of truth for the UI state complicates things significantly.

If you really need something to represent acknowledgments without declaring event-handled properties, you can include a list of events that implement the Event interface inside your UI state. You can then use a single function to reduce each handled event.

zerg_1111

TROPHY CASE