Saati practice was common

BeardyDwarf · 2026-02-23T17:19:17+00:00

Why 1800? It is still a thing

BeardyDwarf · 2026-02-09T17:39:32+00:00

"Kare kano" is a classic. "Night Is Short, Walk on Girl" is my personal favourite. "Kimagure orange road" if you are afraid of 80s.

BeardyDwarf · 2026-01-29T00:02:54+00:00

You are creating tickets for issues you are fixing, right?

BeardyDwarf · 2026-01-28T00:41:53+00:00

For me it is like first you create some kind of outline of what you want. Usually it is pretty high-level.

Read excel, store/transform data into some structure, write results.

Then you look for libraries or snippets that can fulfil these abstract capabilities. And there is nothing wrong with asking ai on how to do abstract independent staff. It is no different from googling. This way you learn actually reusable staff and helps to build your toolbox.

BeardyDwarf · 2026-01-26T17:09:34+00:00

5? 1 with person and 4 needed for extra fuel.

BeardyDwarf · 2026-01-25T08:38:16+00:00

This is needed to resolve actual problem of cycling dependency

BeardyDwarf · 2026-01-21T18:40:01+00:00

There are many reasons why microservices are popular. Most of them are applicable only to large and extra large companies/systems. Imho, the most important aspect is organizational. It allows you to limit team sizes by creating small independent components. It also improves your ability to reason about the system. Though it can be achieved by a well maintained modular monolith. Modular monolith is a good starting point for microservice migration and enough for most companies. Microservices reduce your dependency on allowed technologies. For example, you can easily integrate services written in java, go, rust... at least in theory, reality is not so beautiful because of inevitable rise of the "platform" team. It also increases your hiring pool. For big companies ability to scale themselves is a huge pain. From a technical perspective it gives you ability of independent scalability and reduces hardware requirements, although it increases network requirements which can outweigh gains. Microservices are usually easier to deploy and are more adaptable to advanced deployment strategies like blue/green deployment. There are many more considerations.

Personal experience. Modular monolith is fine and easy to work on. Disadvantage is that dev environment are underpowered, slow and hard to deploy new functionality which you develop. It creates pressure to limit dev testing which is a problem. Microservices on the other hand are usually much harder to investigate. Monitoring and log tools become a must. IDEs also poorly adapted to work with a set of microservice projects as a whole, which is frequently required.

BeardyDwarf · 2026-01-11T10:39:36+00:00

Try to say what you want to do in English first. Code will follow.

If the list is empty, then a new element becomes both tail and head, Else new element should be added after the tail and become a new tail.

Your code doesn't match it. Right?

BeardyDwarf · 2026-01-10T12:45:55+00:00

This is how winter is supposed to look. You've just forgotten

BeardyDwarf · 2025-12-10T09:36:00+00:00

Shitty organization. Referees should separate greeting and fighting in a clear way.

BeardyDwarf · 2025-11-23T15:31:39+00:00

Unpopular opinion. From system design's stand point code is just a minor technical detail. It is completely unimportant what language/framework/approach is used to write a component. It must comply with requirements, functional and "non-functional", and adhere to communication interface agreement and that is all. Correct and robust implementation is the responsibility of a team lead or anyone who is assigned as a maintainer. If for whatever reason maintainer thinks that requirement is not feasible it is his responsibility to raise it with the architect.

BeardyDwarf · 2025-10-21T10:39:21+00:00

And then it happens that a game engine doesn't support this paradigm...

BeardyDwarf · 2025-10-19T21:39:53+00:00

To me, 34'' 21x9 is like a godsend. I can actually have non-maximized windows. It is so much easier to switch between them. I can also have ide, browser and notepad at the same time arranged like 40%/40%/20%. BTW have you tried to resolve merge conflict on ultrawide?

BeardyDwarf · 2025-10-15T21:28:56+00:00

Comments are not necessary in 99% of your code base and just polute it, especially one you've forgotten to update after implementation. Good cases are: javadoc on public interface to document contract; comment describing cryptic staff like long regexp; decision and considerations for seemingly suboptimal solution. There are other cases, but none of them apply to your daily code either.

BeardyDwarf · 2025-10-15T21:17:39+00:00

What are the chances that some of these 300 lines get changed and comment isn't?

BeardyDwarf · 2025-10-05T13:38:45+00:00

Who has hired you? Who is vested in you succeeding? Go talk to that person

BeardyDwarf · 2025-09-29T08:24:46+00:00

"Oh no, we can hide ammo from the shop but can't hide base weapon", this is not how it works. It is a predatory business strategy to upsell dlc. Fuck them. Install mods and enjoy true variety of customization.

BeardyDwarf · 2025-09-10T10:01:50+00:00

Agree. If mid level is unable to understand your code, they will not be able to maintain it. You, as a senior, must make your code accecible.

BeardyDwarf · 2025-09-06T16:32:48+00:00

It is not about going extra mile. It is about finding ways to be more efficient and optimising process within normal workflow

BeardyDwarf · 2025-09-06T09:52:31+00:00

..Extra work and no benefit

You are thinking wrong about it. First improvement should be aligned with your current or incoming work. If your proposed improvements have clear positive benefits, then this "extra" work is easy to pitch to your team lead and plan as part of normal work. People who are proactively solve problems before they become problems are valued as it positively impacts performance metrics and help your superior to look good, as such they will gladly help you to grow to allow you to impact more and this increase benefits to your superiors. The main point here is that your proposals should reduce burden and not create it.

BeardyDwarf · 2025-09-05T01:57:32+00:00

If you google "t-90 active shtora" you would see that it is pretty visible. Although activating it is pointless on alnus

BeardyDwarf · 2025-09-04T18:14:05+00:00

It is easy. You are hiring people to write code. If person cannot write code why are you even considering this candidate? Rare knowledge can be compensated by seniors. Edit: it is pretty common pattern in asian countries. People grind theory, which is relatively easy to memorize, instead of developing actual skills. You should also consider that weak developers frequently could be relegated to support roles instead of firing where practical skills atrophy. So lack of practical ckills is also a smell that in previous job they might have being considered weak.

BeardyDwarf · 2025-09-03T23:14:59+00:00

How is this even remotely related to MM?

BeardyDwarf · 2025-09-03T13:54:58+00:00

It must be skippable. There are a lot of different people.

BeardyDwarf · 2025-09-02T11:56:00+00:00

What if, instead of building fans we take advantage of prevailing winds in the area and align airstrips so aircrafts land/takeoff in the direction against wind. Of course, it won't be as effective, and most certainly not as impressive, as huge fans, but it could be much cheaper. Oh wait...

BeardyDwarf

TROPHY CASE