• 0 Posts
  • 103 Comments
Joined 1 year ago
cake
Cake day: June 14th, 2023

help-circle
  • Imo, the term “buy” for all goods should pass some sort of litmus test. Eg:

    does the product being sold have the same properties as a brick?

    • can the product be resold privately?
    • can the product be lent to another user temporarily?
    • would the product still perform its function when the manufacturer stops supporting it?
    • would the product still perform its function if the manufacturer ceased to exist.

    if the product does not pass all these tests, the customer is not buying. Consider using terms such as ‘rent’ or ‘lease’ or ‘subscription’






  • The problem occurs when house prices tumble from an influx of sales, and the 32% (In NZ) of your population that are paying their mortgage off on their primary residence are potentially plunged into negative equity on rising interest rates.

    Once you’re there, you’re kind of fucked. You can sell, but you’ll still owe the bank money, so you can’t buy/downsize. You can’t even change banks. You’re a risky customer, so you get higher interest rates. All you can do is hope the market rebounds or declare bankruptcy.

    So you’re risking fucking over 30% of your nation (and arguably the most productive segment of your country as they’re earning money to pay that mortgage), to appease a fraction of (as not every renter can/wants to buy. Eg, students, temporary immigrant workers etc) the 30% of renters that are being fucked over by high house prices.

    Not to mention, all the renters you’ve displaced into an even more competitive rental market.

    But that’s not to say the solution is to shrug your shoulders and let the landlord class continue to punch down.

    It would be expensive, but you could guarantee (current) mortgages for primary residences in cases of financial hardship. Buy mortgagees out and turn the houses into state housing, renting them back to the previous owners at fair prices.





  • I used to love ‘the cloud’. Rather, a specific slice of it.

    I worked almost exclusively on AppEngine, it was simple. You uploaded a zip of your code to appengine and it ran it at near infinite scale. They gave you a queue, a database, a volatile cache, and some other gizmos. It was so simple you’d struggle to fuck it up really.

    It was easy, it was simple, and it worked for my clients who had 10 DAU, and my clients who had 5 million DAU. Costs scaled nearly linearly, and for my hobby projects that had 0 DAU, the costs were comparable.

    Then something happened and it slowly became complicated. The rest of the GCP cloud crept in and after spending a term with a client who didn’t use “the cloud” I came back to it and had to relearn nearly everything.

    Pretty much all of the companies I’ve worked for could be run on early AppEngine. Nobody has needed anything more than it, and I’m confident the only reason they had more was because tech is like water. You need to put it in a bucket or it goes everywhere.

    Give me my AppEngine back. It allowed me to focus on my (or my clients) problems. Not the ones that come with the platform.





  • Could a hypothetical attacker not just get you to visit a webpage, or an image embedded in another, or even a speculatively loaded URL by your browser. Then from the v6 address of the connection, directly attack that address hoping for a misconfiguration of your router (which is probable, as most of them are in the dumbest ways)

    Vs v4, where the attacker just sees either your routers IP address (and then has to hope the router has a vulnerability or a port forward) or increasingly gets the IP address of the CGNAT block which might have another 1000 routers behind it.

    Unless you’re aggressively rotating through your v6 address space, you’ve now given advertisers and data brokers a pretty accurate unique identifier of you. A much more prevalent “attack” vector.




  • If you still do the sizing (it’s not entirely wasted as it’s a reasonably effective tool to gauge understanding across the team), This can still be done without the artificial time boxing.

    “How much work have we done in the last two weeks?” Just look at all the stories closed in the last two weeks. Easy.

    “When will X be delivered?” Look at X and all its dependencies, add up all the points, and guesstimate the time equivalence.

    Kanban isn’t a free for all, you still need structure and some planning. But you take most of that away from the do-ers and let them do what they do best… do.