project-guidelines VS Lobsters

Code is read more frequently than it is written. This is especially true at Grab, where the team size is large and we have multiple engineers working across multiple projects. We highly value readability, maintainability and stability of the code and there are a few ways to achieve that: "Extensive testing", "Consistent coding style" and "Typechecking". Also when you are in a team, sharing same practices becomes really important. Check out these JavaScript Project Guidelines for instance.

JS Project Guidelines : A set of best practices for JavaScript projects.

var req2 = http.GetStringAsync("https://lobste.rs");

"I actually wish we had a hacker community like this without the business/startup side at all"

Sounds like you want https://lobste.rs

Well, there's https://lobste.rs/, or we could all go back to slashdot I guess

Requesting https://github.com/lobsters/lobsters as I'm going through that codebase and would be able to provide feedback. cheers

ps. just gonna second everyone else who's saying being able to edit out incorrect data is very important, otherwise people are gonna be weary of reading repos they aren't already familiar with.

> Hacker News, but also lobster.rs

First time I hear about it. I think you meant https://lobste.rs