I'm a little late to this thread, but I agree with others; the 'meet' tab would be an incredible addition to HN. Perhaps it could include features like location-based topic filters or even a 'looking to meet' tag where users can express interest in meeting others with similar interests. To keep things safe and inclusive, maybe we could have a 'verified meetup' system where members can host and vet events before they’re posted. I'll shut up before my brain dumps all my thoughts here.
On a related note, for any HNers (or hackers) in/around Austin, TX that want to meet, I'd be happy to help organize a meetup in Austin, if you're interested in connecting.
That's such an inspiring story! It's amazing how serendipitous connections can lead to something amazing. I had a similar experience meeting my previous co-founder at an in-person event in Austin where I was presenting. There’s just something special about those chance encounters, whether online or offline. I've also met a few incredible folks here on HN discussions in my city. It's one of the things I truly appreciate about this community—never know where the next great connection might come from.
The short answer is - there is no good answer. The best thing that worked for me was to just pick a popular stack that can help me achieve specific some goal. And, possibly one with wide adoption and a thriving community and ecosystem, especially if you are looking for career prospects.
Spend a little bit of time with a couple of stacks to understand what you feel comfortable with.
When I was looking to transition from legacy technologies (think mainframes) while working at an established financial company, I had an itch to build a specific product on the side. To be able to build it, I had the option to choose any modern stack at that time (around 2012), and I chose the Java-Spring-Jquery. I could have chosen any other similar stack for my purpose (PHP, C#, etc on the backend and plain JS or any other library on the front end) that were widely used and had big ecosystems. I tried to build some basic functional products with both Java and PHP based stacks, and decided to go with the Java-Spring stack. These days there are even more options, so it boils down to trying a few and settling on one that excites you.
This is interesting. I’m gonna try it out this week.
I wonder if you have plans to extend this to allow saving to S3 or GitHub or other types of document stores in the backend, in addition to Google Docs.
Yes I'm a CPA and was most recently director of finance at Stack Overflow. I've also done financial modeling consulting work over the years for many companies.
That's great. I recently started building something similar (although more rudimentary) for a community that I run in Austin. I'd love to connect and discuss more offline, if you're interested. What's a good way to reach you?
I second this. I try to replicate the UI/UX of the applications that I like (as a user of such apps). Obviously, it doesn't mean copying mindlessly, but using similar patterns/flows where it makes sense in my applications. Even though it's not a resource like a book, in a way, I'm learning from good real-world examples.
Mostly architecture diagrams, data flow diagrams, flow charts, sequence diagrams and ERD. Mostly they are used as an accompaniment for the brainstorming and design discussions and, in some cases, to serve as easy reference for future. We mostly use draw.io and Visio as the diagramming software in our teams.
We use story points in our SaaS product startup. In a larger company that I consult at, whose main business is not a software/technology product (but IT/software is a core enabler for their business), we tried story points, but eventually settled with hour-based estimates. I think the difference was in team sizes, nature of business and delivery timelines.
In the startup, we had a small team where everyone was aware of the agile processes, and the delivery timelines were based on the estimates.
In the larger org, agile processes and story points meant a change in the culture from the traditional waterfall-oriented process they followed. And larger team sizes meant it took a longer time to change the culture and thinking. Also, due to the nature of the business, the delivery timelines are stricter, and sometimes already decided before IT was involved. Projects also often involve multiple non-IT teams (sales, marketing, customer service, etc.), and it is easier to communicate in hour-based estimates to them. We still do agile development as much as possible, but settled on hour-based estimates.
Stackoverflow, Github and plain old Google search. One thing I like about Stackoverflow, Github gists and issues is the discussion around the code/problem/topic. With Github, I also get a chance to see how others solved the same problem in real-world projects, in possibly different ways, and in interesting projects I would not have come across otherwise.
Looks like a good high-level intro for a first-time founder. It would be good to have another section on some common legal policies (privacy policy, terms of service, etc.).
On a related note, for any HNers (or hackers) in/around Austin, TX that want to meet, I'd be happy to help organize a meetup in Austin, if you're interested in connecting.