Location: Ontario, Canada
Remote: Yes
Willing to relocate: No
Technologies: Go, Python, Java, AWS, GCP, K8s, SQL, etc.
Résumé/CV: https://docs.google.com/document/d/1hFPH4PgodS_mIZ3lxERSU0hFbJX9KrvNd87jcPxwTiA/edit?usp=sharing
Email: josh@hayes-sheen.ca
Staff+ Engineer with a backend and distributed systems focus. I love to build teams, orgs, and products with care. Have dabbled in a little bit of everything from microcontrollers to huge cross-cloud applications. I lean a little towards devops and though I haven't ever been an SRE/DevOps specialist, leaning that way has been a superpower for building products and platform tools.
Location: Ontario, Canada
Remote: Yes
Willing to relocate: No
Technologies: Go, Python, Java, AWS, GCP, K8s, SQL, etc.
Résumé/CV: https://docs.google.com/document/d/1hFPH4PgodS_mIZ3lxERSU0hFbJX9KrvNd87jcPxwTiA/edit?usp=sharing
Email: josh@hayes-sheen.ca
Staff+ Engineer with a backend and distributed systems focus. I love to build teams, orgs, and products with care. Have dabbled in a little bit of everything from microcontrollers to huge cross-cloud applications. I lean a little towards devops and though I haven't ever been an SRE/DevOps specialist, leaning that way has been a superpower for building products and platform tools.
I have the opposite frustration here, where I queue up some music videos on my TV and inevitably after 1-2 songs, I'm staring at static album covers when I know there's an awesome music video that should be playing instead
You should look into multistage docker builds, that lets you still use a full fat image for your build but then leave all the build tools out of your final image
Someone else suggested the same thing actually. Easy to get lazy when it "just works" and internet is 1gig home and office - you can see how bloat just builds up.
I wouldn't mind changing it to use a js renderer, currently it's using the (deprecated!) Google image api but I hadn't really found anything as complete/safe/reliable to replace it
A while ago it was suggested to me to mentally translate "accident" to "collision" in context of cars hitting cyclists. Most collisions with cyclists are easily avoidable, and caused by negligence, impatience or ignorance.
Treating collisions as unavoidable, unintentional mistakes relieves drivers of a lot of the inherent responsibility of controlling a vehicle. Watch the road. Respect other users of the road. Be patient, safe, and focused.
Correct, a "North American" account would not be able to message or otherwise interact with a "Oceania" account (the region which contains Australia). That being said, an Australian could register an NA account, but shouldn't expect bearable ping/latency.
I've wanted something like this for years! A great real world example of a data structure that really made an impression on me during my computer science education, connecting theory to implementation
I think Google has shown they're trying very hard to become a primary infrastructure host for any business in "The Cloud", getting more people online opens up new opportunities there too