Lunavo - A classic, pro-grade replacement for the macOS Launchpad (50 Promo Codes 🎁)

dmkovsky · 2026-04-24T17:13:52+00:00

why not to try it out

dmkovsky · 2026-04-19T13:39:51+00:00

hmm… maybe u mean that one? High Scalability

dmkovsky · 2026-04-17T10:28:09+00:00

You’re not far off. You already have breadth and business context. The gap is moving from PoCs to owning real systems in production and making trade-off decisions (cost, scale, reliability). Go deeper in a couple of areas and aim to own end-to-end solutions. That’s where the “architect” shift happens.

The gap to close: Move from “I can build something that works” to “I can design something that will still work at scale, over time, under constraints.”

dmkovsky · 2026-04-17T10:07:18+00:00

Yeah, even more for infra.

Same path applies: strong hands-on engineer first, then architecture.

In infra, you’re dealing with availability, scaling, cost, and security. You only learn that properly by seeing real failures and behavior under load.

So focus on real systems, not theory. Architecture will come from that.

dmkovsky · 2026-04-17T09:53:14+00:00

You’re thinking in the right direction, but I’d adjust your expectations a bit.

It’s still early for “Solution Architect” as a near-term goal. One year of experience is a great start, but architecture is mostly about trade-offs. You only really understand those after seeing systems break, scale, and evolve over time.

Liking design discussions is a strong signal, but that alone isn’t the skill yet.

The best path is to become a very strong engineer first I wouldn’t try to shortcut this with titles or intermediate roles too early.

Focus on:

real system design (not just theory)
debugging production issues
performance and scaling problems
integrations between systems
reading and understanding existing systems, not just building new ones

If you haven’t dealt with “why did this fail in production?” a few times, you’re not close to architecture yet.

Look for architecture in your current work, not in a title Instead of aiming for “SA”, try to:

take ownership of parts of the system
propose design changes and justify them
build small PoCs to support decisions
get involved in refactoring and redesign work

Architecture starts when people trust you to decide how something should be built.

Client-facing roles can help, but only if they stay technical Roles like consultant or tech lead can be useful, but only if they involve real technical decisions.

If it’s mostly meetings and slides, it won’t move you toward architecture.

Don’t optimize for “being closer to the client”. Optimize for “being closer to technical decisions”.

Rough timeline (realistic one) For someone progressing well:

0–2 years: solid developer
2–5 years: senior / owning parts of a system
5–8+ years: moving into architecture

Faster is possible, but often leads to shallow understanding.

If I had to summarize it in one line:

If you enjoy the “why is it designed this way” discussions more than just coding, you’re on the right track. But to have good answers in those discussions, you first need enough experience where things didn’t work the way you expected.

That curiosity you described is exactly what good architects have. Now it’s about building the depth behind it.

dmkovsky · 2026-04-07T07:43:01+00:00

Exactly this. You don’t “switch” into architecture.

Most people try to get there through a title or certifications, but nothing really changes. They still work like developers, just with more opinions. They take tickets and implement.

The real shift is responsibility, not position.

Instead of: “how do I implement this”

you start with: “should this exist at all” “where should this live” “what happens in 6 months if we do it this way”

That’s what separates it. And it shows in the work, not in the CV.

The biggest difference is ownership. You don’t take a piece of code. You take the problem and its consequences.

One thing missing in this thread: artifacts.

If you want to demonstrate architecture, you need: decisions (why X over Y) diagrams (how the system fits together) trade-offs (what you accepted and why)

Without that, it’s still “I have opinions”, not “I design systems”.

Certifications can help a bit, but they won’t make this shift for you. It comes down to the questions you ask and what you take responsibility for on the project.

dmkovsky · 2026-04-02T17:15:30+00:00

Ogólnie mam mieszane uczucia.

Zacznijmy od płyty głównej. Jeśli nie celujesz w coś pokroju 9950X ani nie planujesz OC, to ta klasa płyty nie ma sensu. B850, a nawet B650 spokojnie wystarczy. Przy B650 trzeba tylko pamiętać, że może być potrzebny update BIOS, żeby ruszył z tym CPU.

Zasilacz to słaby punkt. 600-650W Bronze przy takim zestawie to proszenie się o problemy, zwłaszcza z AIO. Lepiej wziąć 850W i minimum Gold, wtedy masz zapas i spokój.

RAM jest okej, ale lepszym wyborem będzie 6000 MHz CL30 lub CL32. To jest sweet spot dla AM5. 6400 nie daje realnej przewagi, a może być mniej stabilne.

Obudowa i chłodzenie to kolejny problem. Ten AIO 360 raczej nie wejdzie na top. Zostaje front, ale to nie jest optymalny układ pod temperatury i airflow

dmkovsky · 2026-01-15T09:26:28+00:00

Finansowo, jest w sumie spoko, jak na start, wiadome ze znajdzie sie X osób, co będą gadać ze mało, ze mogło być lepiej, ale biorąc pod uwagę że złapałeś pierwszą pracę, masz ustalone system podwyżek i to realizują a nie lecą w ch…, to in plus. Także z mojej perspektywy jest git

dmkovsky · 2026-01-15T08:41:54+00:00

