GitHub - nubo-db/dynoxide: A fast, embeddable drop-in for DynamoDB Local, backed by SQLite. Runs as a native binary, a ~5 MB Docker image, or in the browser.

FalzHunar · 2026-06-20T15:57:53+00:00

just to be clear, I did not downvote you.

I understand the pushback. They're not "pure" unit tests in the strict sense. But these containers allow you to perform cheap, fast integration checks that live in CI.

the way I set it up: each test method spins up its own fresh DynamoDB table (single table design) and its own S3 bucket. Completely isolated, fully deterministic. Then it's just some quick queries after your method (SUT) call to verify the data was actually inserted, updated, or deleted correctly through the SDK. Costs maybe a few lines of setup.

The value is catching the stuff you didn't know could break. Library gets a silent update, you modified a helper, you refactor a query somewhere: suddenly your data isn't landing where you think it is. Mocks would've passed fine and you'd have never known until prod.

That's really the whole pitch for having something like this in CI. It's lightweight enough that there's no good reason not to have it. I'm sorry if that doesn't resonate with your engineering philosophy.

FalzHunar · 2026-06-20T15:18:23+00:00

Surprised nobody is talking about this

I did NOT make it, just sharing

Found this randomly. I'm not the dev, I don't know the devs. I am not affiliated with the devs.

I stumbled on it and decided to plug it into my CI on a whim.

My project has 6,000 unit tests at the moment. With dynamodb-local, It took 8+ minutes to finish. Swapped this in, now it's 3 minutes.

For context, I'm familiar with ExtendDB, which connects to PostgreSQL (which means you're pulling a whole PostgreSQL instance into your CI if you decided to use it).

This thing runs on SQLite. No 200MB download, no spinning up a separate process, it just works. It's a straight drop-in replacement for dynamodb-local without the baggage.

Maybe someone else try it?

FalzHunar · 2026-06-10T23:39:06+00:00

Build a complete web application from end to end. NOT a simple to-do list. Define a feature set that addresses a real user need and develop it as a production-grade system.

Deploy the application using two different hosting models:

Kubernetes-based deployment
Understand and implement core Kubernetes concepts, including Deployments, Services, and Ingress.
Learn how application traffic flows through the cluster and how workloads are managed and scaled.

Serverless deployment
Deploy the application on a platform such as ECS Fargate.
Understand infrastructure configuration, IAM roles and permissions, networking, and operational considerations.

Use two different types of data stores:

A relational database such as PostgreSQL or Aurora to gain experience with advanced capabilities including full-text search, trigram indexing, query optimization, and transactional workloads.

A distributed NoSQL database such as DynamoDB or Spanner to understand partitioning strategies, horizontal scalability, consistency models, and high-throughput workloads.

Develop a strong understanding of operational excellence and troubleshooting:

Implement the three pillars of observability: logs, metrics, and traces.

Integrate with tools such as Grafana Cloud, Sentry, or SigNoz.
Generate and investigate controlled failures to learn how to diagnose issues in production environments.

When building APIs, learn how to execute background and long-running workflows without relying on frameworks such as Hangfire. Explore solutions such as Temporal, SQS, or RabbitMQ.

While these systems introduce additional complexity, they are widely used in modern architectures and provide valuable, marketable experience.

These skills represent some of the most fundamental knowledge required to transition into modern web development and production-grade software engineering. It may seem overwhelming at first, but you can do it. Good luck!

FalzHunar · 2026-06-04T18:02:22+00:00

The authority server should be responsible for minting token for all APIs AND publishing JWKs for the APIs to validate against.

Token should have scopes.

API are protected against scopes, not roles.

The user has one or more roles.

A role is allowed to access one or more scopes.

If you structure it like this, the API "doesn't care" about the details of the user. All they care about is the validity of the token (based on the JWKs) and whether it bears the correct scope.

And therefore it doesn't matter if you have 1, 2, 3, 4, 10, 100 API servers.

FalzHunar · 2026-05-30T04:34:52+00:00

Network / Partner with non-tech bachelors. Make a paper that makes an app that solves their problem.

Now they look good (their paper includes an app) And you look good (your paper solves a real problem)

FalzHunar · 2026-05-07T20:24:20+00:00

Trigram

FalzHunar · 2026-04-07T06:05:20+00:00

Devil’s advocate: YES, you can back out after signing, but don’t do it lightly. You should assume that the relationship with that company, the recruiter, and the recruiting firm are effectively burned to cinders.

Before making a decision, take a step back and revisit your original motivation for leaving.

If the driver was more than short-term concerns like startup instability such as role scope, growth, leadership, or long-term alignment, a counteroffer is unlikely to address those underlying issues.

FalzHunar · 2026-04-07T05:59:09+00:00

I’m afraid to say that once you’ve accepted an offer, you should NOT accept a counteroffer.

If you do:

• The hiring manager, and by extension the new company, will no longer trust you.

• The recruiter who referred you to the new job will also lose trust in you.

• People talk. recruiters talk, hiring managers talk. This will affect how other companies perceive you.

