• 1 Post
  • 23 Comments
Joined 1 year ago
cake
Cake day: June 19th, 2023

help-circle

  • Wonder what the engineering solution to this could look like…

    Thinking something like a zero trust model being required for all web requests… Like the target address would need to receive a validated identity token from some third party but that token couldn’t contain identifying info about the requester. Likewise, the validating third party would need to verify the identity of the requester without having knowledge of the target address.

    Then that raises more questions like who would we all be comfortable trusting as a verifier and what data would we use for that validation? The validation system and the data used to validate would need to be provided for free too to account for low income people so no subscription services or hardware MFA keys. Also who counts as an identity to be validated?

    What do enforcement mechanisms look like if this does get built? Are the validators entirely passive or do they actively participate in the process? Like do we have rate limits imposed by the validation engine or do we just leave that to the target address/organization to impose themselves? What happens if someone is banned from a site? Does the site notify the validators to drop requests earlier in the lifetime of a request? Do individuals get a lower request quota than corporations? Would you have to form a company just to prototype a new tool/product?

    If someone seriously wanted to work on this I’d jump on the opportunity to work with them. It sounds like a fascinating project.


  • It’s a big, stupid truck but so is every other truck it’s competing against. It’s got poor visibility but so does every other truck/suv being sold in America. The cheapest option doesn’t have the longest range but it’s still longer than the average person would realistically drive in a day. It can’t haul much but the overwhelming majority of people driving trucks in America aren’t towing or hauling things on a day to day basis… The people doing real work buy vans or have special purpose trucks.

    The steering geometry seems nice and the rear wheel steering is interesting. Those seem like the only major positives though.

    It’s not as bad as everyone seems to be making it out to be but it’s obviously still a dumb car that shouldn’t exist. That’s all cars though really.

    EDIT: Since the front windshield is flat, I assume its cheaper to replace than typical curved windshields? No idea though… Might be talking out of my ass.




  • Certs are a waste of time tbh. If you have 8 years of experience, you should have more than enough to fill out a resume already.

    An AWS cert is almost certainly even more useless for you specifically unless you wanted to get into devops/sre and do systems design. I have been in sre for a very long time and have never even heard of anyone writing tooling in Java. That section of the industry is entirely dominated by go, python, and (more often than anything else) bash for really quick automation.



  • I’m living in Tbilisi, Georgia. There are TONS of older foreign cars here with damage that would clearly fail an inspection in places like America… Lots and lots of cars driving around with crumple zones that have been destroyed but the engine works fine. Apparently it’s cheaper to import one of these than it is to buy a car here.

    It’s not just American and European cat’s either. There are significant numbers of Japanese imports as well which have the steering wheel on the wrong side. Sometimes you’ll get picked up in a taxi and the whole radio/infotainment screen is all Japanese.


  • As a counter balance to that though, interviewers need to understand what they are hiring for and tailor the questions asked to those requirements.

    For example, there is genuinely very little coding required of an SRE these days but EVERY job interview wants you to do some leetcode style algorithm design… Since containers took over, the times I have used anything beyond relatively unremarkable bash scripts is exceptionally small. It’s extremely unlikely that I will be responsible for a task that is so dependent on performance that I need to design a perfect O(1) algorithm. On terraform though, I’m a fucking surgeon.

    SRE specifically should HEAVILY focus on system design and almost all other things should have much much less priority… I’ve failed plenty of skill assessments just because of the code though.






  • Most resistance I have seen mostly comes down to a misunderstanding in the benefits that kubernetes offers. The assumption is that kube is used for autoscaling and that, if the inbound traffic is predictable then the added complexity is unnecessary. When that happens the “kube isn’t right for all situations” turns into “kube isn’t right for any situation” whether the person in question would ever admit that or not…

    All of this ignores the MASSIVE reliability enhancement kube delivers and the huge amount of effort currently going into modern tool development surrounding the kube ecosystem.


  • Real talk, you don’t have the luxury of being an idealist right out of university. Your goal is to get a job. When you’re in that job you will likely not have the luxury of being an idealist either.

    When you have enough experience making practical, reasoned decisions, then you can stand on principals.

    For context, I have been in this business for nearly 20 years. The people I have personally worked with who have resisted things on philosophical grounds ALWAYS get left behind. I’ve seen it with systemd, the cloud, and now I’m seeing it again with kubernetes. You cannot escape the collective inertia of an entire industry.

    Obviously there are still thresholds… I would never work for someone like Raytheon. You have to draw lines somewhere but saying you aren’t going to work for a company that does user behavior tracking is short sighted and impractical.