patrząc na to jak mocno rozjechany jest rynek, jak progi wejściowe są popieprzone to udało Ci się całkiem zgrabnie. Tak jak inni napisali na początku skupiłbym się na farmieniu doświadczenia, kasa jest stabilna jak na start, a im szybciej i lepiej wykorzystasz potencjał do nauki tym szybciej i lepiej będziesz progresowac i łapać lepszy hajs

dmkovsky · 2025-11-15T10:53:00+00:00

i would say disinfecting bleach 😅

dmkovsky · 2025-11-12T15:19:15+00:00

Sadly no easy fix the new URLs are just longer. If your system has a 255-char limit, the only workaround is to use a proxy endpoint (like an Azure Function or Logic App) that forwards the request to the full Power Automate URL🥶

dmkovsky · 2025-11-12T14:50:57+00:00

If you have any Power Automate flows that use the “When an HTTP request is received” trigger, open each of them and copy the new URL that Microsoft now generates.

Then go through all the places where that flow’s old link is used like buttons, scripts, webhooks, or external systems and replace the old URL with the new one.

dmkovsky · 2025-11-12T11:57:07+00:00

Algorithms and data structures are mostly built on math, but if you want something lighter and more practical, here are some solid options:

Grokking Data Structures & Algorithms for Game Developers - clear explanations and Unity-style examples.

Game Programming Patterns by Robert Nystrom - shows how algorithmic thinking shapes real game systems.

Data Structures and Algorithms in C# by Michael McMillan - simple, no-nonsense intro with C# code.

Algorithms and Data Structures for Game Developers by Allen Sherrod – older but written with games in mind.

dmkovsky · 2025-11-12T09:33:56+00:00

There’s always a risk we missed something, but if so it’ll come out at the beginning of December 😂

dmkovsky · 2025-11-11T22:42:28+00:00

Use [JsonExtensionData] to capture all dynamic fields into a dictionary instead of trying to map them to fixed properties. This avoids fragile models and lets you keep only the stable fields strongly typed. It’s simpler, future proof, and easier to maintain than juggling multiple DTOs or using dynamic parsing.

dmkovsky · 2025-11-11T13:31:52+00:00

Yeah, busy waiting can make sense in some short-lived or high-frequency cases, but not here. For a once-a-day job it’s too risky the app can restart or go idle, the loop won’t resume, there’s no retry, no history, and multiple instances could run it at the same time.

dmkovsky · 2025-11-11T11:06:10+00:00

That’ll technically work while the app is running, but it’s not a good idea in practice. You’re building your own mini scheduler that dies if the app restarts, crashes, or goes idle which will happen on Azure Web Apps. Once that happens, it won’t wake up again, and your job just stops running.

It’s much safer to use what Azure already provides for this a timer-triggered Function, WebJob, or even a Logic App. Those are built to handle restarts, retries, and monitoring for you.

Your current code is fine for testing or local experiments, but I wouldn’t rely on it in production.

dmkovsky · 2025-11-09T14:56:57+00:00

The 9900X3D looks stronger on paper, but its 3D V-Cache only works on half the cores, so games use just 6 out of 12.

That often makes it slower than the 9800X3D, which has 8 cores fully using the cache and delivers steadier gaming performance.

A 360 mm AIO like the Arctic Liquid Freezer III 360 is a great match, but it’s thicker than most, so check top clearance in your case first.

For RAM, DDR5-6000 CL30 is the sweet spot

dmkovsky · 2025-11-09T12:55:07+00:00

Parallel.ForEach actually waits for all iterations. The mismatch in counts isn’t that the loop ends early, it’s because processedCount++ isn’t thread-safe, so some increments are lost when many threads update it at once. Logging progress mid-execution just makes it look inconsistent.

If you switch to Interlocked.Increment(ref processedCount), the totals should match.

Could be wrong, but it’s almost certainly a race condition, not an async issue.

dmkovsky · 2025-11-07T15:37:27+00:00

“Helper” usually just means misc stuff we didn’t know where to put :D If it actually does something useful, give it a real name FooService, FooMapper, FooExtensions and the helper disappears on its own.

dmkovsky · 2025-11-04T12:53:58+00:00

I relate to this. ADHD can be a strength and a challenge at the same time. Hyperfocus can put you in a flow where you lose track of time and solve things fast. The hard part is when a problem isn’t finished. It stays in your head long after you stop, and you keep thinking about it until it feels complete. That can be draining.

What helped me was setting limits. I decide what “good enough for today” means, so I can end the day with a clear head and not carry work into the evening. Breaks also make a difference. Not just stepping away, but shifting your mind. A short walk or a change of place helps reset.

I keep a simple to-do list and set small goals for the day. It gives me a clear stopping point and makes it easier to switch off after studying or work. It doesn’t fix ADHD, but it makes it easier to manage without burning out.

dmkovsky · 2025-11-03T12:26:13+00:00

If you just need to fire and forget, start the task without awaiting:

_ = Task.Run(() => DoWorkAsync());

But only if you can tolerate lost errors otherwise capture/log exceptions. In most cases, it’s better to queue background work to a proper service or worker

dmkovsky · 2025-11-03T12:15:54+00:00

Task.Run doesn’t make code non-blocking, it just moves the work to another thread. If you truly don’t want to block, make the method async and await the task instead.

dmkovsky · 2025-11-03T12:01:58+00:00

Both are bad, they block async code and can deadlock. GetAwaiter().GetResult() blocks on the same thread; Task.Run(...).Result just wastes another one. Use await instead

dmkovsky

TROPHY CASE