Show HN: I'm 48 and finally learning how to be a game developer
171–180 of 258 posts
Re: Show HN: I'm 48 and finally learning how to be a game developer
#172Re: Show HN: I'm 48 and finally learning how to be a game developer
#173Re: Show HN: I'm 48 and finally learning how to be a game developer
#174Earlier quoted context omitted.
(I don't know how much you know about electronics so sorry if I'm stating the obvious here) 9V batteries sound and look like they should last long, but putting 6 1.5V batteries in series should last much longer. 9V batteries have a typical capacity of ~550 mAh, 1.5V batteries (even rechargeable ones) have a typical capacity of 2000~3000 mAh.
Of course 9v batteries are just six 1.5 cells in a rectangular pack- often they are even made of round cells like AAA, only much smaller.
Re: Show HN: I'm 48 and finally learning how to be a game developer
#175It’s gratifying to see this remain #1 on HN for so long. I sincerely wish you luck. I like your privacy policy: https://13bananas.com/privacy-policy/
haha, and I used to be really proud of mine: https://sonnet.io/tommy-the-toe/policy/
Sonnet.io seems to be less chatty, except for the requests to Heroku.
Congrats on you game! It looks really nice, and I wish you the best of lucks!
Re: Show HN: I'm 48 and finally learning how to be a game developer
#176Re: Show HN: I'm 48 and finally learning how to be a game developer
#177I've been doing it on and off for 14 years and I'm still learning how to do it. Started a new prototype last night after the kids went to bed.
Do you post your WIPs anywhere?
Re: Show HN: I'm 48 and finally learning how to be a game developer
#178Also, 800 upvotes can't lie. I wonder, which part of the premise resonates with the HN crowd: "it's never too late" or "I always wanted to make games too"?
Re: Show HN: I'm 48 and finally learning how to be a game developer
#179Earlier quoted context omitted.
haha, and I used to be really proud of mine: https://sonnet.io/tommy-the-toe/policy/
While I appreciate its simplicity, private data on the internet is messier than it sounds, and almost impossible _not_ to collect it (server logs store the ip by default for example). In particular, 13bananas.com has outbound connections to stats.wp.com (prompty blocked by uBlock Origin) and to bandcamp.com. Also, uBlock Origin seems to log access to Google Analytics through a bandcamp script. Sonnet.io seems to be l…
Yup 100% agree. One of the reasons I do this is that I used to work in adtech (focusing mainly on privacy, which is a complete joke in that industry, but we all know that), so in most of my projects I try to use privacy-friendly alternatives.
For instance, the Heroku requests will either use umami (without sessions/state) as well as stripping unnecessary headers/cookies from the payload from the network traffic (e.g. credentials: none). The code is available on GH.
I still want to know what's happening on my site, e.g. UX-wise, so I can fix and adjust stuff. But, so far I've never needed to know "who" is visiting vs. what are the general interactions with the content.
Just like oil/CO2 emissions, user data should be considered a burden, not an infinite resource.
Even if your expectations of adtech are already low, I can assure you that some of the shit I've heard considered acceptable is just mind-boggling, and scary.
Re: Show HN: I'm 48 and finally learning how to be a game developer
#180Earlier quoted context omitted.
> Make as simple a game as possible when you're starting Back when I had enough spare time to do game jams, one critical thing I learned was, once you have some idea, make it simpler. Now make it even simpler. And then, make it simpler again. Repeat that about 20 times, possibly more. Now you have something that you can possibly build and actually release, and guess what, counterintuitively, it'll be fun as hell. Coz…
I've never been brave enough to do game jams. I dunno, I've always been afraid I'd break under the pressure. Was it fun for you?
It's been frightening alright but I learned so much, and not just about game dev: lots of takeaways that apply to day-to-day development, like finding the balance between quality and getting things done, keeping things ultra-simple, understanding the value in inlining or even repeating code, finding the minimal abstraction sweet spot...
It's OK to be afraid! Turns out it also teaches that you can just let it go, go for it and enjoy the wild ride.