iOS Swift developer with an unhealthy amount of Android and Flutter thrown in. Cycling enthusiast. Admirer of TTRPGs, sometimes a player, often times a GM.

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

help-circle




  • samus7070@programming.devtoTechnology@lemmy.worldWhat DID Apple innovate?
    link
    fedilink
    English
    arrow-up
    18
    arrow-down
    2
    ·
    7 months ago

    The facts are that large companies rarely innovate anything major. They tend to buy up smaller companies that have taken the risk and succeeded. Look at Google and Microsoft and tons of others. It’s a problem with growing big. The forces that make a company a successful scrappy little startup die out in the name of organizational efficiency. If you want to know what Apple innovated you have to look at what they did in the 70s or extend your criteria to companies they have bought.



  • I enjoyed it. The only thing I would say is that there wasn’t a lot of tension or risk of loss in the series. It was more a low key telling of a period in someone’s fictional life. It kind of left me wondering if the last episode coincides with the last chapters of the book or if the season only covers part of the book like what was done with Silo.





  • Agreed on the M1. Anything entry level for Apple is decent but not really meant to push the envelope very far. I had a 16GB Mac mini and it served me very well for software development. I had to run multiple ram hogging tools at the same time so it did have pauses when switching between them. Other than that it was a beast. It held up well compared to my higher end MacBook Pro i9 with 32 GB Ram. The M1s run very cool. You’ll wonder if your machine even has a fan except if you’re doing a long intensive processing job. The M2s from my experience run hotter. I have an M2 iPad that I’m betting becomes thermally throttled just by watching Netflix. Not that it stutters, it just becomes warm to the touch.


  • Keep in mind these things don’t really know anything. They’re good at saying things that seem to fit the situation because that’s how they’re trained. They are like that person you may know that thinks he knows everything and will just say stuff that sounds right to them. The only difference is the ai is a lot more practiced than the human. Google’s llm may have some filtering done on the output to at least make sure that all of the books it recommends are real though it wouldn’t surprise me if there’s a fake one in the list somewhere. These things are prone to “hallucinations” which some lawyers found out the hard way.


  • There is a school of thought that break and continue are just goto in disguise. It helps that these two are more limited in scope than goto and can be considered less evil. If you read the book Clean Code by Robert Martin (it should be required reading for all developers), you’ll see that he doesn’t like functions to be very long. I think his rule is no more than 4 lines. I try to keep mine around 10 or less with a hard stop at 20 unless it can’t be avoided because I’m switching over a large enum or something. If you put your loops into functions then you can just use return instead of break.

    I did have a discussion with a teacher once about my use of early returns. This was when I had returned to school after many years as a professional programmer. I pointed out that my code has far less indentation than theirs and was simpler because of it and that it is common in the world outside of education. I got all of my points back he has deducted.

    You’re going to hear some good and bad advice from your teachers. Once you have a job check out what the good developers are doing and just follow them.