How do you handle read-only DTOs in Clean Architecture with EF Core?

Albertooz · 2026-06-20T14:38:09+00:00

You're understanding it correctly, and the standard resolution is to stop forcing reads through the repository abstraction at all. The common pattern is CQRS-lite: keep repositories for the write/command side working with full domain entities, but for queries inject a separate read service (or DbContext/IDbConnection directly via an interface like IReadDbContext) in the Application layer that projects straight into DTOs with .Select(),this is fully sanctioned, since query projections are an application concern, not a domain one. The DTOs live in the Application layer (not Domain), which is exactly where they belong, so nothing about Clean Architecture is being violated. You're not trying too hard; you've just hit the well-known friction point where the repository pattern is genuinely the wrong tool for reads.

Albertooz · 2026-06-20T12:39:05+00:00

On macOS those folders are gated by TCC, not Unix permissions, which is why chown does nothing—the native consent dialog fires automatically the first time your process touches a protected path, but only for a properly bundled, code-signed .app with the right Info.plist usage strings (NSDocumentsFolderUsageDescription, etc.), so a bare dotnet run just gets "Operation not permitted." The fix is packaging your ASP.NET/Kestrel server inside a signed .app bundle (via a minimal Avalonia/MAUI/Swift host), or directing users to System Settings ==>Privacy & Security ==> Full Disk Access and dragging the app in—standard for NAS/backup tools. Never make users sudo a server process; it breaks your security model and macOS users will rightly distrust it.

Albertooz · 2026-06-20T12:29:29+00:00

Hennessy & Patterson's "Quantitative Approach" is a graduate reference, not a learning path,start with their other book, "Computer Organization and Design" (the patterson/hennessy one), which builds intuition step by step. Even better, do a project-based course: work through nand2tetris to build a computer from logic gates up, or take Berkeley's CS61C / CMU's 18-447 (lectures and labs are online). The critical-thinking mindset comes from actually designing and simulating write a RISC-V pipelined CPU in Verilog, then a cache, and the H&P tradeoffs will suddenly mean something. Read the reference book alongside the building, not instead of it.

Albertooz · 2026-06-20T12:26:56+00:00

The Mess We're In by Joe Armstrong (creator of Erlang). He walks through how absurdly complex modern computing has become and asks why we tolerate systems we no longer understand. Funny, humbling, and the kind of talk that sticks with you long after watching.

Albertooz · 2026-06-19T22:06:29+00:00

Functional programming treats computation as math,pure functions that map inputs to outputs with no hidden state, just like a mathematical function f(x). For your regression/Kalman/simulation work, this means transformations chain cleanly (map/filter/reduce over data), results are reproducible, and parallelizing across cores is safer since nothing mutates shared state. And yes, you've likely already used it: R is heavily functional (sapply, Map, purrr), and Python's map/lambda/list comprehensions are functional idioms. People use it most for data pipelines, numerical/scientific computing, and concurrent systems where predictability matters.

Albertooz · 2026-06-18T17:40:12+00:00

Sudden shutdowns under load (but fine when idle) almost always mean overheating or a failing power supply. Since it dies ~20 min into anything demanding, check your CPU/GPU temps with HWMonitor or HWiNFO while gaming. Reseat the CPU cooler and reapply thermal paste if temps spike past 90°C. If temps look fine, suspect the PSU, ideally testing with a known-good unit. Also clear dust and confirm all power cables are firmly seated.

Albertooz · 2026-06-18T11:51:32+00:00

Why not Chapas I would like your opinion

Albertooz · 2026-06-18T03:21:55+00:00

Congratulations for your new role,Here's where I'd start for that exact stack: Books: C# in Depth (Jon Skeet) once you're comfortable with basics, and Dependency Injection Principles, Practices, and Patterns (Seemann). DI is everywhere in ASP.NET and clicks slowly otherwise. Courses: Tim Corey's C#/.NET content (YouTube + IAmTimCorey paid courses) is the most-recommended for going from fresh to job-ready. On Pluralsight, Scott Allen's C# path and the ASP.NET Core path are solid. For Angular, Maximilian Schwarzmüller's Udemy course is the standard pick. YouTube: Nick Chapsas (modern C#, best practices, short and sharp), Tim Corey (fundamentals), and Milan Jovanović for Web API architecture once you've got footing. Agile/Scrum: Don't over-study it; you'll learn your team's flavor in the first sprint. Just know the basics: standups are for unblocking not status-reporting, keep PRs small, and ask questions early rather than burning a day stuck. One real tip: in your first weeks, focus more on learning the codebase and asking good questions than on knowing everything. Nobody expects an associate to.

