Zmbnski's Categories

Zmbnski's Authors

Latest Saves

💪 And we're down to the last 48 hours until the biggest live-streamed startup event hosted by @thepatwalls & @shipstreams kicks off!

With this, let's get motivated with some curated readings & posts by fellow #24hrstartup participants & indie makers. Check them out below!

✍️ Andrew Parrish wrote - "Why I'm Participating in the 24 Hour Startup Challenge".

@makersup's takeaway - Makers love possibilities, the joy of building. Any aspiring maker should experience the end of lurking on forums & reading @wip's to-dos.

Read:

👩‍💻 @anthilemoon created a list of @women_make_ members participating in the #24hrstartup challenge. Do let her know if she missed anyone!

More at:
https://t.co/zYKVZEq8aq


😺 We can't forget one of the key platforms in shipping indie, can we, @ProductHunt?

Check out @ProductHunt's guide to launching at: https://t.co/VB6WgGx6sa.

In addition, it would be wise to prepare for the launch. Fine tune your assets and post at

🚢 Well, we definitely can't leave out the man behind all of this, @thepatwalls!

Launching isn't easy, but know what you'll be facing even before coding. Check out @thepatwalls' "words of shipping" at:
I think about this a lot, both in IT and civil infrastructure. It looks so trivial to “fix” from the outside. In fact, it is incredibly draining to do the entirely crushing work of real policy changes internally. It’s harder than drafting a blank page of how the world should be.


I’m at a sort of career crisis point. In my job before, three people could contain the entire complexity of a nation-wide company’s IT infrastructure in their head.

Once you move above that mark, it becomes exponentially, far and away beyond anything I dreamed, more difficult.

And I look at candidates and know-everything’s who think it’s all so easy. Or, people who think we could burn it down with no losses and start over.

God I wish I lived in that world of triviality. In moments, I find myself regretting leaving that place of self-directed autonomy.

For ten years I knew I could build something and see results that same day. Now I’m adjusting to building something in my mind in one day, and it taking a year to do the due-diligence and edge cases and documentation and familiarization and roll-out.

That’s the hard work. It’s not technical. It’s not becoming a rockstar to peers.
These people look at me and just see another self-important idiot in Security who thinks they understand the system others live. Who thinks “bad” designs were made for no reason.
Who wasn’t there.