Sometimes I make video games

Itch.io

  • 0 Posts
  • 29 Comments
Joined 1 year ago
cake
Cake day: July 26th, 2023

help-circle





  • You seem like somebody who might have an answer for me:

    A streaming service that I’m using lists the spoken language of the show, and I’ve often seen Spanish, Espanol, and Castilian listed. What’s the difference between Espanol and Castilian - is it like a regional dialect? Also I’m probably misinformed, but I always thought that Espanol was the English word for Spanish, which makes it seem odd that the service would list both Espanol and Spanish separately.

    * Walter, this isn’t a guy who wrote the Magna Carta, this is a guy…



  • I wasn’t aware my mediocrity was on display. 😅

    Honestly, I liked the professor. When he had time to teach something he was clearly interested in, he did a great job of connecting. He didn’t get to teach us OOP though because there was a staffing emergency. The person we did get normally taught Hardware, so he was basically just reading aloud the textbook. Poor guy.

    And you’re right, the professor did let us know that there was going to be a change of requirements partway through. But it wouldn’t be a good lesson if he told us what was going to change, although he did give some examples from previous times he’d taught the course.

    A lot of people got burned when the change came. For my part I thought I did pretty okay, the refactor didn’t go perfectly but it was better than if I hadn’t been prepared. But I’ve also written a bunch of really gross objects that served no purpose just because they might change later. As anything is, it’s all about finding that happy medium



  • Most of my college coursework was around OOP. That said, they actually did a pretty lousy job of explaining it in a practical sense, so since we were left to figure it out ourselves a lot of our assignments ended up looking like this.

    At the end of the program, our capstone project was to build a full stack app. They did a pretty good job simulating a real professional experience: we all worked together on requirements gathering and database design, then were expected to build our own app.

    To really drive home the real world experience, the professor would change the requirements partway through the project. Which is a total dick move, but actually a good lesson on its own.

    Anyway, this app was mostly about rendering a bunch of different views, and something subtly would change that ended up affecting all views. After the fact, the professor would say something to the effect of “If you used good objects, you’ll only have to make the change in one place.”

    This of course is only helpful if you really appreciated the power of OOP and planned it from the start. Most of us were flying by the seat of our pants, so it was usually a ton of work to get those changes in



  • I’ve got a couple sources that can probably explain it better than I can, but here’s the gist:

    • Walk through each file you want to read
    • Walk through each line you want to read
    • Replace emojis using RegEx

    The tricky part seems to be defining the range of characters you want to replace. Most emoji are in a particular block of unicode, but there could be a few outliers particularly if you want to remove kaomoji.

    Here’s a Stack Overflow link where there’s some discussion on what that range will be.

    Here’s a Python script that shows how you might do it for one file.

    Good luck!



  • A lot of the criticism comes with AI results being wrong a lot of the time, while sounding convincingly correct. In software, things that appear to be correct but are subtly wrong leads to errors that can be difficult to decipher.

    Imagine that your AI was trained on StackOverflow results. It learns from the questions as well as the answers, but the questions will often include snippets of code that just don’t work.

    The workflow of using AI resembles something like the relationship between a junior and senior developer. The junior/AI generates code from a spec/prompt, and then the senior/prompter inspects the code for errors. If we remove the junior from the equation to replace with AI, then entry level developer jobs are slashed, and at the same time people aren’t getting the experience required to get to the senior level.

    Generally speaking, programmers like to program (many do it just for fun), and many dislike review. AI removes the programming from the equation in favour of review.

    Another argument would be that if I generate code that I have to take time to review and figure out what might be wrong with it, it might just be quicker and easier to write it correctly the first time

    Business often doesn’t understand these subtleties. There’s a ton of money being shovelled into AI right now. Not only for developing new models, but for marketing AI as a solution to business problems. A greedy executive that’s only looking at the bottom line and doesn’t understand the solution might be eager to implement AI in order to cut jobs. Everyone suffers when jobs are eliminated this way, and the product rarely improves.




  • Well, I’m not a psychologist, so I suppose my interpretation might not be correct - the irony mounts.

    But from the graphs you shared, it looks to me like the only people who underestimated themselves were the top performers. And from what I know firsthand with imposter syndrome, a competent person underestimates themselves.

    I used hyperbole for effect, so I don’t think that if you believe you have zero competence in something because you actually have zero competence means that you’re secretly good at something. If you know nothing about plumbing, don’t try to install a toilet.

    But if you’re working in the software factory then you don’t actually have zero competence, you probably have formal education and some experience. Having that feeling that you might not be good enough is a sign that you’re on the right track.


  • I felt like that early in my career. I used to think that being a rockstar developer was a good thing, and I’d be happy to describe myself as one.

    The thing is, a lot of rockstars are really just churning out heaps of unmaintainable code. They think they have a high degree of proficiency, they’re confident in their competence, but there’s a disconnect between what they think and what they produce.

    It can be a sign of personal improvement to question yourself when you think you’re doing great. We owe it to ourselves to ask ourselves critically if we can be doing better. Because if we don’t, and we just assume we’re awesome, then we’ll happily churn out sub-awesome cruft.

    The insidious thing is that self-criticism leads to self-doubt, and imposter syndrome can be quite paralyzing. But if you learn to control your criticism instead of allowing your criticism to control you, you can achieve higher heights than rockstardom.


  • Based on what I know of Imposter Syndrome and the Dunning-Kruger effect, it seems you’re at your most competent when you feel like you’re at your least.

    So if you’re feeling badly because you feel like you don’t know enough to do your job, take some time to remind yourself that other people who appear to be confident have no idea what they’re doing.

    It’s fake-it-till-you-make-it all the way down.