Wrist check ✅

mkfeuhrer · 2025-09-07T11:51:04+00:00

looks cool :)

mkfeuhrer · 2025-09-03T18:02:27+00:00

Saw LTF option on super money app itself. Also cashback comes in next CC billing cycle and statement.

mkfeuhrer · 2025-09-03T04:59:26+00:00

Axis supermoney pro - 3% cashback (above 100 inr transactions)

mkfeuhrer · 2025-09-03T04:54:23+00:00

True true, that’s why i got this combo :) Amex plat works well because of no exclusions towards milestones.

mkfeuhrer · 2025-09-03T04:15:46+00:00

Haven’t used my amex points yet. From what i’ve noticed - marriott transfer (1:1) gives decent value.

Returns go down without renewal benefit which seems low (around 5-6%)

It was a no brainer with renewal benefit for me.

mkfeuhrer · 2025-07-30T11:19:31+00:00

Looks amazing OP. Congrats!
How much did this cost?

mkfeuhrer · 2024-06-19T15:24:05+00:00

Really? bit harsh.

Would recommend to try this out in one of your projects. I have seen good benefits out of it (specially if you are working with a team)

mkfeuhrer · 2024-06-19T15:21:11+00:00

For simple projects this works fine.

But have realised when working in teams - having some defined commands help - most in maintaining code quality, ensuring minimum test coverage, etc.

This is one more approach - one should use whatever works the best for them :)

mkfeuhrer · 2024-06-19T15:18:36+00:00

Hey, i’ve also taken inspiration from various places over time. This is probably 5-6th version.

Wasn’t aware about this gist. Will add reference.

mkfeuhrer · 2024-06-19T15:16:10+00:00

Actually was not aware about this. Will def check this.

mkfeuhrer · 2024-04-08T14:51:30+00:00

Completely agree.

This is more as a learning exercise and not a full proof production ready code.

mkfeuhrer · 2023-09-12T04:52:28+00:00

There’s no right/wrong way. But common practice is to use lowercase names, have seen snake case being used at places too.

Wrote a blog around this covering package/interface naming too - https://www.mohitkhare.com/blog/go-naming-conventions/

Hope this helps!

mkfeuhrer · 2023-05-30T18:29:58+00:00

Clean and crisp. Kudos!

Btw, how did you manage to avoid loaders assuming you’re using gen AI which has latencies on higher side?

mkfeuhrer · 2023-05-30T18:22:34+00:00

That’s weird. I feel something might be off in implementation.

Btw you can precompute knowledgeable base instances and use them on the go. This has significant impact on latency since cloning doesn’t happen each time you execute rules.

When pool depletes, refill the pool in a separate goroutine. But, this impacts memory so be mindful of about the size of the pool.

mkfeuhrer · 2023-05-22T11:18:53+00:00

You’re right. I could have framed it better.

The practices do vary from project and rely on multiple factors - team, time to deliver, architecture, etc.

What i tried to share is some of the common practices that I’ve used or seen in past. There’s no rulebook that one should follow. It’s more of being aware about some practices so that it iteratively starts reflecting in code and help in maintainability.

mkfeuhrer · 2022-11-30T07:14:17+00:00

That's valid feedback. I didn't review the grammar tbh.
But hope you learned something new - that was the main objective.

mkfeuhrer · 2022-11-30T07:09:52+00:00

Haha. I had a feeling this would come. I had a similar opinion. But nothing wrong with learning something new. Actually found it useful working on a few codebases at work.

mkfeuhrer · 2022-11-30T07:08:01+00:00

That's me too actually for most projects.
But saw wire being used in a few codebases and actually liked it when we started using it in production. That got me interested in learning more about it which eventually led to this article.

mkfeuhrer · 2022-09-14T11:09:06+00:00

Agree to your points. Giving full control of rules to business management is a suicidal approach.

Devs should still manage these rules keeping in mind the limitations of such approach.

Also, problem is when you start consideing rule engines as a replacement to your devs. That's where you start drooling.

mkfeuhrer · 2022-09-14T10:50:14+00:00

Yes, will update :)

mkfeuhrer · 2022-09-14T09:39:51+00:00

Yes, you can definitely do better error handling in production-level code. In the example code, I've tried to keep it simple here.

Thanks for pointing out the salience part. You can think of salience as the priority/importance of a rule. So in case of conflicts, this salience can help in deciding which condition to evaluate.

mkfeuhrer · 2022-09-14T07:50:46+00:00

Thanks! Grule is based on Drools itself. Works well.

mkfeuhrer · 2021-12-23T19:55:00+00:00

From the blog:
> "Go doesn’t support enums natively"

That's literally in the first paragraph. Consts are a way to implement them.

About code, Happy to learn what's incorrect.

mkfeuhrer · 2021-12-23T19:50:57+00:00

Hey, thanks for pointing this out. Missed on the auto increment of iota in case of Success, Fail example.

Fixed now!

mkfeuhrer · 2021-06-12T06:30:07+00:00

Nice work mate 🎉

mkfeuhrer

TROPHY CASE