"Pacific time" is going to be so confusing though. Should have just called it Yukon Standard Time, since that's already a thing, at least informally. Cause that would not be confusing at all...
Yes, it's going to cause a lot of confusion and missed meetings. At the moment everyone says "pacific time", but now that will mean two different things.
I think we'll need to say Vancouver time or California time.
In my professional experience, having needed to work with relatively unsophisticated people across many time zones, the only thing that worked consistently was "[City] time". That way people could always check 'what time is it in X now' or 'when it's X in [City], what time is it here', and get correct responses.
Descriptors like "Mountain time" are too vague, especially when there are various places that do/do not practice DST within that timezone, or there are similarly named time zones internationally. (Australia has Eastern and Central time too, for example, and in summer - which is northern hemisphere winter - they split into four different time zones due to varying DST practices.)
Trying to be overly clever and exactly specify the time zone, e.g. "MDT", leads to lots of subtle mistakes in my experience. Often people will think they know what that is, and then get it wrong. Or their calendar app will helpfully suggest MST and they'll click on it, not noticing the difference. Or they'll just scramble the letters when writing them down and wind up with "NTT time" or "AT&T time" or some such.
EST is Eastern Standard Time. Most of Europe is on CET or CEST depending on time of year. (Somewhat confusingly, the 'S' in that case refers to Summer rather than Standard!)
Mountain time is ambiguous due to Arizona, and yet we still use that phrase. Hawaii-Aleutian time is also ambiguous: the Aleutian islands do daylight savings, but Hawaii doesn't.
Casual speech doesn't use the city names (like America/Los_Angeles for pacific time); presumably we'd have Pacific time (America/Los_Angeles) and BC time (an update of the existing America/Vancouver). If Washington's time change ever gets approved it would presumably become simply Washington time (America/Seattle maybe?).
It’s already ambiguous. Just use a city and let your calendar do the rest. New York, Phoenix and San Francisco time are unambiguous in a way trying to name time zones is not.
Location: Kelowna area, BC, Canada
Remote: Yep
Willing to relocate: Nope
Technologies: Linux, Kubernetes, Helm, Docker, Terraform, SaltStack, PostgreSQL, Redis, MongoDB, Nginx, Python, Django, apt packaging, iptables, VPNs, TCP congestion control algorithms (more than I ever wanted to know)
Résumé/CV: https://www.linkedin.com/in/foxmatthew/
Email: matt@tansen.ca
I seek contract platform engineering projects. I can help early stage startups set up infrastructure and CICD so founders can focus on PMF. And I can help established software companies with outdated infrastructure adopt modern tools and practices.
I have 15 years of experience in startup software development and DevOps across web apps, cloud, and Linux networking. 10 years of leadership in teams of up to 7 people. I have built infrastructure using Google Cloud, Microsoft Azure, Digital Ocean, and Linode.
Here are a sample of my accomplishments:
* Built a platform for hosting web apps using Kubernetes at a major cloud provider and taught engineers to operate and improve it. Introduced Terraform, Helm, and incident management processes. It operates in 4 regions and has about 250 total CPUs.
* Led a B2B SaaS company through their first SOC 2 Type II audit.
* Created an application CI/CD pipeline using Jenkins and Gitlab, resulting in a DORA performance score of 8.0 (above average in all scores according to dora.dev)
* Published and maintained the community Apt package for Helm, the Kubernetes package manager, which is downloaded more than 200,000 times per month.
It wasn't for no reason at all though. There were concerns about availability of yeast, which isn't used in sourdough. (Valid concerns or not, I have no idea.)
Yesterday my manager sent LLM-generated code that did a thing. Of course I didn't read it, I only read Claude's summary of it. Then I died a little inside.
It was especially unfortunate because to do its thing, the code required a third party's own personal user credentials including MFA, which is a complete non-starter in server-side code, but apparently the manager's LLM wasn't aware enough to know that.
Agreed- just a month ago I told my team to read https://www.joelonsoftware.com/2006/06/16/my-first-billg-rev... and note how Spolsky knew the details of his application (weird date issues in Excel and VB). If you want to be a senior engineer, you need to know where are the odd edge cases in your app. I don't want to be the only one on the team who remembers that stuff.
I installed CodeRabbit for our reviews in GitLab and am pretty happy with the results, especially considering the low price ($15/user/mo I think).
It regularly finds problems, including subtle but important problems that human reviewers struggle to find. And it can make pretty good suggestions for fixes.
It also regularly complains about things that are possible in theory but impossible in practice, so we've gotten used to just resolving those comments without any action. Maybe if we used types more effectively it would do that less.
We pay a lot more attention to what CodeRabbit says than what DeepSource said when use used it.
I was driving home with my family from a long trip having just bought a really cool camping trailer, a 1979 Airstream. Our vehicle died on the side of the road in a rural area. The owner of the property where we stopped was mowing his lawn and came over and asked if we needed help. When it became obvious our vehicle needed a tow, he used his own truck to bring the trailer onto his property. And he kept it there for a couple of weeks while the engine in our vehicle was replaced.
I'm really not sure what I would have done with the trailer if he hadn't offered to help. We were more than 600 km from home.
I do a check for `request.htmx` in my views and conditionally return a template partial as needed. This reduced my need for one-off view functions that were only returning partials for htmx. Works pretty well from my experience.
I distinctly recall early in my first university programming courses the instructor saying something to the effect of "Just wait until you learn 'public static void main'". I think we had only used BlueJ until that point in the course.
