Readit NewsI think I might know...
For us, an accurate delivery date on a 6 month project was mandatory. CX needed it so they could start onboarding high priority customers. Marketing needed it so they could plan advertising collateral and make promises at conventions. Product needed it to understand what the Q3 roadmap should contain. Sales needed it to close deals. I was fortunate to work in a business where I respected the heads of these departments, which believe it or not, should be the norm.
The challenge wasn't estimation - it's quite doable to break a large project down into a series of sprints (basically a sprint / waterfall hybrid). Delays usually came from unexpected sources, like reacting to a must have interruption or critical bugs. Those you cannot estimate for, but you can collaborate on a solution. Trim features, push date, bring in extra help, or crunch. Whatever the decision, making sure to work with the other departments as colaborators was always beneficial.
Mediaboard hardware is notoriously underpowered, especially with 3D. The touch response times are also questionable, usually designed for tap instead of swipe.
If a board game needs a computer to handle the rules, then it is a needlessly complicated board game.
Setting up a game can be tedious as well; Axis and Allies is notorious for taking longer to set up than to play, but it's a lot of fun once you get going.
This reasoning never made a ton of sense to me. Gen Z don't use devices with knobs and buttons anymore, therefore we should all design our interface elements to look like nothing in particular?
If you give someone young and tech savvy a digital UI, they will figure out how to use it. It's precisely the oldest and least tech savvy users for whom interface design is most important, as they are more like to get frustrated and quit your app. Why optimize for the young, then?
(I mean, it's a rhetorical question, as I already know the answer - the designers creating the interfaces are themselves young and tech savvy gen-Z'ers.)
Knobs work as a tactile interface that require two fingers minimum to rotate predictably. With digital screens we lost the tactile element, and mandated a new one finger (thumb) minimum. Interfaces had to adapt, which is why knobs were replaced with sliders. Changes like this happened all over the place; not because of "gen-Z", but because they were the most effective solution for the platform.
To pre-empt the typical reply, yes you must serve a cookie banner even if you are only using functional cookies.
Organizations, and typically lawyers, skew conservative and lazy. A little cookie-consent cottage industry popped up to handle GDPR, so instead of worrying about the regulations most companies pay the small monthly service charge for a third party to handle consent. The consent companies built the most compatible solution, a banner, with the most conservative options as default to prevent any legal quandary.
Most public facing sites do have analytics (usually LOTS of analytics) and ads, so the banner is mandatory for them. If you understand the regulations, and don't violate them, then consent is not necessary.
https://files.catbox.moe/i8tfkl.jpg
https://files.catbox.moe/mw8vbc.jpg
Then I thought what would it make from an already dark and grim scene, like HL2 Ravenholm
https://files.catbox.moe/d7z77h.jpg
but nothing really? Just made the whole thing a different color scheme + changed some architecture
Bottom: Shady Sands