dimaaan

RTO - Return to Office

Don't call them rockstars - call them "resume-driven developers."

We had one on our team in the past.

A bunch of microservices built on an in-house RPC framework he wrote, RabbitMQ, half-baked "monads" in an OOP language, esoteric naming, and no comments (the code should be self-documenting!), no docs.

Management adored him.

Once we started to grow, the problems started to appear: bad orchestration, uninformative logs full of PII, poor error handling, edge cases that were nearly impossible to fix within the existing abstractions, dependency hell, etc.

At that point, he moved on.

It took years and many hundreds of pull requests to clean it up.

Don't forget NPM packages Mocha and Chai (Pee and Tea)

MIT license: https://github.com/dotnet/roslyn

No. See https://stackoverflow.com/questions/1732348/regex-match-open...

And "Search by picture"

Right, fixed such test today

And standard library design errors also.

Properly designed date/time API invented relatively recently.

System.DateTime (.NET) - 2002 | System.DateTimeOffset - 2005

Joda time (JVM) - 2005 | java.time - 2014

Temporal (JavaScript) - still experimental

Thank you for that kind of words.

It's so rare nowadays.

While i agree with technology, art (painters, literature), dance (ballet), i didn't think Russia brings much to the worlds of music.

Curious what is in you iTunes rotation?

And the greatest Russian rock singer was Korean.

https://en.wikipedia.org/wiki/Viktor_Tsoi

> No, https://twitter.com/ is probably not blocked in Russia

> No, https://www.instagram.com/ is probably not blocked in Russia

Seems like its not working at all.

Similar trick for JSON-based web API's that returns either error message or result

    async fetchApi<TResult = void>(request: Request): Promise<TResult> {
      type SuccessfulApiResponse = { Succeeded: true; Result: TResult }
      type FailedApiResponse = { Succeeded: false; Error: string | null | undefined }
      type ApiResponse = SuccessfulApiResponse | FailedApiResponse;
      const response = await fetch(request);
      ensureStatusOK(response);
      const result = await response.json() as ApiResponse
      if (!result.Succeeded) throw new Error(result.Error || 'Unknown API error');
      return result.Result
    }

Use System.Threading.Channels.

BoundedChannelFullMode.DropNewest, DropOldest, DropWrite, Wait specifies the behavior to use when writing to a bounded channel that is already full