• 42 Posts
  • 537 Comments
Joined 2 years ago
cake
Cake day: June 11th, 2023

help-circle













    • Make changes to existing projects
    • Create and use projects you have an interest or use in for yourself
    • Reading technical articles
    • Reading guidance docs (like Microsoft dotnet or SQL Server docs giving introduction to architecture, systems, approaches, behaviors, design decisions, etc)
    • Working with more experienced people - seeing them work, being instructed, reviewed, commented, guided by them
    • Experiencing alternative technologies and approaches
    • Experience in general
    • Exploring existing projects and their architectures

    I don’t know how far along you are in Python use. In general, I don’t think Python guides you into good practice or architecture. It’s too dynamic and varied of a language. You’ll need a framework to be guided. Personally, I have a dislike for it for multiple reasons. Others seem to like it. Other languages and ecosystems are more limited, in good ways. (Maybe I’m misinterpreting “todays” Python, I’ve only peeking experience with Python.)

    I would suggest trying out Go or/and then C#. Both are relatively simple to get into, and have more native/mainline frameworks and guidance. C#/Dotnet in general has a lot of guidance, documentation in broad and specific, and tutorials and sample projects.


  • I don’t think 2% of M365 is necessarily bad numbers. Office is prevalent, for all kinds of and even the simplest of office work. Not everyone needs AI or has the technical expertise or awareness of what this offer even means. Some people may not have launched their Office for one or two years but still have a paid license.

    There’s also a free copilot for GitHub users, which may be necessary as a teaser and testing, and adoption. That may also offset “adoption” by measure of commercial licenses instead of active users.

    I didn’t like the initial focus on that number of sold licenses in the article. Of course, they expand upon it and draw a broader picture afterwards.


  • I think it makes sense that publishers are required to update or at least assess games when open security issues come to their attention.

    The current state is that you may have 20 games installed and 10 have not been maintained for a long time, and 5 have open security issues that an attacker may use. For example, a game launcher with service installs to program files with admin permission. And suddenly, you have a privilege escalation.

    Or a game, when run, pulls in some monitoring, and suddenly exfiltrates data because that service is defunct and was taken over, or hacked.

    The necessity is quite clear.

    Maybe this will also push us towards more stable software, that changes less, or has less attack or escalation surface. That could significantly reduce maintenance burden - even if it ends up only assessing reported open vulnerabilities not affecting your product (because you don’t make use of or open up the vulnerable functionality).