Born a sconie right on Lake Michigan, lived in Iowa for a handleful of years for college, then moved to Sota where I live currently. Software Engineer for 20+ years, Ham Radio Operator, lover of retro graming, old time radio and the outdoors.

Mastodon: jecxjo@mastodon.sdf.org

  • 0 Posts
  • 29 Comments
Joined 2 years ago
cake
Cake day: September 9th, 2022

help-circle



  • Back then i only had a few games but among all my friends we had a pretty good collection. As an adult playing on a retro console I’ve started to go through a lot of the games i never tried or didn’t own and only played a few times.

    While I’d say the total NES library is a majority of garbage games (publishers just figuring out how to make games, not how to make good games) I think the big thing i noticed is that the good 8bit games look and feel drastically different than the garbage ones. When you learn the history of the games then it makes sense.

    The quality of the sprites, the extensive design of menus, transitions and other interactions, the storyline and dialogue. Even with only 8bits and crappy resolution the output for many of the good games actually looked and played well back then and even now. But I’d say about 90% of the NES catalog was garbage back then and still is now.


  • I think the difference is that in the 8bit generation yhe majority of the game were bad relative to each other. The peak of the bell curve for 8bit was between mediocre to kinda bad games.

    While there are more games in later generations, it feels like the console manufacturers took more control and regulated what was published. Bad games happen now because of shitty business decisions and bad story writing. You dont see garbage being published just because you can.



  • All of my gaming is super retro or low tech. I do have an XBoxOne but i rarely use it. Computer is old so games on there are mostly old old stuff from the 90s and early 2000s.

    Hardware wise i have an Anbernic 353V that I do a lot of retro gaming. Not a huge fan of the Gameboy style setup but its a good cheap machine.

    My kids have Switches and thats what kicked me from supporting Nintendo after they go obsolete. The Joycons on one suck and I’ve replaced the connector hardware twice now. The best version is the Lite but you cant connect it to a TV which is dumb. Their family sharing is broken (wife has digital game, i havs DLC, we are SOL).




  • I don’t think it matters what tools you use as long as it works.

    That would be true if other systems and services depend on them. Would have been nice to come out with a standard and designed systemd around that standard. Then you pick the tool you want that follows the standard rather than be tied into systemd.

    Worth noting is that a process not managed by pid 1 isn’t really a thing you want generally

    I would disagree. A compromised Docker doesn’t mean i have access to things managed by PID1. The entire control model is based around moving your publicly available services further away from something with the highest level of access. Be it users or processes.




  • You don’t have to actually do a real project. It’s more about doing a task that requires you to create outside the hand holding.

    After 15 years of OS and embedded systems development I learned web dev by creating a SaaS for my HOA’s property manager to communicate with tenants. Node, React, MongoDB, docker, iOS and Android apps. Did the project look good? Nope. Did I have to dig into manuals and debug for weeks, yep. But I easily stepped into a new role in an industry I had never worked in because I really learned the tech stack. Actually using the app wasn’t necessary, just that I actually had to create things requiring me to design around the technology I was learning.

    Pick a problem in your life and solve it. Doesn’t need to become something you sell or publish or even use after you’re done learning. But the point is to actually use your skills.


  • I’m saying that the work they would be doing in two days isn’t the same as solving an actual problem. The way to really learn a language/framework/library is to actually use it in a real project. You run into pitfalls, you get compile errors and have to figure out how to debug in said tech, you find out how extentions to the tech work so you can create your own. Making a Todo Front End isn’t going to cover the vast majority of the stuff I’d expect one to know or experience when you say you “know” a language/framework/library/etc.




  • jecxjo@midwest.socialtoProgrammer Humor@programming.dev“Hire me”
    link
    fedilink
    English
    arrow-up
    13
    arrow-down
    1
    ·
    1 year ago

    Because anyone worth their salt knows that the superficial hello world example covers the tip of the iceberg. So to say you learned it in two days means you either don’t get that you barely scratched the surface or you dont get what other developers really need when they hire someone with knowledge in a specific framework.