1,577 karma · joined October 7, 2011
1. There may be a community of your type of immigrants so you might not need English and within the community there are trusted people who can translate, so you don't actually NEED to learn the language yourself. This is why immersion language programs work well since you're forced to learn a language. Otherwise it's much harder, even if you're motivated.
2. When they moved they likely were not given the tools to help them learn. And even if they were given some of these tools, were the immigrants able to balance work with these classes. California does this well, they have a lot of free ESL classes, which are well taught and agencies/non-profits push immigrants to attend them.
3. Learning a new language is HARD, especially when you're older. Especially if it's not similar to your existing language (learning Spanish, French, German is relatively easy for English speakers since there are many words that sound the same. Learning Russian or Mandarin or Arabic is much harder since the language aren't part of the same family).
Integrating large groups into an existing community requires a lot of intentional work, no matter if that's immigrants integrating into a country or a company meeting with another. If that intentional work isn't done, you end up with silos.
We have to make a lot of changes across virtually the entire economy including equipment/factories etc that have lifespans in 30, 50,100 years. There are major questions about how fast we can accelerate the timelines as we basically reinvent ourselves
Admittedly there are some macro effects that are causing security to be taken more seriously by companies in general. The proliferation of compliance programs especially SOC2 had made basic security the default for a large portion of b2b tech companies. Cyber insurance requirements are increasing. Newer state regulations and SEC regulations have pushed other companies to increase resources dedicated to security.
That said this is an uphill battle after a decade or so of companies having no security with passwords or SSNs in plaintext and everyone having access permissions.
``` The company currently guarantees eight years of automatic updates to Chromebooks. That period, however, begins at the time when the company certifies a Chromebook, not when it’s actually in the owner’s hands. Because of the time it takes schools and businesses to purchase, receive, set up, and deploy new fleets of computers, they commonly end up getting four to five years of use out of them in practice. ```
so this is really about ensuring that the laptops actually get 5 years of use before needing to be replaced.
Code review: For a senior dev, I would expect tests even if I didn't ask for them explicitly. I'm also surprised to see that the functions are in a generic utils instead of better named files.
The reality: 1. other people are spending more time on these takehomes. 2. Being more senior means that there are higher expectations. 3. The takehomes are typically a qualitative assessment
Roadblocks: - Some backend providers still don't support opentelemetry format. Notably the number that do support it have increased dramatically over the past year. For those who don't natively support opentelemetry, you'll likely want to use the opentelemetry collector to translate to the format of choice - There's a fair amount of difference in maturity level depending on the language you're using. For example, python's opentelemetry ecosystem is very mature whereas rust's ecosystem was lagging behind. - Tracing is probably the strongest aspect. While metrics and logs are supported, they're definitely lag behind in terms of the TLC they're given
Tidbits of note: - Opentelemetry collector has rapidly become the go-to agent of choice. It has leapfrogged vector.dev in terms of features, and I'm seeing some enterprises choose to use it as their customer-facing agent (ie GCP's agents are clearly opentelemetry + plus some extras) - As more companies support opentelemetry as a format, there's less of a need for opentelemtry's format translation feature.
This is now mirrored since Grapl shut down (RIP)
For most non healthcare first SAAS providers you either do a major rebuild or you end up with a healthcare specific cluster which is missing some of your tools (although it's worth pointing out that many more vendors particularly in the observability space are now HIPAA compliant.)