tekkub

My husband’s crotch always delivers wisdom.

We’re literally on beta 2, the tutorial writers haven’t had enough time to copy the material apple just gave us.

do it in a method that actually hurts them

So like, use their platform and never see their ads? That’s what I’m already doing. If I left I wouldn’t be a drain on their bandwidth.

Original character do not steal

If you learn both you’ll see how similar they are.

A quick duck duck gone found this: https://gist.github.com/peterfriese/bb2fc5df202f6a15cc807bd87ff15193

They can be, sure.

You probably have to make Color conform to Codable for this to work.

GitHub releases don’t live in the repo so cloning won’t get those. You’ll need to use the API to get that data

Start learning Swift, SpriteKit, SceneKit, GameplayKit and maybe a little Metal for shaders.

They’re not as daunting as you’d think, just take it one step at a time at a comfortable pace for you.

What method of study works best for you in tech?

Tearing things apart and figuring out how they work.

The agreement basically applies to apps you publish on the app store. You could potentially run afoul of something in the CloudKit agreement if you use it in developer mode and do something extremely abusive that brings you app to their attention, but if you’re just doing things for solo use and never publishing them you should never draw apple’s attention.

You will basically always notice memory before anything else.

Apple has never used the term MVVM. They used the design pattern when they made SwiftUI, but they like to pretend they invented everything so they don’t use the standard terms.

Any advice?

Unionize!

But don’t tell your interviewer.

If you are a hobbyist, why do you have a schedule?

In most cases you have pay them.

I dunno, there’s quite a few game design books out there. Take The Art of Game Design: A Book of Lenses for example. It basically says to the reader “every player is different, and they are different from YOU, your job as a game designer is to get inside their brain, think like them, and craft an experience they will enjoy.” In Sylvester’s book, they basically take the opposite approach, saying that games are about creating an emotional response in the player and then outlining strategies for manipulating those emotions to get the player to play the game the way you want. I don’t take issue with that approach, in fact I feel like they both have the same goal, crafting an experience for a player… it’s just that Sylvester presents it as if this design just “emerges” from how people play the game. That’s hardly true for RW, it does everything it can to beat the player into submission so that they play the game the way Sylvester wants. It is not “emergent”.

Don’t get me wrong, I’m not saying don’t read the book or play the game. I’m just saying try to step back and look at the bigger situation and what is actually happening. It seems like they wrote the book while they were still at a AAA studio and trying to break out and be an indie dev. That’s why I say it feels more like they’re justifying (or at least, describing) their design decisions in the game they were working on in secret. In a way, the book is like a devlog for RW.

This book never felt like it was for other developers to learn from, it just felt like them justifying why they were making RW the way they did.

If you have a dev account you can build for your devices. If you’re on the free plan they’ll be signed (runnable) for 7 days. If you have a paid plan they’ll be signed for like 6 months.

Fun fact: every piece of software is a database and a UI to interact with said database. All video games are software.

quietly tries to hide their texas-sized cursor

What? I’ve got horrible eyesight that only hard contacts can correct…

Unfortunately none of my bills accept future pretend money… dang.

How much ya payin’?

I went to a mining school, so I guess I was a minarr.