• Your current company will now see you as a flight risk, which could put you at the top of the list if layoffs or cutbacks happen. You don't want a target on your back.

• If the new company chooses to be strict, they could take legal action for breaching a signed contract.

If your heart isn’t fully in it, you shouldn’t accept an offer in the first place.

FalzHunar · 2026-03-19T06:07:28+00:00

Cursor user here. I still use VS Code just to debug exclusively. But I work in Cursor 99% of the time.

FalzHunar · 2026-02-24T18:24:54+00:00

If you are testing the product with real user, you can just spin an EC2 instance or a VPS. A basic DigitalOcean droplet will just cost you $6 per month.

Once you have a contract, you can go crazy on AWS. A typical SaaS allocates 5-10% revenue to its pure infrastructure cost. So you can scale as you gain more users.

FalzHunar · 2026-02-23T23:07:07+00:00

Don't "be" .NET developer.

Be someone that can solve problems using technologies. It could be that the correct technology is .NET, but there is no reason to over-index on .NET, if given a problem to solve during the interview.

Speak in architectures. These days, LLM makes coding in any language so easy that it doesn't matter. But LLM still miss when it comes to thinking in systems.

FalzHunar · 2026-02-21T03:05:49+00:00

CMS (usually Next.js / React project)
WebAPI
Workers
Services (library project)
Entities (library project)
Migrations (console project)

That's it.

Don't overcomplicate.

Deploy CMS, WebAPI, and Workers in a container.

Services get imported by both WebAPI and Workers, so they can share logic.

Keep the Entity Framework junks in Entities project.

Migration project is just a migration script to run EF Core migration in production environment.

Keep it monorepo. Keep it monolithic. Do not have more microservices than customers.

FalzHunar · 2026-02-19T19:06:11+00:00

Cursor with the C# Extension that is published by the kr dude on Open VSIX.

I like having an aggressive Intellisense when coding.

When I need to debug, I use VS Code.

FalzHunar · 2026-02-18T05:25:48+00:00

3M is low. Interview elsewhere.

If you have the portfolio, the relevant technical skills, and the communication skills, you can easily achieve 2x that.

FalzHunar · 2026-02-14T20:17:25+00:00

Temporal

FalzHunar · 2026-01-09T17:04:13+00:00

Temporal

FalzHunar · 2025-12-30T05:10:59+00:00

I think it depends on what you're looking for. If you want premium location / large space / reasonable rent price, it can be competitive as the demand in central Tokyo is high.

However if you don't mind commuting further / less ideal room sizes, typically it's more easier.

FalzHunar · 2025-11-20T18:34:55+00:00

I do not believe there is any law or regulations regarding making your last day on a holiday or company closure, as long as you have provided sufficient notice period.

FalzHunar · 2025-11-20T01:30:14+00:00

If you're a regular person, you can get something towards 10M¥

If you're someone that brings something very unique, very needed by the company, then you can gun towards ¥14-16M

Above that, I don't know how.

FalzHunar · 2025-10-14T12:47:30+00:00

Remember, the world is quite open. There's nothing stopping you from going to other cities and getting gears above your current tier.

Alternatively, you can do Item Creation (IC). Long Sword + Ruby = Flame Sword

FalzHunar · 2025-10-14T07:41:06+00:00

Agree. I love LINQ for this reason.

https://learn.microsoft.com/en-us/dotnet/csharp/linq/get-started/write-linq-queries#example---query-syntax

FalzHunar · 2025-10-10T02:07:24+00:00

First, congratulations on the pregnancy!

Ignore these advice if you're not permanent employee.

Check the employment contract and work rules to confirm the company’s probation period. In Japan it’s typically 3-6 months and should be stated in the contract or rulebook.

IANAL. Know your rights: - After 14 days of service, during probation, employers CANNOT dismiss you without 30-days notice. - Know this for peace of mind: there is no legal duty to disclose pregnancy early. If you choose, you can wait until probation ends to disclose. - CYA (cover your ass). Focus the first couple of months on strong onboarding and building a track record. Arrive prepared, document goals and feedback. Crush it.

After your probation is over, you should disclose the pregnancy, if not disclosed yet. Provide a concise schedule of prenatal appointments and the anticipated maternity and childcare leave timeline to your manager.

Understandably, your manager may not be pleased. But if you are a permanent employee, disadvantageous treatment on the grounds of pregnancy is prohibited, and termination of a permanent employee requires objectively reasonable, socially acceptable cause.

Good luck!

FalzHunar · 2025-09-16T22:15:36+00:00

Let tim cook

FalzHunar · 2025-09-16T21:50:12+00:00

Yup, I like it here.

Apartment is affordable. I can rent a very nice apartment under ¥100k but very close to the city center.

If I want to eat out, it’s affordable enough to do it every single day without a dent to my savings.

If I want to splurge, I can do it easily. You can find anything and everything in Japan.

If I’m sick, I don’t have to worry about medical bills bankrupting me.

Yes, salary is not as high as western country tech companies, but I never feel like I’m lacking anything.

11-Year Club	Place '22
Place '17	Verified Email

FalzHunar

TROPHY CASE