• 1 Post
  • 14 Comments
Joined 1 year ago
cake
Cake day: July 7th, 2023

help-circle
  • Do you realise that we are years (decades?) away from viable open source hardware? You likely use a closed source processor with closed source chipset, GPU and closed source ram. And these are the building blocks, then you have the closed source integrations of these blocks

    Same applies to fitness watches. Garmin happens to be one of the best (if not the best) hardware for the purpose, with a decent (not great, just decent) software that is very closed source and very closed in interoperability.

    You may say to vote with the wallet… but where? Apple that is even more closed and restrictive? Huawei that deserves its own ethical discussion?

    I haven’t looked into Suunto and Polaris but I would be shocked if they were dramatically different since this is their business, selling api and integrations


  • I really don’t think their goal is consumers.

    Sure they want consumers to use generative AI so that they get quality feedback so they can improve the product. But that is not the goal.

    The goal is enterprises, the goal is replacing workers with AI.

    There are estimations that around 300B$ have spent so far for generative AI. This is not for a gadget that close to no-one likes and burns money rather than make money

    This is for removing humans from the productive cycle. It is such an ambitious goal that the various CEOs/shareholders are ok taking such an high risk gamble.

    Trump will ditch any red tape to AI because Trump openly wants this world, a world where there isn’t any more the need for immigrants or workers or unions.

    My ingenuity suggests me that this plan will fail on technical grounds but if it will not, it will be worse. There will be poverty and civil unrest, there will be instability and wars (it’s always easier to look for the enemy outside rather than inside) and, in the end, economy will not do great either (who will buy the crap people will produce?)

    Again, I think that this plan will fail on technological grounds but removing red tapes will not accelerate this failure


  • Confidentially incorrect: at Google there is no clock in and no clock out (for employees, contractors is different). At Google you can work 1h per day or 20h per day you earn the same. Performances are assessed on the output not on the hour worked.

    So, no, find another reason for which Google is right. Popular topic is “they disrupt other people work by making noise” (of course people can work on a laptop in another place because there is generally no special equipment at the desk but details) or “they destroyed properties… you cannot see in the picture but they destroyed millions of precious bacteria on the floor”









  • This! The point of automation is rarely saving time. The point of automation is increasing quality.

    It can be a data quality, it can be mitigating a production risk, can be avoiding regression.

    Heck even unit tests are automation (you may just manually test your code once and call the day).

    I am not saying that automation is always good, but the evaluation should be

    1. what is the cost of production/data quality/regression gone wild? (Possibly in€/$/¥)
    2. what is the cost of the person/team performing the task over 1 Year (Again, £€$¥)
    3. what is the expected cost of the person/team implementing automation?

    Then you do (3)*3 - (1) *3 - (2). Is it positive? You do, is it negative you? You don’t. The more it’s positive the higher the priority of doing.

    Why the *3? The first because the expected cost of automation is always massively underestimated The second because it takes multiple times something goes wrong till the decision is reconsidered 🙂

    Why 1 year? Because generally the task to automatize changes or disappear