I've been reading online for as long as there's been something to read online. But the experience keeps getting worse. Ads, popups, auto-playing videos, modals before you've read a single word.

Pocket was my solution for years. Then Pocket went away. So I built my own.

Pura Letra strips everything away and gives you just the writing. Clean typography, highlights, notes, a personal library. Free to use. Launching today.

This is awesome, thank you for sharing and for building it.

After many years of discouraging women and other underrepresented minorities in tech, those groups have a clear disadvantage and creating groups and other ways to help them catch up is what we need to balance things out.

You are right about one thing, this isn’t only a problem within tech, there are many other industries and careers where women and other underrepresented minorities haven’t been given a chance to succeed and show their capabilities. But it has to start somewhere and with tech being so important for everything we do in our lives everyday, it just makes sense to be louder about this in this community to pledge for a change.

Experts become experts after years of experience, coaching, support, and having people who approve of them and their knowledge all of the time. Women and minorities lack that support, like I said, we are just playing catch up now.

To me, the cons of working at a startup in SV are these:

- lower salary than bigger cos

- mostly smaller/less challenging projects

- low chances of ever liquidating RSUs and if you do, the value will more likely be low with some very rare exceptions

- it's harder (or impossible) to achieve a decent lifestyle living in SF/Bay area with a startup salary

- lack of diversity in most small startup teams

I do believe that the majority of coding will be replaced by AI or some automated process requiring some inputs and expected results to "code" an application. However, this article reads like an advertisement, and it fails to go deeper into the topic at hand, unfortunately.

A developer becomes a "great developer" when the company, team, resources, projects, recognition, etc., are compatible with that person. Under that logic, I believe any programmer can be great if they desire to do so and find the environment and motivation to thrive.

Most technical interviews fail to find the right people because interviewers and hiring managers usually go at it with an "idea" of what a "great developer" looks like to them. In most cases, everyone ends up hiring people who don't work out and miss out on people who could have become the "great developers" there were looking for in the first place.

I will second this because I've seen it happen, both to me and to other people -- an environment that wasn't a good fit changes and suddenly someone excels, or someone excels and the environment changes and suddenly it's like they can't do anything right.

Also, having clear criteria set up in advance is essential. You should know before you go into the room (or pick up the phone, or whatever) not only what constitutes a pass versus a fail, but also what kinds of things in the interview signal more than just passing. And the pass/fail can't just be "regurgitated an algorithm we wanted them to regurgitate", because that tells you nothing about whether somebody's actually good to work with.

I agree.

I have a strong belief that the best way to interview a candidate is to take a literal real world problem the team experienced, distill it down to its essence so it can be tackled in a 2-4 hour pairing session. You should have full access to internet, whiteboard, etc.

If the candidate is having to review CS algos and doing whiteboard prep, you're doing it wrong (unless that stuff truly is what the job entails). If the candidate is nervous because they feel like they're giving a dissertation, you're doing it wrong. It should mimic as closely as possible what the actual job will be like.

You're not going to fully know whether or not they will produce in practice, but you'll be able to tell that you can work with them and that's half the battle.

Maybe.

I would pay for a social network that can offer a simple UI, that works on any device (have you tried to use Instagram on an iPad Pro), and that can help me switch between private, anonymous, and public posts intermittently.

That's a shame.

Whatever the output, the Uber story will surely be an interesting startup/VC/capitalism case study in the near future.

Based on the description it looks like you'll be doing some programming and working closely with software engineers. If you don't have a lot of programming experience this could be a great way to learn and get your foot in the door.

Thanks, just wanted to know if this was worthwhile as opposed to a full-on software engineering internship.