What a twist

What if you only have a nail?

Sounds like you need to add some sleep statements somewhere in your deployment scripts if you want to deploy in 10 seconds

Users are the acceptance testers.

No worries, sounds like you’re definitely on the right track with your approach.

In terms of the style of editor I don’t have a strong preference, I think the most important thing is discoverability which generally means putting docs where they are expected to be found and using whatever your team or org is using. Personally I have a slight preference for markdown mainly because it’s easy to version control, see who wrote what (so I can ask them questions) and use all the tools I’m used to that work well with plain text. Tools that use more WYSIWYG style can be good too though and many of them like Notion have the advantage of making it relatively easy to search across your entire companies documentation assuming everyone uses the one tool.

For my personal notes I use Logseq which I highly recommend. It’s a bit of both, markdown under the hood but with a simple editor that lets you focus on writing notes, tasks and links.

I would say as a new junior dev you are uniquely placed to help with this. Documentation tends to be written by people who know a lot about a thing and they try to imagine what might be useful for someone. Someone new coming in with a fresh perspective can help uncover assumed knowledge or missing leaps to make the documentation better. One of the common onboarding steps I’ve seen is to go back and update/improve the onboarding docs after you’ve just been onboarded for example.

I would say pick your battles though because documentation can be a never ending task and documents are almost always out of date shortly after they are written. Think about what would have saved you time or mental overhead if it was just written down and fix those first.

As far as organising and writing, every place is different and it can depend on the tools your org is using. In general I’d at least have links to relevant docs as close to where they might be needed as possible. Like how to set up and get up and running with a code base should probably be documented directly in the readme, or at least linked to if it’s overly complicated.

Hopefully that’s at least somewhat helpful. It’s definitely a problem basically everywhere I have worked though, you have to do what you can and not stress too much about it.

One might even say it’s an ExtremelyDrawnOutMethodNamesFactoryImpl

Almost certainly

The great thing about schema-less databases is you can put any old thing in there. The bad thing is at some point you have to get it back out again.

Or just !! for the last command. Particularly helpful if you forgot to prefix it with sudo you can run sudo !!

I’ve been using Atuin on my work computer and found it to be pretty good if you want something a bit fancier than Ctrl + R

It was a joke on the dual meaning of “user repository” which I didn’t think about that deeply but that would have been smart.

And the Arch User Repository is really handy when you need some more users.

// This function calculates applicable discounts given a customer's loyalty status
// STOP BEFORE SEASON 8 DEXTER PLEASE 
fun calculateDiscountRate(loyalty: LoyaltyStatus): Set<Discount> {
    // No seriously you can hide out at my place if you need to just please don't let them do it 
...

Microsoft set themselves up the bomb

This looks pretty interesting! I haven’t used fedora before either so could be good to give it a go. I’ve had some issues with my Pop OS install so could be a good excuse to try something new.

It’s too late, we can’t contain it

I sense a great disturbance in the force, as if millions of wallets cried out in pain, and were suddenly emptied.

Outlook

Outlook (New)

Outlook (Newer)

Outlook (Newest)

Outlook (Newest final)

Outlook (Newest final V2)

I’m curious about why you think this. I’ve seen complex multi year efforts succeed and continue to evolve with agile principles in mind. What specific part of agile do you think would necessarily cause the issues you mentioned?