Rog Dolos 🏳️‍⚧️

@RogDolos@mastodon.gamedev.place
154 Followers
257 Following
692 Posts

Indie game dev.
Working on co-op games, as always.

Enby. Pansexual. Queer. 💗
🌈❤🌈💛🌈💙🌈

PronounsThey/Them 🌈
Websitehttps://rogdolos.com
YouTubehttps://www.youtube.com/@RogDolos
Bluesky: Users verify their age by adding a payment method or uploading a photo ID.

Mastodon: Users verify their age by posting pictures of the vintage computer equipment in their homes.

Happy international nonbinary day everyone!! All of you fling your genders up into the air like mortar boards or discarded bras or pizzas, dealer's choice

#nonbinary #internationalNonbinaryDay

AI will not make you a better writer if you’re a good writer.

Those who actually know how to write know this and have every right to be smug about it.

very mad about an article i saw on bluesky by an "expert" who claims its fair steam gets 30% because they allegedly created an ecosystem of gamers who impulse buy a bunch of games they never play

having a backlog of video games you own because you think you might like to play them some day is so ridiculously common that there's an entire cottage industry of channels on YT dedicated solely to "how to handle your backlog" videos

like come on man steam did not create this phenomena!!

Blender Studio's long awaited second game project, focused on creating a bite-sized interactive storytelling playground.

Play as a big adorable dog and explore the winter woods with a little kid.

The goal of this project is to create a pipeline between Blender and Godot to make the asset and level creation process as seamless as possible.

Homepage
https://studio.blender.org/projects/dogwalk/

Steam
https://store.steampowered.com/app/3775050/DOGWALK/

#Blender #Godot

@eniko my hot take is that Nintendo is actively harming their brand by fighting against emulation. It was due to easily accessible emulation that modern generations fell in love with games released before they were born.
One thing the AI craze is showing me is that there really is a generation of ‘programmers’ who actually feel that designing, coding and optimizing is somehow the tedious part of the job and not the fun part we all know it is…
I changed the way I work a couple of months ago to follow this advice, it made a big difference and my productivity went up by miles.

I know sometimes ppl get frustrated when I link Bsky here but there is something it is important be seen by queers who care about Standards

https://bsky.app/profile/cctl.me/post/3lsthzde3h22g

Cable Contributes to Life (@cctl.me)

since it's the last day of pride month I figured I'd at least make one thing for it... i now unveil to you my greatest invention: color bars pride flag

Bluesky Social
One last gay thought for pride month: if you’re someone who has never experienced discrimination you may not understand why we need pride and rainbows everywhere. When I see a pride flag, it tells me that I am okay to be here. I look for pride flags to know if a neighborhood is safe. I look for pride flags to know if a business will treat me with decency. It’s the bare minimum and the least effort and isn’t real activism and all the other things, but it’s something better than being openly hated
×
I changed the way I work a couple of months ago to follow this advice, it made a big difference and my productivity went up by miles.

@kenney

yeah I highly agree. For instance there is a saying in programming "first make it work, then make it fast"

@farooqkz @kenney where would „writing the docs” be in this approach?
@metaphil @farooqkz @kenney you would be surprised...

@uffke @metaphil @kenney

Some recommend writing docs before you write the program.

@farooqkz @uffke it is surprisingly helpful to start with a little readme file describing the features and how to use them, in order to get meaningful answers form future users @metaphil @kenney

@farooqkz @uffke @metaphil @kenney

I find that writing the docs helps me find both bugs and potential usability improvements, because it helps me step out of my own mind into an imaginary newcomer's, and that newcomer uses the code quite differently from the way I do. The newcomer is also less forgiving than I am. Thus careful documentation is important for the output it produces, but also for the effects it has on the developer and the code.

@CppGuy @farooqkz @uffke @metaphil @kenney Even doc comments help here. If you find yourself describing a lot of quirky edge cases, it's a good opportunity to reconsider whether the logic can be simplified or cleaned up.
@metaphil @farooqkz @kenney or making it secure ✌️
@luceos @farooqkz @kenney 𝗈̶𝗋̶ and accessible ✌️ 😇
and yes, I'm well aware of the inaccessibility of unicode strikethrough „font“ generators, thanks for not pointing that out, unfunny-part of fedi ;-)

@metaphil @farooqkz @kenney pick two

