johnnyRose

This is neat! Commenting to see my own.

I was able to enter a room I created without allowing microphone access.

This is a lot of fun! Definitely makes me miss my favorite Irish pub (located in the Midwest).

Nit: I wish the traditional music cycled between a few different songs. What's provided is pretty repetitive, and is already stuck in my head.

I used this approach as part of a personal learning project. It ended up working very well because I was using Mongo, so I could just use $graphLookup with an index on the next ID.

It was definitely fast enough for my purposes, sorting about 30k items in 3 different linked lists in just a second or two. The function allows you to limit your depth or modify your starting location in the linked list (graph) which opens a lot of possibilities and/or performance improvements when only loading the first N records.

Hello! My team is currently creating microservices written in .NET Core. A lot of my teammates don't commit appsettings in their .NET Core microservices, opting instead to simply commit changes to our docker-compose file. This is fine until we need to debug something, and then it becomes painful to manually map the environment variables from the docker-compose file over to appsettings.development.json. I created this to make my life a little bit easier, and hopefully it helps some other folks too!

It's not perfect, and won't support every possible format for docker-compose environment variables (block scalars, for example), which seemed a little overkill for a weekend project.

I'm definitely open to feedback and suggestions! Thanks!

Nice tool, I'd love to try it. Is your sign-up broken? It just comes back with an empty red alert.

You're right - in my experience, most programmers have it pretty good.

What I've noticed is that stress/overworking comes when the team is pressured for time. As a mental, as opposed to physical laborer, sometimes less is more, and sometimes that means leaving an hour early just to figure out the solution to your problems on the drive home.

Managers who think "butts in seats, hands on keyboards" equals "more productivity" can't effectively manage programmers.

I'm curious how requirements are determined at these huge tech companies. Do the programmers have any weight as to which features are implemented, or are requirements typically handed down from someone else? I'm sure this varies from place to place but I'd like to hear your two cents.

The heat has to go somewhere. If your machine is feeling hot, the heat is escaping. Trying to prevent that by using a less conductive material may not end well for your laptop.

I have looked into this in the past and came to the same conclusion. Essentially, the "password" sent to the website is the client-side salted/hashed version of the user's actual password. The server could then salt/hash the "password" another time before storing it. This could result in the same issue if the "password" is logged, but it protects the user's true password from being discovered. Maybe a security expert can weight in on this, because I don't understand why this wouldn't be the standard.