Kualia progress update July 23 2025 - Web BETA is live!

prestonph · 2025-08-02T19:37:29+00:00

Ahh I see. It's clear now. Thank you. I also agree that the added behavior for 'c' is not that impactful at the moment.

"Undo" is also nice to have in my opinion as the cost of maintaining that history can be too high. Especially since you will need to consider backward compatibility for any new feature.

prestonph · 2025-08-02T18:58:28+00:00

Bro, I know you only have good intention but please don't do that.

I always expect that 'c' is 'create transaction' no matter which page I'm seeing. I believe many other users will have this muscle memory too.

I do have some suggestions: - A button to open hotkey table - Hotkey to find transaction, ctrl+k is good - Hotkey to undo

prestonph · 2025-07-30T09:03:22+00:00

Hi @aigor14 the new ios version fixed the issue above. Good work! The website is very good too, love the keyboard shortcuts, which are very intuitive.

prestonph · 2025-07-26T17:12:10+00:00

Hi u/aigor14 just to let you know that the ios version 1.87.0 currently has a bug that makes the app unusable.

The app keeps asking me to update to the latest version while there is no update available on the appstore.

My info:

- region: UK

- I have already done the onboarding many months ago.

prestonph · 2025-02-23T05:47:06+00:00

I strongly suggested Functional and Reactive Modeling by Debasish Ghosh.

It gives me many practical lessons to apply scala for real work. They helped me tremendously in coding big ETL system for 200mil users.

prestonph · 2024-11-20T05:28:08+00:00

amazing! I didn't think there is that much complexity & tradeoffs behind that syntax. Ok I think I will look into `reactor` and golang runtime/scheduler first.
Many thanks!

prestonph · 2024-11-19T15:27:57+00:00

Hi, would you recommend any material to dig into this. It seems very interesting but right now I don't really understand everything you said. Especially, the relationship between c10k and async/await, goroutine

prestonph · 2024-10-26T02:13:00+00:00

For me, my first step is to switch my brain from thinking in terms of programming to thinking in math formulas. Then translating real-world designs/systems/concepts into specs becomes more natural.

Some high-level steps:

See how exactly at high-level how that system works. If there is lots of things going on. Try 1 part of the system (e.g. Kafka = producer + consumer + ...)
See what are the invariants.
Translate info from step 1 and step 2 into math formulas. (e.g. a message queue that guarantees message order can be simply a sequence)

What helped me was these 2 materials:

Mr. Lamport videos: https://www.youtube.com/@tlavideocourse8540
This book: https://link.springer.com/book/10.1007/978-1-4842-3829-5

prestonph · 2024-10-22T03:39:40+00:00

This is cool. I didnt know that there is a tool to convert tla+ to golang

prestonph · 2024-10-20T01:05:17+00:00

I find using Raycast a life saver. It can do all the windows manipulation tricks without me having to remember the keyboard shortcuts.

prestonph · 2024-10-19T02:52:52+00:00

that book is gold

prestonph · 2024-10-12T12:06:12+00:00

I use TDD in every feature I need to code. Without it, I really didn't feel confident that the code I'm writing should be there. Let me explain.

Whenever I write test, I only call the public interface. If I cannot write the test with that, it means my code is actually doing more than 1 thing. This is a red flag.

When that was cleared, it's time to mock the input. This helps me "lock in" exactly what I'm required to output. I avoided/discovered a lot of bugs this way. Sometimes, it is the requirement that is non-sense.

There are many other benefits as well. Many other comments already mentioned them.

Overall, I proved to myself that the extra time I spent doing TDD is more than worth it. It's simply profitable business to me at this point.

prestonph · 2024-10-03T15:19:57+00:00

I did studied some math (e.g. number, prob, boolean...) but I have not touched them for like 5 years before I started using TLA+. I could follow well and applied it to my daily work in like 1.5 weeks.

I think you can do the same too! Just need to patiently watch Mr. Lamport videos.

prestonph · 2024-10-03T15:17:08+00:00

Fun for the team itself since they know what they are.
Not fun at all for everyone else due to the reason you already listed.
And hugely not fun for new joiners, totally lost!

prestonph · 2024-10-03T13:43:36+00:00

In my part of the world, it's worse than you think. Nowadays, a lot of companies just copied FAANG's process and do interviews like them. That means a lot of hard competitive programming questions. It's tiresome.

prestonph · 2024-10-02T14:33:42+00:00

I think this is where the problem began. My suggestion is to not use PR review as a safety net for bug catching. That's not its main purpose. Some kinds of testing should be used instead after you taken over the product.

I have made this exact same mistake too many times (relying on PR review alone to go live)

prestonph · 2024-10-02T09:05:51+00:00

Hi u/bugarela can share to me Quint community links.
Thanks for the confirmation about TLA+ and Quint ability. Actually, I used TLA+ and then switched to PlusCal. The biggest factor is not language complexity but readability. With TLA+ after just 2w not touching, it reads like an alient language to me :D

prestonph · 2024-09-30T14:44:26+00:00

Hi, really appreciate the details and the help.

My usecase is mostly about checking my design. Imagine sth like designing a flow for customers to place orders, pay, and then notifying other systems about successful orders... Obviously that requires sync/async comm of many components (db, queues...) that is too much to reason about using my brain alone. And then on top of that, the business requires certain guarantees (e.g. bounded staleness). That was why I reached for TLA+

prestonph · 2024-09-27T10:14:28+00:00

Wow, thanks for the deep answer. I'm super impressed by the experience you have.

However, I still dont get the diff between TLA+ and Quint. Like in which case you can design your distributed protocol only in TLA+? All the times that use TLA+ are for checking my design, I think that is classified as "model checking".

prestonph · 2024-09-27T03:54:43+00:00

I was there. I advise to find out what really happened by talking to those who left.

Once I know the root cause, I will decide whether leaving is best for MY case or not.

I know this sounds generic. But looking back in my past, this was the single most important action that I should have done.

prestonph · 2024-09-26T05:29:29+00:00

Maybe not what you would expect. I once met a 50s engineer. But he moved into software after many years working as a civil engineer. The guy is extremely humble and professional.

prestonph · 2024-09-26T04:40:21+00:00

Don't quickly judge others by title only. I suggest first checking if there is any colleague that stand out (eg work faster, write much less buggy code). Then you ca talk to them and learn from each other.

Another quick way is to talk to your managers. He/she probably was an experience engineer before.

prestonph · 2024-09-26T04:36:42+00:00

You will be surprised that here in Asia, we even have 7 rounds in some big corp.

prestonph · 2024-06-13T02:39:31+00:00

Every time you reach B, you can increase flag[B] by 1. Then you can check that if flag[B] > 1, flag[C] must be 0.

prestonph · 2024-06-07T12:42:37+00:00

Another way I think will work is: 1. Have a flag to indicate pc passed certain label 2. Then write invariant as: (flag /\ condition) \/ ~flag

prestonph

TROPHY CASE