• 1 Post
  • 16 Comments
Joined 1 year ago
cake
Cake day: July 5th, 2023

help-circle








  • Something isn’t right with this article. I’m suspect:

    • Type 1 is where your islet cells die off and you lose insulin production. Type 2 means your insulin production is fine, but your cells are resistant to the insulin. A Type 2 should have plenty of islet cells so adding more doesn’t seem like it would do anything. Your body should regulate those cells to output the same amount of insulin as before.

    • This same treatment has been done in Type 1s already. It’s not new. The problem is their body eventually kills off the transplanted cells and you have to do it again. Plus, you have to take immune suppressing drugs forever.

    • “Despite a kidney transplant, his pancreas still doesn’t produce insulin.” - This is just nonsense.


  • Waldowal@lemmy.worldtoProgramming@programming.dev...
    link
    fedilink
    arrow-up
    32
    arrow-down
    10
    ·
    7 months ago

    Fucking Microsoft, with their fully featured toolsets, libraries for everything, fantastic IDE, second fantastic IDE, and cloud infrastructure that actually delivers on the promise of cloud, and isn’t just “bare metal bullshit in the sky”. Hate those fucking pricks.




  • The idea of agile is great, and easy to sell at a company in my experience. The problem is that the ideas in the manifesto can only be attained if the business stakeholders feet are in the fire as much as IT. That HAS to have top down support from leaders that understand software. But, in every agile company I’ve ever seen (I was a consultant for 15 years, so I saw a bunch), eventually a project goes south, and the business stakeholders throw tech under the bus by saying: “We’re not in IT. We didn’t know we should be thinking about what we want (and not just waiting until the end to demand more and more and more)!”, and they fucking get away with it. Boomers in senior leadership, who don’t know how to work their car stereo, say “Yea, that makes sense. IT, why do you suck!?”. And then “agile” is dead. Tech learns to cover their ass, and demand clear requirements up front and get signoff.



  • It’s fallen out of popularity over the years, but reading programming books. The big ones. There is an expectation that a book will contain every bit of info about a technology, and you can learn it, in depth, in one place. Online articles, videos, etc., often just skim the surface. You don’t get that deep learning and facts that the books would have. I find even “Official documentation” online is sparse and often doesn’t include examples to gain understanding.

    Unfortunately, the pace of change, especially in cloud services, cause books to be out of date too quickly, so I don’t see it making a comeback.


  • I’d argue you’re right until you need to track down a bug in the code. Then, to the author’s point, you have to jump back and forth in the code to figure out all the interdependecies between the methods, and whether a method got overridden somewhere? What else calls this method that I might break by fixing the bug? (Keep in mind this example fits on one screen - which is not usually the case.)