#twtcc

HAHAHAHAHA OMG. i’m so glad you appreciated that skshsksjsk it seriously means so much to me. 🥺🥺🥺 and the brackets really scream kags to me ngl

Y/N do be acting kinda odd 😳😳😳😳 BUT THANK U SM I LOVE U!!!!

dang y’all are SMART smart huh 👀👀👀👀 i’m glad you’re excited hehe ♡

The problem, is not always simple. It is so huge that often, your digestion system runs faster than needed. But he's been here before... He got passed it. He thinks... "how did I do it last time!". Soon he realizes, he just broke down the problem to the smallest units of problems last time. It has worked. So he goes about it. Now he's got more problems than he started with! he thinks... "At least, they are tacklable"...

That's the way the cookie crumbles - 1 He starts with how to find the best suited solution to a problem. A design pattern. He realises, it is not the architecture. Things change. Its the problem stupid! Htakes some time off, to note down the "stuff" associated with the problem. "Hmmmm..." then he thinks... "these things need a model of some kind".... and then he designs an clear model of the things involved in the problem. It was a long time since he realized, people are lazy. Lazy to adapt too. Given a solution to a problem, if its' stuff needs adapting, it is unlikely to be useful. He says, "I will make a concrete model of stuff based on the problem". Out of a zillion solutions, the easiest path is the one chosen. Easiest for the problem. Not for the architect. Now the entities involved in the problem are modelled. Their interaction with the core system is designed. A lazy way. Now that the baby monsters are dealt with, he can meet the monster mommy. The problem.