61
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
if you're against skub you're just really stupid. You don't get an argument as to why, you're just stupid. That's all you get.pisschamp
this tbh. instead of telling people to stop, understand and counter their misconceptions. see: black man joins kool kids klub, gets the chapter lead to stop being a kool kids klub member by just being a friend and proving by example how his racism was based on misconceptioncounterpoint: it's literally insane to try and play ball with dishonest people on a lego forum
this was actually cool up until like episode 12 when it started going absolutely nowhere leaving footage completely out of context to where we have to wait for some guy on Reddit with too much free time to go sherlock holmes on iti dont hold much stake in the fan theories or trying to decipher what it means, i just think they're neat to watch because someone put a lot of effort into trying to recreate psx era graphics so faithfully
i will say though it's great to fall asleep to. it puts me to sleep before the video ends
Oh look, another envy filled communist.im a warm blooded american, i just know a bottom when i see one
do u think the FBI reads the BLFI've got no doubts a few topics prolly got probed after sephiroth shot up his shool
Cost in software can equate to many things. Something that is expensive can literally cost money, can take excessive amounts of time, or result in inferior quality. In this example, cost and time constraints are eliminated or reduced, so the depreciation of quality is increased. You may end up waiting a significantly longer time for an inferior solution, because the cost of change over time is exponential, not static or even linear.thanks for tell me something i already know and not answering the actual question 😔
A change that costs, say, 10 hours in the design phase could cost 500 hours during development or greater testing. Adding mod support to a big complicated game very late in development could equate to years of work. Furthermore, the cost of a change and the actual work put into a change isn't 1:1, nobody works at 100% efficiency. You're not actually going to spend exactly 500 hours on a 500 hour change. You'll lose some quality. The bigger the change, the bigger the difference, the more quality lost, exponentially. The sooner you start the better.
This is obviously more of a problem when you're designing multi-billion dollar systems for IBM, but I imagine the concept should hold true no matter what software you're building