Making your own engine is worthwhile learning experience. The same as trying to recreate any of the foundational tools that you use. Might not be the fastest or best way to make a game but a good way to make yourself a better developer.
Keep in mind that if you actually want to make a game, make a game not an engine. Too many video game projects get bogged down in the engine development stage and never make it to completion.
Do people even make their own engines anymore? If this wasn’t a pet project I would have dropped the entire thing as soon as I started dealing with 3D models, and visited Godot’s homepage.
…
Perhaps I should get my hands on Godot at some point.
The in-house engines I know are being used are also really old - hell, 343i even decided to ditch the fossil that once was Halo: CE’s engine because of technical debt and outsourcing blood sacrifices
This is my 4th Vulkan related “project” and 2nd attempt at making something other than a glorified tutorial workspace in 6 years, and it took me 4 weeks to draw this stuff with minimal technical debt.
I could just use an existing game engine, but what’s the fun in not manually sorting all draw commands by mesh>pipeline>material and hunting synchronization hazards by just looking at funny glyphs for extended periods of time?
It’s a good thing I’m a hobbyist so that I can avoi- hmm, now that I think about it this feature could be really cool and shouldn’t take too long to implement…
Spouse at 7:00 AM: “Why do only some of the house lights work and there’s no hot water?”
Me: “You know that quick fix I was working on last night. Well, umm, one thing led to another aaaand… Umm… Just so you know, your phone is using mobile data because the wifi is out.”
Step in front of the train: Tell your manager this whole project is dumb, provide a list of reasons why it's a bad idea and explain you are prepared to resign rather than enable its further development.
There are actually a few of them alongside Postmarket. LineageOS and its various forks, Ubuntu Touch, KDE Plasma Mobile, Graphene, Replicant… the list goes on!
Unfortunately, I was playing around with them a few years ago and Android phones seem to be a POS to try and switch the OS on. But, it’s clearly done. I’m thinking about at least popping one of them onto an older phone or tablet.
Solid Explorer has a “Recent” category on the directory tree. Really handy. Also, if you long-press on a file, you can open the directory the file is saved in.
Maybe I’m a sentimental fool, but I feel like there should be some kind of basic respect for the craft, and doing things the right way just because. I get making bad code to meet a deadline, but not if you have a choice.
Then again, I’ve never done coding as my main job.
I have done it as my main job and I echo your sentiment. It’s inevitable that sometimes you have to meet a deadline or get something more important working first, but if you write bad code because you are lazy or unwilling to read the docs to do it right, shame shame shame.
Some people just don’t care. To me it really feels like they are trying to create the problems to later sell the solution, and it’s a never ending cycle. I’ve quit my recent job because 90% of the team just sucks, security risks everywhere, the API just doesn’t respect contracts, there’s no contract actually, we just ask on private chats how to integrate with it really. New features on top of buggy code while support is on fire with the 100th bug ticket reported in just a week. Not to mention that you have a design team, a project manager and a “VP of engineering” but the epics they want you to do are almost just the title of the idea they had at lunch 😅.
This guys are very lucky because the operation teams is able to cash in millions of revenue a year by combining excel, monday and WhatsApp to do their jobs, while a few are still forced to interact with a piece of shit of software that the engineer department provides to them…
Can confirm - you work like a dumber, more tired version of you needs to maintain it, so comment accordingly. Also, you do the work right but also fast; and you see how right you can do it in a reasonable timeframe of course.
But we fired a lot of our mentors after Y2K to save money that quarter. And the juniors there had no learning as to the whys of the whats when it comes to best practice. Those juniors became seniors and their juniors are 2nd-gen flying blind. We’re doing dumb things because we know why we shouldn’t, but we don’t understand that we shouldn’t. (Hint: if someone says “Yeah But,” they may not get it)
We need to rediscover the whys we lost; and it’s gonna be hard to really understand it, but we’ll figure it out. A few more ClownStrikes and we wont have a choice!
Tangentially related, I remember at one of my jobs being tasked (several years in a row) with updating the copyright year in all our source files’ headers.
Yes, it’s actually to notify people who aren’t part of countries with membership to the WTO of the first available year of public declaration of distribution without restriction, however, putting “1997” on your website makes it look old so people put current year to make it look new.
It’s only legally distinct in Aruba, Eritrea, Kiribati, Micronesia, North Korea etc… so it’s almost entirely useless.
I meant it’s a red flag if someone can’t spin up the code and is making an intern change it by hand every year.
programmer_humor
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.