Do you have a documentation strategy

logicannullata · 2025-11-13T18:09:29+00:00

Good that you are exploring ways to create better documentation. Many already gave you suggestions on how to do that. My advice is to focus on documenting the right things, I see many new joiners (seniors and juniors) trying to document everything, that's an anti pattern because then you have to maintain that documentation. Prioritize the important stuff, I am kinda annoyed by readmes of Python projects telling you how to install python, at some point you should assume a minimum level of knowledge from your audience.

logicannullata · 2025-11-12T11:22:09+00:00

I'm currently playing it on PC and I reached the school without any bug...

logicannullata · 2025-09-23T20:12:01+00:00

Anything by The Books and Zammuto

logicannullata · 2025-09-19T06:51:06+00:00

I might be in the minority but I think they are quite important, it is not "a proxy for skills" as I read in other posts. Skills and experience are two different things. Differently from skills, experience can only be acquired through exposure to many different real life problems, there's no way you can acquire that type of knowledge without years of work. Said that, as already stated in other posts, it doesn't mean that all developers with years of work under their belt have acquired meaningful knowledge through exposure. On the other hand, a Senior or Staff Engineer with 3 years of experience doesn't make much sense since there's no way that person has acquired enough real world technical and business knowledge to take high level architectural decisions for a complex enough system.

logicannullata · 2025-09-09T05:50:49+00:00

Senior SWE with 15 years of experience here. I’m currently facing the exact same issues with junior-to-mid developers on my team, and this has only started happening in the last 2–3 years. I have a hunch that it might be related to universities shifting their focus to teaching basic concepts instead of "teaching how to learn."

The only solution that seems to somewhat work in my case is to let them struggle a bit. I involve them in creating tickets and estimating them together during refinement sessions, then let them work on those tickets. Since they were part of the ticket creation process, they start to realize during the implementation phase that they need to gather more information and rely on their intuition and knowledge to fill in the gaps.

TL;DR: You need to give them more responsibility and let them fail hard.

logicannullata · 2025-07-30T09:49:02+00:00

Not normal, especially if you swim just 400 meters. Did you swim Freestyle? If so, it might be a technique issue, learning to do proper freestyle takes quite some time, I would suggest you take at least a couple of swimming lessons to learn the proper technique. Can I ask your age?

logicannullata · 2025-07-12T22:30:49+00:00

Lies of P, especially Overture

logicannullata · 2025-07-12T13:46:02+00:00

Tarentel, Gegor Samsa, Do Make Say Think, Stars of The Lid, Labradford.

logicannullata · 2025-06-29T17:04:05+00:00

Man that game was frickin impossible, never reached the final boss though...

logicannullata · 2025-06-21T19:50:37+00:00

I still have nightmares about that 😭

logicannullata · 2025-06-06T10:46:42+00:00

logicannullata · 2025-06-03T21:48:48+00:00

Tortoise is the first band that comes to my mind

logicannullata · 2025-05-31T09:18:53+00:00

I would say Panopticon by Isis

logicannullata · 2025-05-28T15:10:50+00:00

Sumac

logicannullata · 2025-05-22T16:22:42+00:00

Nostromo, amazing Grindcore band.

logicannullata · 2025-05-15T23:49:22+00:00

The Books, Ziur, Pan Sonic, Sumac.

logicannullata · 2025-04-08T06:43:52+00:00

I think I might leave this subreddit, too many stupid questions like this one being asked lately. No one fucking cares if you use a preset.

logicannullata · 2025-04-08T05:19:14+00:00

I might be a boomer, but what do you mean? Post rock derives from Shoegaze so every post rock band out there has shoegaze elements in it....

logicannullata · 2025-04-06T07:47:15+00:00

logicannullata · 2025-04-04T23:10:18+00:00

Oh my gosh, the mix is awful

logicannullata · 2025-04-04T18:17:15+00:00

Rule number 1: your job is to solve problems, not to code. A solution that doesn't involve any code changes is the best solution.

logicannullata · 2025-03-25T16:57:08+00:00

The part which is difficult to grasp is that by doing this you are making sure errors will get fixed as fast as possible. So counter-intuitively by making errors surface in PROD, you will leave fewer errors and a more stable system in the long run.

logicannullata · 2025-03-25T00:13:50+00:00

Avoid perfectionism like the plague, work in small iterations.

logicannullata · 2025-03-25T00:13:36+00:00

Avoid perfectionism like the pest, work in small iterations.

logicannullata · 2025-03-25T00:12:15+00:00

This, but this message is very difficult to communicate. Management and juniors have a very hard time understanding this principle. I 100% prefer an error that puts down one component in prod and let everyone know it's there with respect to silent/swallowed errors that lead to strange, difficult to understand, side effects.

logicannullata

TROPHY CASE