Let me share the pain, and tell you HOW NOT to do software engineering.

Skill number1 you should have over your service: being able to quickly understand that some specific merge to master/main is in some deployment or no.

Typical application: you merged some fix pr that changes behaviour, you have 20+ deployments that are deployed incrementally, and you want to know whether this specific fix is in the deployment you are interested in (lets say some oncall has paged you and moved to bridge call asking this q).

Usually you have 2 things:
- metric that reports version per deployment
- tag WITH THIS version on the main branch that represents the state of code that got deployed.
These 2 MUST be easily correlated. So version on the dashboard and version on the tag must be either the same or easily derivable.

Now imagine, somebody created a service, that has version coming hell knows from where, git tags that contain completely different numbers and words comparing to version in dashboard, and here you go: some guy is asking you: can we check this thing is deployed to region X?

Guess how much time I spent to confirm it?
Did I confirm 100% in the end?
I as AI successful in helping answer these questions(has access to docs and git)?
🤡🤡🤡🤡🤡

I’ll be honest, sometimes I feel warm nostalgic feeling to Epam and other outsource companies. Maybe I was lucky, but typically I had so small projects that I could have context ABOUT WHOLE project at a time.
You know everything e2e, you have FULL mental model in your mind.

I didnt have this feeling for 5 years now😆

Daily (276/373 streak until LC cap)

The easiest "hard" problem implementation I have ever seen. Good problem, a bit hard to come up with intuition: check discussion tab.

My advice: try to think greedy: which task to process the first and what you want to have as the first task

https://leetcode.com/problems/minimum-initial-energy-to-finish-tasks/description/?envType=daily-question&envId=2026-05-12

#daily #hard #nopattern

Daily (277/373 streak until LC cap)

Pretty hard problem, should be hard definitely. And solution is pretty unintuitive.

https://leetcode.com/problems/minimum-moves-to-make-array-complementary/description/?envType=daily-question&envId=2026-05-13

#daily #medium #pattern

Daily (278/373 streak until LC cap)

For some reason didn't go from the first try for me today XD, maybe too much work at Snowflake.. But in general it is pretty easy

https://leetcode.com/problems/check-if-array-is-good/description/?source=submission-noac

#daily #easy

All this time I was trying to understand how vibe coding feels like to me and in general how my working day looks like.

Pretty accurate

Daily (279/373 streak until LC cap)

Today solid, good problem in first 200 Leetcode problems. Nice to recall binary search. Not that easy, requires to "go through examples" a bit.

https://leetcode.com/problems/find-minimum-in-rotated-sorted-array/description/?envType=daily-question&envId=2026-05-15

#daily #medium #pattern

Daily (280/373 streak until LC cap)

Actually can be solved with bruteforce with one line, but the solution is expected to be better than that.

https://leetcode.com/problems/find-minimum-in-rotated-sorted-array-ii/description/?envType=daily-question&envId=2026-05-16

#daily #hard #pattern

This guy waits for me every night, to have proper dinner

Yeeeeah instagram realized in 1-2 years I am done, and will need a switch. I clicked, no jokes

Daily (281/373 streak until LC cap)

Amazing problem, pretty easy to solve, and has well known pattern.

https://leetcode.com/problems/jump-game-iii/description/?envType=daily-question&envId=2026-05-17

#daily #medium #pattern

Daily (282/373 streak until LC cap)

Nice problem, it is not that hard, except one peculiarity that you need to do. It is good and has well-known pattern. Definitely recommend.

https://leetcode.com/problems/jump-game-iv/description/?envType=daily-question&envId=2026-05-18

#daily #hard #pattern

Yesterday’s dinner. Maybe you have already seen this guy, but I definitely recommend watching.

Atlassian laid off dev is showing system design of their infra. Pretty good system design btw. A lot of similar stuff we are doing at Snow rn.

Folks, do you see the last message with link?

Checking comments…

TELEGRAM WHAT THE FUCK


Are you doing A/B behind my back

This is the most interesting thing from the system design perspective

messages are sent in this order:

message1
message2
message3

===

Some people saw:
message1
message3

It tells a lot about their guarantees and potential implementation (at least gives an idea)

===

Leave your thoughts what could happen!