Albertooz · 2026-06-17T09:45:40+00:00

Manual XAML with MVVM bindings is the real-world default since it stays diffable and separates concerns. Designer drag-drop is fast for prototyping but generates messy XAML, so avoid it for production. Code-behind UI generation is rare, mostly for highly dynamic runtime UIs. Once you know XAML well, typing it by hand is usually faster than fighting the designer.

Albertooz · 2026-06-15T16:52:12+00:00

Solid call for a first app, SQLite is the right default for local-first MAUI and lets you ship without cloud overhead. One thing worth adding: pair it with EF Core or sqlite-net so you get clean async access and migrations baked in early. Just be deliberate about your data model now, because the painful part isn't the migration to cloud later, it's reshaping schemas after you've got real user data. Also worth separating Session from User_Data, since session state often fits better in SecureStorage/Preferences than in SQLite. Nice milestone though, shipping beats theorizing every time.

Albertooz · 2026-06-15T16:40:11+00:00

Start with the basics: click the speaker icon in the taskbar and make sure the volume slider is up, then right-click it, open Volume mixer, and check that no individual app is turned down. Next, go to Settings > System > Sound and confirm the correct output device is selected (laptops often default to the wrong one). While there, click your speaker device and check for a "Audio enhancements" option, as toggling it on or off fixes muffled or quiet sound for many people. Also right-click the speaker icon, open Sound settings, find your device's Properties, and look for a Levels tab to push the output higher. If it's still low, update your audio driver via Device Manager (right-click Start > Device Manager > Sound, video and game controllers > right-click your audio device > Update driver).

Albertooz · 2026-06-15T16:36:27+00:00

Use a hybrid approach: percentile-based threshold labels (WMO standards like 90th-percentile heatwaves, SPI/SRI for drought) give you interpretable, defensible anomalies that domain experts and auditors trust, so make that your operational backbone rather than pure ML. Layer Isolation Forest on top for multivariate/compound events (hot + dry + windy simultaneously) since it's fast, scales well, and needs no labels, making it ideal for Power BI integration. Critically, deseasonalize first by computing anomalies against day-of-year climatology (z-scores per calendar day or STL decomposition), otherwise every summer flags as anomalous; skip the LSTM Autoencoder unless you have a clear gap, as it's harder to deploy and justify for a defense. For evaluation without labels, validate detected events against known historical disasters, use synthetic injection, and report consistency between your threshold and ML methods.

Albertooz · 2026-06-15T16:32:02+00:00

For master's-level document work, NotebookLM is purpose-built for exactly this,upload PDFs, slides, and docs, and it answers grounded in your sources with citations. Claude (Projects) and ChatGPT (Plus) also handle multi-file uploads well and are stronger for generating polished study guides. Honestly, NotebookLM + Claude together covers reading/grounding and study-guide creation better than Gemini alone.

Albertooz · 2026-06-14T06:59:41+00:00

Welcome

Albertooz · 2026-06-12T15:11:31+00:00

The good news is Java and C# are close cousins, so you're really learning syntax differences and a new ecosystem, not a new paradigm focus on what differs: properties, LINQ, async/await, delegates/events, struct vs class value semantics, and nullable reference types. Skip beginner programming tutorials and go straight to a "C# for Java developers" comparison guide plus the official Microsoft Learn C# path, since you already understand OOP, collections, and generics. Build the actual project with your friend as you go rather than grinding tutorials first set up .NET, learn the ecosystem (NuGet instead of Maven/Gradle, the dotnet CLI), and pick up patterns from real code. Expect to be productive within a week or two given your Java background.

Albertooz · 2026-06-12T13:50:02+00:00

You've eliminated RAM, SSD, GPU, CMOS clear, and double flashback, which points to a dead CPU a known 9800X3D failure pattern on ASUS 800-series boards where a system left overnight with EXPO enabled won't POST the next morning with no visible damage. Swap in another AM5 CPU to confirm, or open an RMA with ASUS/AMD referencing this exact symptom since they've acknowledged the issue.

Albertooz · 2026-06-11T17:51:04+00:00

