HN user

springogeek

158 karma

* Software engineer at ForgeRock * Hobbyist game developer * LARPing as an 80s programmer

Mastodon: https://mastodon.gamedev.place/@springogeek Twitter (Read-Only): @avivbeeri Github: http://www.github.com/avivbeeri Games: http://avivbeeri.itch.io

Posts9
Comments68
View on HN

This is pretty cute. It'd be interesting to have slightly more "collaborative" mechanics in the next version.

Maybe rather than directly attacking the boss, damage boosts can get stacked up for other players to use? Or maybe "shields", which reduce the cooldown / timeout.

Is there a way to get notified about future versions/updates?

I like this approach to thinking about abstractions. It's easy to forget /why/ you are abstracting something, and this gives some perspective and structure to it.

Pixel Tablet 3 years ago

I've had bad experiences with the hardware maintenance of Google devices. Things break down and Google don't provide good ways to repair them if the device is older than a couple years, so while it's cool, I don't think I'll go for this.

What I read of the developer's blog suggests that it does. In addition to the resolution of various vulnerabilities, web standards are constantly changing and updating, and curl has to keep up, which is pretty hard part-time.

Mature doesn't mean it's static.

That's actually why Qualified Immunity was originally introduced: To prevent courts filling up with potentially spurious cases raised by defendants of other cases or participants of interactions with police.

It was originally conceived to have a much less heavy-handed scope though, but has been strengthened over time to something near-impossible to thwart.

You're right, but it isn't a helpful comment for the discussion at hand. The story in that article, and many like it, are symptoms of a larger problem, but it's not because of public vs private healthcare.

The system works, assuming it's adequately funded, which it hasn't been for a while. Salaries aren't high enough to live on (thanks to the conservative government and creeping privatisation), and then brexit and other immigration policies have caused a shortage of trained professionals and no one willing to fill the vacancies.

There's a whole heap of issues (I've left out quite a few) stacked up against the NHS, and yet it powers on, doing its best.

The actual phrase for describing the NHS is meant to be "Free at the point of use", but people are likely shortening for convenience. People are paying for it, but not in a tangible way.

The main thing is knowing that if you need any procedures, services, an ambulance, critical or emergency care, etc, you'll not be asked up front to pay for it, you'll just be treated. Seeing that principle erode over time is heartbreaking and terrifying.

(rant) Healthcare as an industry doesn't function properly under a capitalist model, which expects that competition and consumer choice will encourage innovation and further competition, leading to a better outcome for the consumer. If you need healthcare, you don't really have a choice in it, or your choices are artificially restricted by circumstance, so you can't benefit from a competitive marketplace. It's a broken system, as far as I am concerned.

* It (usually) doesn't have to be perfect the first time. Programming is an interative process and your first attempt is going to have bugs, or make faulty assumptions about the problem.

* A design which can be generalised is inherently more complicated, and is often unnecessary (you probably won't make use of that generality, leaving you the burden of maintaining it), so you'll be glad you made a simpler first pass.

* I don't like working with docker/containers personally. It makes me feel so far removed from how services are deployed that it's basically magic.

I acquired a D620 at the start of the year to use as a semi-regular hobby machine. I love how user-servicable it is. Pretty easy to take apart and fairly modular design. I swapped out the processor for its maximum spec (a Core 2 Duo T7600) and 4GB of RAM.

I use Badwolf as the primary browser, which comes with built in toggles for disabling images and JS loading, and that makes web browsing tolerable most of the time. I've even managed to stream from it to Twitch using ffmpeg without much of a problem!

If I am working that day, I buy a box of doughnuts to share with my colleagues.

Sometimes I treat myself to a nice meal. Reduced responsibilities for the day, just to make it light and fun.

It's a good excuse to arrange a get-together of some kind. A full table for some board games :)

If you don't mind taking a risk on a physical card game (and you have an extra player), you could try out Netrunner (you can print-and-play the excellent starter set from here: https://nisei.net/products/system-gateway/#bundle).

Pitch: You play as either: an elite hacker trying to break into the servers of megacorporations for fun and profit, or the inner workings of said megacorporation, trying to defend against the hacker.

The game requires you to take risks because it's a game about information control. You don't know what the corp will do to defend itself until you make a run at their servers, and corps don't know exactly how the runner plans to get in, or what they'll find when they do.

The media is often captured using a smartphone, but I don't think I would call unedited media "content". I reckon that the editing process is more likely to be done on a PC/Mac/Workstation than the phone itself.

A couple of things I try to remember, when I work on things: (I didn't coin either of these)

"'done' is better than perfect"

It's easy to get caught in a trap of trying to "perfect" something. If it's good enough to call done, you can always improve it later if necessary. You do need to have some clear definitions for what "done" means for you though.

"make it work, make it pretty, make it fast"

This is adjacent to the first saying. I sometimes find myself trying to optimise something prematurely. This is a good reminder to wait until the [unit of work] is "complete" before I try to optimise it.

I started making games regularly with the PICO-8, and it's a fantastic tool and community.

Eventually I wanted to make larger projects, so I was inspired to make my own engine, for when you want to transcend its limitations.

Because of its minimal nature, you can kind of scope up gradually, to whatever kind of project and scale you like.

https://domeengine.com

Programming in C requires you to take proper responsibility for what you write, but also allows for great power in return.

I've been working on a reasonably large (and cross platform) project in C (https://domeengine.com) for a couple years now, and I find that C generally requires a certain kind of discipline. When you interact with an API, you need to read the docs, figure out their specific preconditions, and requirements on handling frees, establishing what you own and what you don't.

It also helps to make sure that if you allocate something, you clean up after in a clear and well defined way.

You should also get very familiar with debuggers (LLDB/GDB) and other dev tools, to help when you have made a mistake.

In the modern era, you have a couple of options for getting it to run on Windows. C89 using Visual Studio, The MSYS2/MinGW2 gcc toolchain, or a gcc toolchain using the WSL. I use the MSYS2 tools for DOME because it requires the fewest platform-specific modifications to my code, but this varies by usecase.