: Senior Director, Rendering. 
: Photography & Creative coding. Sometimes I write on c0de517e. My opinions are not my own. I don't tweet about ROBLOX
Time to change my pinned tweet I think
Näytä tämä ketju
Why nothing great is ever good http://c0de517e.blogspot.com/2017/10/the-curse-of-success-why-nothing-great.html … - Over-engineering is the root of all evil http://c0de517e.blogspot.com/2016/10/over-engineering-root-of-all-evil.html …
-
-
On my personal projects I definitely need the later reminder. Thank you.
Kiitos. Käytämme tätä aikajanasi parantamiseen. KumoaKumoa
-
-
-
"Production is a monster that devours everything" - great quote
-
It's an idea from Creativity Inc. I think IIRC one of the chapter is called "the production monster" or something like that
- Näytä vastaukset
Uusi keskustelu -
-
-
Only solving current problems can create a lot of debt. Experience can tell you a lot about problems that are going to happen but are not current, and engineering in that anticipation is a good thing imo - that doesn't translate necessarily to over-engineering.
-
I'm conflicted, I don't see future-proofing and over-engineering as remotely the same thing. Ultimately I think a well-engineered (read: often a simple one!) solution to a current problem will allow you to extend, refactor, etc, as the future problems come up.
- Näytä vastaukset
Uusi keskustelu -
-
-
Great post!
Kiitos. Käytämme tätä aikajanasi parantamiseen. KumoaKumoa
-
-
-
would it be better to flip a coin when deciding between explore vs. exploit...it's what a lot of good stochastic algos do :P
Kiitos. Käytämme tätä aikajanasi parantamiseen. KumoaKumoa
-
-
-
This is freakin’ great.
Kiitos. Käytämme tätä aikajanasi parantamiseen. KumoaKumoa
-
-
-
Great post. I find that it often comes with the C++ culture where needless complexity and obfuscation is reveled. The more screens of ridiculous template hacks you produce the more people applaud. Complexity is a liability, not a virtue.
-
Loss of ability to reason about your code base should be a warning signal to everyone. The default should always be under-engineering because you can add complexity later if required. The opposite is too costly and often not possible.
Keskustelun loppu
Uusi keskustelu -
Lataaminen näyttää kestävän hetken.
Twitter saattaa olla ruuhkautunut tai ongelma on muuten hetkellinen. Yritä uudelleen tai käy Twitterin tilasivulla saadaksesi lisätietoja.