wonkothesane

About

Username
wonkothesane
Joined
Visits
624
Last Active
Roles
member
Points
3,017
Badges
2
Posts
1,751

Reactions

1.5KLike2Dislike94Informative

  • Apple falls to 36th place on Glassdoor's annual Best Places to Work chart

    wonkothesanewonkothesane
    canukstorm said:
    sog35 said:
    they are working so hard?.... on which product... that has not been delayed or released with a problem.
    They are working hard making 103% of phone profits
    90% of tablet profits
    80% of PC profits

    Takes hard work to be the most valuable and profitable company on the planet
    Depends on whom you ask

    http://kensegall.com/2016/12/apple-earning-the-wrath-of-steve/
    Thanks for the link. Some part of me shouted "yes! Yes! Yes!" When I read it, as I can't help but feel the same. Maybe from a business perspective they put their focus right. However from a personal perspective from someone who always had lots of interconnected Apple stuff that just worked I'm not so convinced anymore. Let's hope for innovation on the mac line beyond touchbar. You hear me, seamless Apple routers, gorgeous displays, and yes, even printers? All those low margin products which made the difference between hideous and not reliable, compared to cool design and joy to use. :)

  • Apple releases updated iOS 9.3 to fix Activation Lock bug on older devices

    wonkothesanewonkothesane
    Upfront: I do realise that bugs are a reality and that they will be for a foreseeable future. 

    Now, stories like this one, or recently on the MacOS side related to wifi still do make me wonder to what extend any bigger software project is just a clusterf**k of code with basically no chance of catching everything and why is it like this? Last time I wrote somewhat serious code was when turbo pascal and c were fashion, so please bear with me here for a sec. 

    A mechanical system has basically all analogue interfaces through the components physical properties/dimensions, and therefore basically an infinite number of states to be theoretically checked. 

    in contrast, software is (usually) not "fuzzy" and comes with a finite state space. What makes it so hard to make bullet proof bug free software then? 
    Or, over decades, why has - let's call it - insufficiently tested code not been replaced over time and piece by piece with "100%" sound code? 

    Is it a question of effort versus quality and some pareto that would increase costs by a multifilament just to catch the last few bugs?

    Or, is there a a fundamental and proven law/theorem that any code by force contains what we consider as bugs?

    Maybe some of you professional software developers can provide some insight.