Rambles

This is a term I've just coined, for my personal projects. It's a good way to see if something is worth doing or not. An MSP is the minimum you need to accomplish, to get the project to a state where even if it plateaus and never grows beyond that, you're pretty happy about the result and are willing to leave it running forever. Link to LinkedIn post: https://www.linkedin.com/posts/mngrwl_minimum-successful-product-i-like-to-think-activity-6687924119507492864-DHHI Actually, copying the original post here in case LinkedIn shuts down 10 years later and nobody can find it anymore: MSP is the minimum I would have to build and accomplish,…

This is a new project/business idea about teaching non-technical people about modern computing technologies in a rapid fashion without learning to code, to build systems thinking and technical fluency which is way more valuable than writing your first 5000 lines of code. Discussions: Dan Frysinger, Derek Pankaew, Vardhan User Interviews/Advice: Lee Hansen, John Brandes, Garrett Gibbs, Sampath Mallidi Notes Lee: Large teams already have dedicated teams to train employees immersively. But small/mid-sized teams could definitely use something like this.The Challenger Sale was quite popular, and its authors created their own practice, selling seminars and training.Sales people aren't the only people…

So I had an idea about how a tool that would allow people to easily record voice versions of their Medium articles, and automatically did the noise removal and balancing etc for them using machine learning. I imagined that most people don't really want to spend all their time doing audio editing, which is why a lot of online articles don't have any audio versions on them. I also imagined that a lot of people would enjoy turning their blog posts into "podcast"-like episodes, but are deterred by all the technical mayhem involved. I feel like recording and hitting "publish"…

Using this post to think through all assumptions, strategy and technical decisions made so far about DenseLayers. Deploy date is tomorrow. Today is 01May2020, and DenseLayers is ready to release minus a few last-minute changes that I keep making. I am in a state where I keep adding one more feature to make it easy to maintain the website once it is out, so that I can focus exclusively on content creation and marketing for the next several weeks. It is classic scope creep. But in the midst of all the excitement, I need to recollect my thoughts and ideas…

  The first version of DenseLayers is very close to completion (it's past the deadline of Dec 31, which makes me disappointed but at the same time I'm glad I'm making a lot of progress and doing it right. Need to decide what kind of metrics I should be monitoring as the founder, during the crucial initial stage. Using this post to think out loud from first principles and put my ideas on paper, hoping it will help me make sense. What I want to accomplish I want to grow the website into a product that people enjoy using, and…

This is a post in which I explore what would be the best way to explain my current database schema for DenseLayers (my current project) in a clear and concise manner - which I will do in another post. This means that this is a rambling post about how I should write that future post. Writing great documentation (whether for yourself or others) is a skill and it should be practiced thoughtfully. I want to compare different ways of organizing/structuring the ideas on paper so that they make the most sense. Update: I realize other readers may not know what…