Fast, secure, documented, cheap, performant

😬

@farooqkz @kenney
"Premature optimisation is the root of all evil."
@kenney my daily struggle 😅

@kenney #AltText4You

A hastily-drawn circle that isn’t quite closed, titled “Just make it exist first”.

Beneath it, a perfectly closed circle, titled “You can make it good later”.

@jdeisenberg Thank you, I've added it
@kenney Besides productivity, I'm sure you feel much more at peace now.
@kenney this is also called "technical debt" btw. :)

@tomtrottel @kenney
Yes and no.
Something existing gives more concrete details, and at that new point you see more and clearer.
It is debt only if you leave it there for a long time. But initially it was a step that supported you in your climb of unknown and complexity.

Those do no mistakes, who start nothing.

@kenney This is difficult to learn!
@kenney beautiful wisdom. thanks for posting.
@kenney I was about to doomscroll and procrastinate, I'm going to give it a go right now
@kenney my ADHD perfectionism need this reminder on the daily.
@kenney good that this work for code, but not for governance. The system has deteriorated, not gotten better.
@kenney That's a really good principle that I adopted years ago. Especially when I translate, which I do a lot. First: translation almost as stream of consciousness, superfast, then two or three correctional evaluations.

@kenney

make a mockup

management decides it is good enough
now mockup is in production and never touched again

@Joe_von_Saporski

I can't tell you how often this happened to me. I learned pretty quickly not to show my work until I was absolutely forced to. And when that finally happened, which it always did, I made sure to plaster warnings ("test system" or "WIP - output not verified" or "demo only") all over it and all its output. That still didn't stop them from trying to put unvetted systems that were still a WIP into production but at least I could say 'I told you so' later.

@kenney

@Joe_von_Saporski @kenney Unfortunately, that's true. Not only management is the problem also marketing.
If marketing guys are in your area, cover your monitor or show boring stuff!
@kenney Most people forget "later". :/
@kenney
I didn't need to be told that. I figured it out when quite young, probably in my twenties when I started writing things, possibly a teen.

@iclast @kenney

looks like you got the first part down, could use some work on the second judging from your website 😹😹😹

@kenney I have been yelling about it to my gamedev and gameart students for 5 years and a single one listened
@kenney just as long as 'release it' is step 3, not between steps 1 and 2.
@kenney I like the first one better.
@wcbdata @kenney The first is far more expressive.

@kenney mvp

:

small good first prototype

make it great ( give it enaugh space to breath )

scale it

:

minimum viable product

:

@kenney just make it work, then keep the temporary state forever.

@kenney

Sir R.A. Watson-Watt would be proud of you.

@kenney

Distance from couch now exists.

@kenney Which can be OK as long as the "later" bit happens, and it does depend on what "IT" is so many companies do the first bit but release the thing too early in it's lifecycle.

@kenney

This is the only way I know. Sometimes even the draft is good enough.

Very likely that the entire creation has been done that way. And we still wait that ends will meet. And that shit people become angels....
@kenney this is a) excellent advice and b) the advice I have the most trouble taking

@kenney There is however a fine art to making it exist first without digging any enormous holes that will haunt you for the rest of the product lifetime. That's one of the signs of a really good systems architect

For open source it's also often the case that make it work will pull in "make it work nicely" and "I've written an install document" people.

Sometimes even "I can't stand the random formatting in your repository can I please fix it" people!

@kenney
I use, "don't let perfection get in the way of good enough "
@kenney Gonna take this to heart
@kenney that's true man.

@kenney this can be great advice for individuals like me who procrastinate.

Not so great when adopted by for-profit corporations. Case in point: "AI" companies.

@kenney not sure how good of an idea this is 
@kenney I definitely agree. Just not sure why it is so hard for me :)
@kenney i like the top one too

@kenney

There are no great writers. Only great re-writers.

@kenney You're lucky you work somewhere that you get to make it good later… for a lot of us, that opportunity never arises.
@kenney @nixCraft Problem for most firms is they just want it and don't care if its good, then when it craps on them, probably for security reasons they complain you weren't doing your job.

@kenney My brother, who gets more shit done than anyone else I know, has a saying: "If it's worth doing, it's worth doing badly".

Which I think is pretty much the same idea.

I remember asking him many years ago what the key to getting shit done was, and he said "Start."