Jason Thor Hall / PirateSoftware / Maldavius Figtree / DarkSphere Creations / Maldavius / Thorwich / Witness X / @PotatoSec - Incompetent Furry Programmer, Blizzard Nepo Baby, Lies about almost every thing in his life, Industry Shill, Carried by his father, Hate boner against Ross Scott of Accursed Farms, False Flagger

  • 🐕 I am attempting to get the site runnning as fast as possible. If you are experiencing slow page load times, please report it.

Which will happen first?

  • Jason Hall finishes developing his game

    Votes: 33 0.8%
  • YandereDev finishes developing his game

    Votes: 412 9.7%
  • Grummz finishes developing his game

    Votes: 117 2.7%
  • Chris Roberts finishes developing his game

    Votes: 143 3.4%
  • Cold fusion

    Votes: 1,638 38.4%
  • The inevitable heat death of the universe

    Votes: 1,925 45.1%

  • Total voters
    4,268
It didn't sell poorly.
Normies just consume the slop when FOMO / rarity is introduced.
Given it's budget it did flounder hard VS expected sales figures. Having a pre-game mainstream popularity explosion released PC game title move 10+ Million units is a crazy fucking milestone to live up to. Which it did not even with all the time it's had since release. It didn't fail in a sense of only shitting out sub milly units but it did fail compared to what blizz had expected from it and it never got the lightning in a bottle e-sport status that it's grandpappy did imo. It did limp along in terms of support
 
C-like:
// Mald talks about how undertale's dialogue system is insane
global.dialog_array[1583,1] = "There are sections of the game that show like, oh, here's an example:";
global.dialog_array[1584,1] = "All the dialogue in all of undertale is in a single switch case statement in one object.";
global.dialog_array[1585,1] = "Its thousands and thousands of cases long. Single object.";
global.dialog_array[1586,1] = "All of the dialogue in the game. Hardcoded into that object.";
global.dialog_array[1587,1] = "Insane. Insane behavior.";
I don't know why but his code makes me so irrationally angry. I want to teach the kid, but he's WAY too proud to be taught by anyone. Maybe I get so angry because he talks and postures that he's so experienced yet produces that garbage.

Another "interesting" take from Mald. The "amazing AGS QA" is particularly funny,

people (rightfully) questioning his "developer" credentials, seeing as he spent a lot of his time as QA, which is as close to "unskilled labor" as you can get.
If Amazon's QA team was so good and paid so well, then why did he leave? To make his massive array switch case slop? I still think he leaves jobs because he gets outed as a retard who doesn't know anything.

Also QA are not developers, they never will be developers, they are developer support, always have been and always will be. They are the water-boys of development. There's a major and significant difference, mald. They have drastically distinct roles with different focuses and skill sets. Plus if most developers weren't so fucking retarded, they could essentially remove more than half of what QA does overnight, but unfortunately test driven development is actually the exception not the rule. TDD actually makes the QA team do exploratory/integration/system-level/real-world testing vs the dumb automated bullshit that should have been done at the actual developer level. Which that kind of testing for QA is actually fun because it's not fixing garbage developer slop. I've had to deal with many QA teams and that has always been their sentiment. "Let us do the fun testing."

Exploratory/integration/system-level/real-world testing is the real star of the show and it's what QA should be doing but really never get to do it because they are busy writing retarded test plans for code like mald's game. Well done TDD is insane at how well it works but no one likes to do it because it's incredibly slow. You write tests first then write code to pass the tests and developers want dopamine hits for writing slop instead of dopamine hits for writing good testable code that people would actually be proud of. TDD actually forces developers to think about problems before programming which causes an exponential compounding effect of better code if done right. Who knew thinking out things before acting would result in a better outcome? If anyone learns programming today or tomorrow, learn and employ TDD correctly and get in the habit. You'll be a 1% top tier programmer by default.