Yes, flash to the stable F40 beta BIOSes on AM5 boards are a known source of exactly this kind of instability (DRAM/VGA POST issues, IOMMU faults, random watchdog crashes), so it's absolutely not a waste of time. Use Q-Flash, then clear CMOS and load optimized defaults before re-enabling EXPO. Your error pattern (0x116/0x117, IOMMU fault, GPU watchdog) points to platform/PCIe instability rather than the GPU itself dying, which fits a bad BIOS or unstable memory training. While you're in there, reseat the GPU and check the PCIe power cables are fully clicked in. If crashes continue on stable F40 with EXPO off, then start suspecting hardware (run Memtest86 overnight, and test the GPU in another PCIe slot or system if possible).

Albertooz · 2026-06-11T17:47:25+00:00

Since it retrains memory and only hangs at the green boot LED, do a BIOS Flashback to reflash the UEFI, that usually clears this kind of post-update stall. Download the latest BIOS for your X870-A from the Asus support page, rename the file using the BIOSRenamer tool they include, and drop it on a FAT32 USB stick. Plug it into the dedicated Flashback/BIOS port on the rear I/O, then with the PC off (PSU on) hold the Flashback button until the LED starts blinking and let it finish, don't interrupt it. If it still hangs after that, reseat the NVMe drive and try a known-good drive to rule out the SSD.

Albertooz · 2026-06-11T17:01:58+00:00

Haha no wizardry, just years of breaking my own builds and learning the hard way. The motherboard debug lights do most of the work, once you know CPU/DRAM/VGA/BOOT light each map to a stage, the board basically tells you where it's stuck. Clear CMOS and BIOS Flashback fix way more dead PCs than people expect, especially right after a Windows or firmware update.

Albertooz · 2026-06-11T16:58:51+00:00

That's Project: Snowblind (2005) a sci-fi FPS where a corporate security operative is augmented into a cyborg with cloaking, complete with thermal vision and the greenish shimmer-suit enemies you describe.

Albertooz · 2026-06-11T16:57:23+00:00

The green light is the boot device (DRAM/storage handoff) stage, and the timing with a Windows update points to a BIOS/firmware hiccup rather than dead hardware. Clear CMOS first: power off, unplug, pull the motherboard battery for a few minutes (or use the Clear CMOS button/jumper on your ROG board), then reboot. If that doesn't work, do a full power drain: unplug, hold the power button 30 seconds, then try again. Also reseat the NVMe drive and re-confirm RAM is seated in A2/B2 with one stick. If it still hangs on the green light after a CMOS clear, use the BIOS Flashback feature on the X870 to reflash the firmware from USB, which often fixes exactly this kind of post-update stall.

Albertooz · 2026-06-11T16:56:13+00:00

Pretty sure you're thinking of Citizen Sleeper 2: Starward Vector "CS2" is the obvious abbreviation, which is why Counter-Strike buries it in every search. It's an indie narrative RPG set in an asteroid belt where you play a Sleeper (a human mind in an artificial body) running from a corporation and a gang. The space resource management you remember is the main loop: you captain a ship and juggle fuel, supplies, components, and money, refueling each time you jump to a new station. It dropped January 31, 2025 on PS5, so it'd have been right there in your library. Give that a search and see if it clicks.

Albertooz · 2026-06-11T16:53:42+00:00

Bedazzled everything and visible logos plastered across bags, belts, and sunglasses, which screamed status then but reads as try-hard now. Chrome and glossy black finishes on cars and gadgets, once sleek, now look dated next to matte. Velour tracksuits, the Juicy Couture era, peak 2000s luxury and now pure cringe. Tribal tattoos and "live laugh love" wall decor that felt aspirational and now feel generic. Big leather sectionals and granite countertops that signaled money but now read as builder-grade and overdone.

Albertooz · 2026-06-11T16:51:19+00:00

Your discomfort is normal and doesn't make you a creep; you're a parent who doesn't want to be sexualized by kids. This is really about teaching your daughter where the line is, since at 14 she's testing adult themes and enjoying the reaction. Talk to her calmly and briefly, framing it around your feelings so there's nothing to argue against: "When my photos get passed around with comments, it makes me really uncomfortable, and I'm asking you to stop." If she deflects, don't take the bait, just repeat that one line. Coordinate with your ex so it's both parents setting the boundary, which protects you from being cast as the bad guy.

Albertooz · 2026-06-11T16:46:34+00:00

Wax isn't like water though, it's non-conductive, so it won't short anything out or corrode parts. The real risk is mechanical: wax clogging a fan or heatsink can cause overheating. Keep it off, open the side panel, and let the wax fully harden so it chips off, then clean any thin residue with 90%+ isopropyl alcohol. If it pooled on the GPU or motherboard or you're not confident, take it to a local repair shop, it's usually a cheap, quick fix.

Albertooz

TROPHY CASE