I'm wondering if anyone on HN has recommendations for learning more about software systems architecture, distributed systems, scalability, etc., mainly with regard to internet/web systems or web applications? E.g. a book that might have a chapter on queue design patterns, when and why to use them, or a chapter on notification architectures, caching concepts, etc. Not just "this is what ___...
The main use case is for more focused discussions / information sharing. It started as a threaded chat app but evolved over time. I used the GitHub Issues analogy because you could use the app to make a customized generic version of a GitHub-issues-like bug tracker.
For that analogy, you can think of each board in ThinkBase as a repository of issues, while the cards are like issues.
Each board that you create in ThinkBase can have its own "card template" to focus the cards/conversations on that board, just like GitHub Issues has templates.
When it comes to tracking the status of your cards, you can create your own tags like status:open, priority:10, asignee:mike, and then perform queries on these custom tags (e.g.: segment engine status:open priority>1) to segment the cards to your liking.
The main power (I hope) of the app is that you can focus each board on whatever type of discussion or information sharing use case that you'd like depending on how you craft your templates and tags. Boards don't have to be "issues" focused but they could be.
To be honest, at this point in time I'm still refining the different possible use cases. Perhaps there is a better analogy to use. Once I'm able to hone in on one or a couple solid use cases I'd like to build out more features to better support them.
You bring up a great point about columns. I've been thinking lately of a feature that would allow you to choose which tags you want to use as your columns if you prefer a column view. So for the GitHub Issues analogy, you would create the tags - status:TODO, status:doing, status:done, and designate those as your "columns".
Appreciate the feedback.
That thought inspired me to build this app with features that encourage focused work, efficiency and modularity.
I just opened up free registration for the public today so that I can gather some more feedback. Let me know what you think!
Also, I think that the probability of this happening is possibly lower than you think, as it assumes that your posting is wildly popular AND popular enough that someone at a big tech co. thinks it's worth building AND that person is convincing enough to convince his team to build your product AND they're able to move as fast as you're saying AND they execute well enough AND there is not room enough for more than one co. in the market you're after.
Even if you do manage to keep things a secret and choose a different path, who is to say that the alternative path doesn't somehow end up exposing you even more due to the large number of unknowns that you'll encounter as a founder?
You may even be able to move faster than Zoom as a solo dev depending on the circumstances. In the long run, I really don't think that a posting to HN will destroy a co. Most of the time it will be something else like lack of motivation, time, resources, etc.
This is one of the larger apps that I've shipped on my own. I'd love to see if anyone would like to beta-test it or chat about related matters (email in profile).I was inspired to build this because of past frustrations with remote communications (inefficiency, messy organization, etc.). I spent a lot of time thinking about what made some of those communications successful (or not), what...
I would love to know what people think of this idea. Here is the hypothesis/pain point:ML and more broadly data science are very useful, but even some of the most recent "easy" data science tools (e.g. Google AutoML tables) have too high of a learning curve to be useful to the average consumer.Normally if you were learning a new tool, you might learn through a combination of study, and trial...