reledi

Check out the Toby extension: https://www.gettoby.com

Agreed, I completely missed the server name field. Scanned over it thinking it was a horizontal line with a label below and didn't bother to read it.

Thanks for clearing that up, it's exactly the same for me. I find technical mock interviews help.

As an Atom user, I gotta say this looks like a solid release and I'm excited to give VS Code another try. Well done!

The content on the page does a very poor job of explaining what it is and why we should care. It's only until I saw the KDE developers at the bottom that I realised it's a graphical desktop environment but for your mobile phone. It's FOSS so it's hackable, as in you have access to the source code and development is done in the open and contributions are encouraged. The target developer phone seems to be the LG Nexus 5. I guess it's running some Debian-based OS as apt-get is its package manager.

FYI There's recent evidence that the fire didn't start on Pudding Lane: http://www.telegraph.co.uk/news/uknews/12109005/great-fire-o...

Thanks for sharing that blog post. I just started a sabbatical, and it was encouraging to read about yours. I'm thinking of going to graduate school on my return since I left for the industry right after my bachelor's.

Would enjoy reading an update of your journey to see how your next sabbatical goes.

Do you have a link?

These people may not have access to the document, but surely in a small company they would figure out some of the salaries either through the grapevine or shoulder surfing?

I don't have an iPhone to try it out, so a few questions.

1. Do you need to "log in" to use it? Or can it be used without an account?

2. Can you have hidden/secret conversations? That is, the conversation isn't easily observable by everyone within 1km?

- Have you experimented with painters from areas other than China?

- What's the onboarding process like for a painter?

- I read on the reddit soft-launch post that one way the business handled scaling was by printing out the photos and then painting over them. Did it turn out to be a successful strategy?

> people who disagree with me [...] aren't doing so out of spite, stupidity, or carelessness, they often just have different priorities than I do

This is an interesting perspective that I'd like to try. Thanks for sharing.

The post got one critical detail wrong. The microservices won't have their own API. APIs are dead. They'll use Kafka for messaging. That's the future.

I've been using this handy Chrome extension for years. It places the collapse button in front of the username.

https://github.com/andrewheins/HN-Comment-Hider

I used to do this but endlessly pruning distractions itself became an unwanted distraction. My current approach is to do nothing and only act on important notifications/emails. It's not Inbox Zero, it's Inbox Zero Fucks Given.

There's a lot of talented Spaniards out there. I know because I can proudly say many of them are my teammates.

Did I mention we are hiring? Clojure, Ruby, Data.

https://www.fundingcircle.com/uk/careers/

Excited to see a platform that doesn't charge fees to tenants. The rental industry in the UK, and especially London, is ripe for disruption. No fees is a good first step. Another example, one search criteria that many renters will not compromise on is shared housing, yet many (all?) platforms do not offer this search filter.

Gotta admit the salary range for the lead engineer position is worrying. You won't find anyone worth their salt for such an important role in an early stage company starting at £30k.

Doesn't feel like it for me.

They can and they do. The onus is on the passenger to report issues such as indirect routes.

It's worrying that something as harmless as this comes across as a stunt with some ulterior motive. Not everything is a viral marketing campaign.

I don't think antoncohen meant searching file contents, but point taken.

I've been thinking about this lately and my thoughts resonate with yours. My situation has amplified since moving to London a little over a year ago, where I had no friends or family. I've been wanting to go back to a simpler style of friendships like when we were younger.

At the same time I've also missed sports. My solution was to get back into skateboarding. I haven't skated in ten years but you'd be surprised by your muscle memory. I got all the gear and headed to the nearest skatepark and was quickly approached by the local skaters. I met a lot of great people and skated with them all evening. Haven't had so much fun in a while. Can't wait to go back.

There's also a third reason. It can be illegal without consent of those involved (e.g. lecturer, students, university). To comply with the law, you would have to clear rights such as copyright, performer's rights, moral rights, and privacy rights before any recording takes place.

Commits to squash can start with [squash] and when you rebase they are automatically squashed.

> Upgrade everything, all the time

This is dangerous advice. There's some good advice underneath. Updating often addresses pain points iteratively and is easier than doing major upgrades every year, for example.

But you should not be blindly updating your dependencies every week. It's a distraction and some updates require dev time to fix things (hopefully your integration tests catch some of these).

It's also dangerous if you update all without looking at changelogs. Maybe the new version of one dependency brings in ten new dependencies, or maybe it brings in security vulnerabilities, or maybe it's a completely different codebase or package was removed like what happened with the recent npm fiasco.

What does type A mean?

Every line of code added needs to be maintained and makes adding future code more difficult. As our job is to build software, we are too eager to increase technical debt without knowing it. Always ask "how can we avoid building it?"

When you realize it really does need to be built and it is the highest priority, think about how it can be built while keeping cruft down. You can still be fast while keeping the codebase clean but it requires constant refactoring and review and a common understanding between team members.

You should have posted your comment after the second paragraph.

> But it doesn't make sense for the original repo to be the only repo which can ever be canonical.

This is a red herring. The problem that's a lot easier to solve and will benefit the community just as much is better discovery of useful forks.

The current interface that GitHub gives for discovering forks is awful when it comes to this.

P.S. Those two diagrams do a poor job of explaining the problem, they're the same diagram.

Regarding the customer references, I'm always highly suspicious of anonymous praise. Do you not have permission from the authors or companies to use their name?