vrkr

@vrkr@programming.dev

• ⁨Comment⁩ on ⁨Merge then review⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  Something like that literally happened to me yesterday. I reviewed one PR, then some Important Guy came in and said:

  • it is nice you reviewed my work, but we need to push this to production right now.
  • just fix these things, I described you how. Just copy/paste these snippets
  • these are cosmetics, I don’t care
  • "cosmetics", huh?
  • gfy and push this to production right now
  • well, ok

  Of course, lack of these “cosmetics” caused crash in production.

• ⁨Comment⁩ on ⁨A lot of YAML⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  I like YAML.

• ⁨Comment⁩ on ⁨What is your favourite font for code ?⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  My own variant of Iosevka

• ⁨Comment⁩ on ⁨Day in the Life: Senior Dev Edition⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  I’m not proud of it at all, but in my case:

  • 06:45 - Sit down, log in to PC, be sure teams status is set to invisible, sip of coffee
  • 07:00 - Start doing useful stuff while it’s quiet
  • 09:00 - Set status to available
  • 13:00 - Try to remain sane and professional
  • 15:30 - Time to end this: leave “early”, because life reasons

  I’m getting tired of this.

• ⁨Comment⁩ on ⁨What is the best file format for configuration file?⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  No reason to go beyond simple key-value format like dotenv or just env variables. If you need more structure you may be confusing configuration with state and this is not really the same thing.

• ⁨Comment⁩ on ⁨become ungoogleable⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  In places like here, probably, where nerds share nerdy stuff.