pelya

That’s exactly the difference. The business needs to sell shit, so your management needs you to get the shit done, just good enough quality to sell it, because otherwise you’re burning them money in salary.

Take any of your hobby projects, and ask yourself - ‘How do I sell this thing?’. You’ll arrive at all the same problems you are seeing in your company. Good managers will explain this and let developers make their own decisions and take part in business processes, bad managers will just dictate which buttons you need to press on your keyboard.

Lines of code is a really ancient metric for managers who are totally ignorant of technology, I was just putting it here for emphasis.

I believe the author got the wrong job position. If your job title is something like ‘software developer’, yeah you are measured by the amount of lines of code. You should aim for a senior role such as ‘system architect’ or ‘technical lead’, then you have some kind of guidelines from the sales side of business, and your job is to turn them into requirements and produce the final product, and you choose the tech stack and other details that are inconsequential for sales bug will get the programmers flinging keyboards.

You did not include the scale in the photo.

It wasn’t an engine limitation, it was a design choice. Heretic is a colorful game, and it was made using Doom engine.

It’s especially bad in Quake, all monsters look like a moving piece of a wall, and the level design is walls on top of walls with some walls in-between. If not for the revolutionary game engine, it would seriously flop.

The answer is 256-color (8-bit) palette.

It’s not the same without two little screws jangling about

It’s cool, but no phone support yet. Games themselves run on my phone fast enough.

Pro tip: for(;;) takes less to type thann while(true)

Testing the interface is more like validating the architecture of your module.

Say, you have your interface IShape, which represents a geometric shape.

Now you decide to add some shape editing capabilities to your qpplication.

Can you rotate your IShape? Can you flip it? So your IShape interface needs methods rotate(double angle) and flip(enum direction). So you add a test that checks that your module exports methods rotate(double angle) and flip(enum direction).

Does your application requires rotating shapes by a fractional angle? Maybe rotating by 90⁰ is enough? So you replace rotate(double angle) with rotate90degrees(bool clockwise) in your test and you can simplify your implementation.

I’ve ported games to web using WASM. You still need to interact with HTML DOM using JS, no way around it.

You use WASM when you either need raw CPU speed, or you have some C++ code that you don’t want to rewrite in JS.

If you just want to make a website, pure JS is better, unless you’re that kind of dev who prefers to render their own text strings pixel by pixel.

Commenting your code is an industry standard. Some kind of separate comment metadata won’t generally work, unless you code exclusively in spreadsheets, where you can add a note to each cell.

Given that it’s a hospital, I guess your management will listen to whomever performs bureaucracy better, not whomever codes better.