jonhmchan

What I Need to Hear That I Don't Want to Hear

SO dev here. Not sure your size, but your first 10 users are much cheaper. On signup, it starts at $10/month and includes the first 10 users. It's $5/user/mo after that.

If you're much larger than 10 - creeping into the 200+ people, it might be better to go with Enterprise: https://stackoverflow.com/enterprise

I'm curious what you think about remote work and whether it's overall a net positive for companies that are struggling to find talent in their own country.

There seem to be some obvious benefits: no need to worry about getting people visas, expanding your talent pool to beyond your geographic region, and so on. There's also legal tradeoffs: dealing with complicated laws with taxes, benefits, and so on.

In your experience, is opting for remote a net benefit? Or perhaps more fittingly, in what situations do you think it's appropriate for a company to consider building a remote workforce, wholly or partially?

Stack Overflow does. I'm an engineer there and we still think providing private offices to our engineering team is important for their productivity. This includes engineers, SREs, designers, data scientists, PMs, and others.

However, most of our engineering team is remote and if they're not in one of our locations, we give them pretty much what they'd like to build their own home office or go to a coworking space.

For me, I'm actually nomadic, so I tend to work from wherever I'm staying or end up in cafes a lot of time. I still get the support I need if my work "station" isn't optimal.

TL;DR Stack Overflow provides private offices, but is really flexible, especially given its remote policy.

Work at Stack here. We still provide private offices for developers when they're in one of our offices. A lot of the engineering team is remote too, which lets people have their own workspace as well.

I wake up earlier. Both the meditation and pledge to write take up an extra hour in my day. It's causing me to readjust my old habits too: if I don't sleep late and get a good night's sleep, waking up earlier is easier and I can make the time.

I'm curious to see how this evolves in future weeks.

I absolutely love this idea - it solves for a HUGE pain point that entrepreneurs have dealing with the logistical, legal, and financial groundwork for a startup and getting to payments easily. Good lord, if Atlas were around for me to setup my startup, I would be crying tears of joy.

What I'm confused about is why they didn't focus more on the convenience advantages and positioned Atlas as a non-geo tied incorporation/setup offer. As many people have noted, the advantages of doing business as a U.S. company if you're not in the U.S. is unclear. It seems far more appropriate as a side note to the much needed advantages of solving a legal, financial, and accounting nightmare just to get payments. Why emphasize international?

I know I'm walking right into the fire with this one.

Take a look at Bento. https://www.bento.io/

https://www.bento.io/tracks/front-end - front end track

https://www.bento.io/grid/ - all their tutorial recommendations

They hand-pick some of the best free tutorials for each of the technologies you might need (including the other ones mentioned here) and even have curated tracks for front end.

Some differences. Generally, it's been ported over to the main Stack Overflow site with Q&A now.

Discourse was really, really close for us. The breaker was the lack of a real WordPress import support: https://meta.discourse.org/t/is-it-possibile-to-import-exist...

That being said, that evaluation was done before we found out how difficult it would be with Disqus.

Someone else also mentioned prose.io - something I didn't come across when building this. Going to explore.

Our problems actually weren't with Jekyll. Like I mention in the post, much of the functionality came right out of the box. The major pain here was exporting and combing through the data afterwards, and that required some Python to parse comments and convert to markdown. Once we did, that meant less security holes, opening up our content and technology more, among other pluses.

I'm the author of the post and the lead on this project. Many of the costs you mention aren't so bad. As mentioned earlier, we actually consider learning GH and Markdown a plus for non-devs. As for comments and writing Python, some pain here, but were ultimately solvable.

Performance also wasn't the only plus here. Closing major security holes, making more of our content and technology more open, and moving to a platform that our devs liked working in are just some of the other wins.

It's too early to say definitively now, but we think the change is probably a good one.