Side note: In the future, developers will really only produce well defined test code and AI will solve the challenge of writing a solution. With developer driven test code the AI can sit and turn out solution after solution until all tests pass. It's a hot take, but it's going to be true, it's something the company I'm at has been doing for the past few years and it's incredible at how well this works. AI is really good at writing code that solves well defined problems. 9 times out of 10, it happens to be better and faster than most top tier developers in our experience. It's funny our top devs actually like this paradigm way more because instead of worrying about random dev shit, they can focus on thinking about the actual problems and developing a well structured plan of attack. We call it ADD internally, automated driven development. (I came up with the idea over 10 years ago and we built the first working example about 8 years ago, the past 2 years we've employed it across the entire development team)
 
Well done TDD is insane at how well it works but no one likes to do it because it's incredibly slow. You write tests first then write code to pass the tests and developers want dopamine hits for writing slop instead of dopamine hits for writing good testable code that people would actually be proud of. TDD actually forces developers to think about problems before programming which causes an exponential compounding effect of better code if done right.
It's also incredibly hard to do if you don't have mocking for the things you interact with (some of which are near impossible to mock), and often gets very repetitive very quickly in my experience. I usually end up with tight unit tests for things that are especially fragile or especially vital, and a manual test covering most of the surface of a feature (in personal code at least). I've missed plenty of stupid obvious things this way, though they're usually fixed in a couple minutes and not vital.
Side note: In the future, developers will really only produce well defined test code and AI will solve the challenge of writing a solution. With developer driven test code the AI can sit and turn out solution after solution until all tests pass. It's a hot take, but it's going to be true, it's something the company I'm at has been doing for the past few years and it's incredible at how well this works. AI is really good at writing code that solves well defined problems. 9 times out of 10, it happens to be better and faster than most top tier developers in our experience. It's funny our top devs actually like this paradigm way more because instead of worrying about random dev shit, they can focus on thinking about the actual problems and developing a well structured plan of attack. We call it ADD internally, automated driven development. (I came up with the idea over 10 years ago and we built the first working example about 8 years ago, the past 2 years we've employed it across the entire development team)
This sounds kind of miserable, but aside from that, how closely do you check the AI code over, and how tight are your tests? In my experience AIs tend to generate really suboptimal solutions which make it not worth calling on most of the time. It seems like you'd need a very large amount of test surface for each piece of anything complex to ensure you aren't getting complete garbage as well. I'd be interested to hear more about how you work this, especially in cases where every possible input cannot be tested.
 
Be careful, this rumor originated from Jason himself so I wouldn't trust it too much
I know, that's what makes it funnier. Either he's lying out his ass, or the game was so worthless, that even after suffering millions of subscriber losses in WoW, a mount still managed to out-sell the sequel to one of the most popular RTS games ever.
This doesn't make any sense. Are product managers also "developers"? Being part of the development team doesn't make you a developer.
Receptionists. Janitors. The office supply delivery driver. The guy who cuts the grass. The guy who delivers the 5 gallon water jugs. They're all Developers now.
 
AI will solve the challenge of writing a solution.
I have some doubts about that and my 2 doubts basically are:

  • On OOP I never saw an AI dealing well with loosely coupled or complex objects, like microservices that a lot of classes and checks are done on runtime and relies on the dev coding well or uses an extremely complex architecture.
  • If you solve the first which IMO is doable by AI, you will ended up needing to use an LLM. The problem of LLM's is that it relies on cloud, like copilot, gpt4,... is that you're not running on your machine. This would break a lot of ISO and others code standards, even more that those AI are full of prompt scape, this can easily make a company lose their entire codebase for AI
 
  • Like
Reactions: 419
Also, I lol'ed at his "my game is unhackable because it relies on Steam achievements", the guy is truly incompetent and arrogant. Steam DRM is basically non-existent because in 99% of cases it's bypassed by putting a custom steam.dll that's been unchanged for 10+ years.

To "hack" his game all you have to do is modify this dll to return correct results from achievement-related calls. The reason why his game is still not hacked can summarized by an old Russian joke (I always thought it has American roots, but judging by Google it does not):
Two cowboys, a local and a foreigner, are sitting in the saloon somewhere in Western American steppes drinking whiskey. Suddenly, someone outside rushes down the street at wild speed, firing revolvers in all directions.
However, no one in the sallon bats an eye.
A foreigner asks the local:
— Billy?
— Yes, Harry?
— What was that, Billy?
— Oh, that was the Elusive Joe, Harry.
— Why do they call him Elusive Joe, Billy?
— Because no one has ever caught him, Harry.
— And why is that, Billy?
— Because nobody gives a shit about him, Harry.
 
Last edited:
Receptionists. Janitors. The office supply delivery driver. The guy who cuts the grass. The guy who delivers the 5 gallon water jugs. They're all Developers now.
They are at least much less likely to be whiny dipshits than some of the programmers, so I think we should replacd Jason's name with whoever was the top janitor of the month.
 
Another day and another video where our main "hero" complains about the changes that will help users, but as a dev he thinks they are not good. I sense a pattern here.
A lot of comments are not agreeing with him.
>your reviews have to be informative and on topic
>"wow this is blatant censorship, every pee pee poo poo review should be treated equally"

This dude is incapable of having a decent take.
 
Receptionists. Janitors. The office supply delivery driver. The guy who cuts the grass. The guy who delivers the 5 gallon water jugs. They're all Developers now.
Yes, but do they have the same Cocaine Dealer that Jason Thor Hall has? Because I know the guy who used to sell him his weed and harder shit and in his words:
"That Sheep-Fucker is a fiend. A rich one but still a fiend."
Jason often spoke about "Doing bumps" and taking entire weeks off because "I was on shrooms, bro." after ghosting everyone only to show up the next week.

Edit: It was Tustin. We all knew the same dealers. We all knew the ghetto on El Camino Real and Newport. We all knew the other ghetto on Newport and Michell. We knew the dealers got their shit from Mexico. We knew them by first and last name. Jason wasn't just a "tester" when it came to his daddies video game company. He'd shake his greasy, smelly, moldy hair and scream "I AM THE LIZARD QUEEN!", ala The Simpsons letting all the potheads he was high and everyone else that he was trying to be "Lol, totally random bruh!"
 
Last edited:
Yes, but do they have the same Cocaine Dealer that Jason Thor Hall has? Because I know the guy who used to sell him his weed and harder shit and in his words:
"That Sheep-Fucker is a fiend. A rich one but still a fiend."
Jason often spoke about "Doing bumps" and taking entire weeks off because "I was on shrooms, bro." after ghosting everyone only to show up the next week.

Edit: It was Tustin. We all knew the same dealers. We all knew the ghetto on El Camino Real and Newport. We all knew the other ghetto on Newport and Michell. We knew the dealers got their shit from Mexico. We knew them by first and last name. Jason wasn't just a "tester" when it came to his daddies video game company. He'd shake his greasy, smelly, moldy hair and scream "I AM THE LIZARD QUEEN!", ala The Simpsons letting all the potheads he was high and everyone else that he was trying to be "Lol, totally random bruh!"
Was he more, or less productive when he was under the effects of cocaine?
 
Well done TDD is insane at how well it works but no one likes to do it because it's incredibly slow. You write tests first then write code to pass the tests and developers want dopamine hits for writing slop instead of dopamine hits for writing good testable code that people would actually be proud of.
Here is the thing: you are right about most things, but also wrong about some.
Jason is a little QA monkey that knows just enough about dev work to imagine himself, in best dunning-Kruger fashion, to be a gifted developer that just naturally can see and do all this stuff the other developers dont see.
You’re probably a developer that knows just little enough about C-level decisions to go off about TDD like this.

Yes, TDD is slow. But slow means fucking expensive holy shit it’s so fucking expensive. And slow might also mean I’m unable to make stakeholders halpy, customers happy, investors, whoever else is paying the bill to keep the lights on, happy. And that is what sometimes matters more than a perfect product, because none of you are getting paid if we can’t keep the dough rolling in.

If the feature takes one developer a month and doing TDD doubles the dev time, it suddenly costs $20,000 dollars instead of $10,000. Some QA faggot monkey costs not even a fifth of that. Now multiply by number of devs.
That’s the issue here, not dopamine addicted devs or whatever. The fucking Silicon Valley bubble made developers so far detached from the basic concept that they need to actually somehow generate a value approximating their overblown salaries, they treat work like their hobby free time and get pissed when grown ups have to make suboptimal tech decisions to keep the cash rolling. Fuck you, I’m not paying a few thousand bucks so you can fuck around with your linter for two days.

Sorry for ranting, nothing against you personally.
 
Back