Knights* rip, too excited to type carefully 😭

This guy gets it 😤🙌

Rip I meant *pet* the cat

Can you oet the cat??

The 2D elements are super cleanly integrated in the 3D space with this. Absolutely love just looking at it

Oh shit this looks cute 👀

If you're rushing something out the door, you're way past the "make it exist" point, period. It's just supposed to be encouragement to go out and prototype your idea. As I said, using it as an excuse to write bad code and push problems down the road is a quick way of gathering tech debt.

Now, if you're using that phrase as an excuse to write terrible code and constantly push refactoring down the road for the entire project, then you're vastly misusing the phrase and causing yourself a heaping load of technical debt that will lead no where good. 5/5

If you have a cool idea, prototype it. Make it terribly. Focus on getting the idea out and seeing if it's as cool as you thought. Don't waste time writing fully designed systems for something you might decide sucks. If you like the idea? *Then* come back, break it all down, and make it properly. 4/5

Being at a point where you know the outline, design, systems, etc. of your final project generally comes *after* the prototyping stage, which is what the "make it exist first" phrase is, by my understanding, supposed to be referring to. 3/5

Inherently I would agree with your statement in regards to code if you already know what your project should look and feel like, and you know that systems you're building now will need to be expanded later. That's not the point of the phrase, in my opinion. 2/5

I apologize, "getting it right" was me generalizing your statement, not me trying to quote it directly. I'll use real quotes here. The implication with "making it good in the first place" is that you should just *get it right* from the start, so as to not have to "make it good later". 1/5

I'm a firm believer that you've gotta learn how to make it terribly before you can figure out how to make it properly. If development was as simple as "getting it right" the first time, it wouldn't be so hard to make things and QA would be an irrelevant job field.