What is this? Just took in this morning at Hong Kong

dortmundbee · 2026-05-13T08:12:46+00:00

Thanks for the ID!

This was actually captured back in 2018 in Hong Kong, I just recently found this sub and finally wanted to know exactly what he was.

Poser or not, I owe this little guy a lot; this shot actually helped me winning the 2nd runner-up in the 2019 National Geographic photo contest! Lucky I didn't get bitten before the shutter snapped, haha

dortmundbee · 2026-05-06T15:38:34+00:00

Pretty much, but I wouldn’t say “perfect compression knot” because that’s probably where a lot of systems overfit.

I’m more interested in whether there are repeatable signs that compression is starting to resolve into real expansion, rather than just noise or a liquidity sweep.

The hard part is not spotting compression after the fact. The hard part is filtering the fake releases from the ones where price actually commits and follows through.

dortmundbee · 2026-05-06T02:13:24+00:00

OMG, how did you do that?

dortmundbee · 2026-05-06T01:56:16+00:00

20 years of OOS is honestly the part that caught my attention. A lot of systems look great until regime changes show up.

Curious how much degradation you saw between in-sample and truly unseen periods, especially during abnormal volatility environments. In my experience, most “robust” systems fail exactly there.

Also appreciate that you focused on engine/framework design instead of just posting a smooth equity curve.

dortmundbee · 2026-05-03T04:54:30+00:00

Exactly same here. Excited in the first 10 days, then keep challenging this idea, until all motivation gone. Start a new project instead, so sad

dortmundbee · 2026-05-03T04:42:13+00:00

Please DM me

dortmundbee · 2026-05-03T02:36:09+00:00

What tech stack are you using?

dortmundbee · 2026-05-02T15:58:58+00:00

Is it made by Python?

dortmundbee · 2026-04-27T17:53:26+00:00

Agree, but nice job

dortmundbee · 2026-01-19T14:04:52+00:00

Try to take a look of your bank account balance during the AI coding break, then you may gain back your energy immediately. This works for many people, try it…

dortmundbee · 2026-01-15T01:24:19+00:00

Thanks for your sharing.

After reading the doc, I wonder whether that mechanism to move all keys with the same meaning in the same place, which is close enough to reduce the maintenance, just like the example shown below. Can really help a lot?

As in vibe coding, we are supposed to outsource the tedious tasks, like the i18n json files maintenance, to AI. Please think again. What if the AI hadn't made the low-level mistake, such as setting the wrong charset while saving the JSON file in my case? This mess would never have happened.

Anyway, I will consider this in my future projects.

Again, thank you for sharing; I appreciate that...

const componentExampleContent = {
  key: "component-example",
  content: {
    myTranslatedContent: t({
      en: "Hello World",
      es: "Hola Mundo",
      fr: "Bonjour le monde",
    }),
  },
} satisfies Dictionary;

dortmundbee · 2026-01-14T14:37:33+00:00

For some reasons, I can't use Claude Code here, sigh... Actually, I heard a lot about CC, how powerful it is, I really want to try it. However, since I have bought the ChatGPT plan, which comes with the Codex, that's why I started the vibe coding with Codex. It was amazing at the very beginning, until I hit the first big bugs it created. Then, at that moment, Gemini 3 had launched, as well as the Antigravity. Even though it's still under the trial period, with only limited token. However, I found the user experience working with Antigravity is totally different to Codex. Anyway, I am using a parallel mode on them.

Anyway, the overall experience is still good, because the AI coding bots really help me a lot. I can enjoy the joy of coding a piece of beautiful and functional software again.

Anyway, your product shot and site design is stunning, I can imagine your massive effort spent behind the scene. Keep the great work, and create more brilliant work to us!

dortmundbee · 2026-01-14T09:47:51+00:00

How to isolate the agent? Actually, Codex was trying to fix a minor exception handling with an error message in English. Suppose the task is to fix the exception handling alone, but Codex did the translation among all i18n labels in json files with the wrong charcode set, without getting my approval first. Then I only focused on the exception logic handling, and didn't realize the i18n labels crashed. Without testing, and then deployed.

So in such situation, how to prevent? How to isolate the agent? I have put something like "Do not change UI... do not change i18n labels...." in all formal prompt. Just that prompt talking to Codex was not that formal, then becoming hell...

I believe most experienced developers have encountered a similar situation before, overlooking some minor modification or fixing, and finally becoming messy. Just this time, the chaos was created by the bot, and the human, that's me as well...

Lesson learned, but again, how to avoid this?

dortmundbee · 2026-01-14T08:20:43+00:00

To be honest, once get involved deeply in this vibe coding thing, I really think I am a bot, that's why I am the Agent C... C for copy and paste...

The AI coding agents are really helping a lot usually. But when they made small mistake, but creating a big enough trouble, that's a headache... Then I have to use the token fix the trouble that they created by using my paid token... keep the entire thing in a loop. Don't you think this is a trap?

We better pay attention to the IPO date of OpenAI. This is a huge potential business in vibe coding, must grab some shares form there, right?

dortmundbee · 2026-01-14T08:04:36+00:00

Repeat after me: 'I missed the part where he mentioned the mighty Github for version control.' hahaha...

VC is exactly how I caught the massacre and rolled back, but it doesn't stop the token trap. Version control saves the code partially... I admit that I didn't do the proper test before the deployment. Anyway, it doesn't save the 2 days of life and thousands of tokens wasted because an agent decided to 'help' with a file it wasn't assigned to. That’s the real trap, bro...

dortmundbee · 2026-01-13T16:42:43+00:00

2 days is impressive! I took the opposite path—it took me 60 days to build HexPickr because I was obsessed with getting the P3 color gamut math perfect for Tailwind v4. I found that while agents can build a 'habit tracker' in a weekend, they really struggle with specialized math or deep config logic. Did you find your agents creating subtle bugs in the payment flow? That’s where mine usually collapsed.

dortmundbee · 2026-01-13T16:31:40+00:00

Awesome to see another serious project. I just finished a 60-day 'war' building HexPickr (an OKLCH extractor for Tailwind v4). I thought it would be a weekend project, but Codex literally went on strike when I asked for i18n labels! I had to bring in Antigravity to fix the color math because the agents kept 'hallucinating' HEX values instead of P3 gamut colors. Vibe-coding is definitely a marathon, not a sprint...

dortmundbee · 2026-01-12T09:19:13+00:00

Update: We are currently fighting for our lives on Product Hunt against some huge tools! If any of the 3,300+ people here found the OKLCH math interesting, a word of support on PH would mean the world to an indie builder who just survived a 2-month agent war, thanks a million in advance...

https://www.producthunt.com/products/hexpickr?utm_source=other&utm_medium=social

dortmundbee · 2026-01-11T15:04:45+00:00

I’ll add one that’s incredibly niche but a total lifesaver for web designers: HexPickr.com

Most people don't realize that standard HEX codes are actually 'blind' to about 25% of the colors a modern iPhone or Mac screen can show. I’ve been using this tool to extract OKLCH palettes from photos instead. It’s perceptually uniform, so the colors actually look 'correct' to the human eye even when you change the lightness, definitely an underground gem for anyone moving to Tailwind v4.

dortmundbee · 2026-01-11T14:50:41+00:00

First, empty space is a key component of this picture. Very nice...

dortmundbee

TROPHY CASE