HN user

crablar

271 karma

jeffmeyerson.com

Posts80
Comments33
View on HN
www.softwaredaily.com 6y ago

Materialize: Streaming SQL on Timely Data

crablar
4pts0
softwareengineeringdaily.com 6y ago

Scale with Alexandr Wang [audio]

crablar
1pts0
softwareengineeringdaily.com 6y ago

Leadership with Ben Horowitz [audio]

crablar
2pts0
dev.to 6y ago

Open Source Consumer Apps Are the Future

crablar
1pts0
dev.to 6y ago

3 Ways Software Entrepreneurship Is Like Poker

crablar
2pts0
dev.to 6y ago

GitHub: The Salesforce of Open Source

crablar
2pts0
softwareengineeringdaily.com 6y ago

Facebook Parse Acquisition (Part 1)

crablar
2pts0
softwareengineeringdaily.com 7y ago

Podsheets: Open-Source Podcasting

crablar
1pts0
findcollabs.com 7y ago

The FindCollabs $5k Hackathon

crablar
1pts0
findcollabs.com 7y ago

Show HN: FindCollabs: Find Collaborators. Build Projects.

crablar
1pts0
softwareengineeringdaily.com 7y ago

Engineering Philosophy with Tyler Cowen

crablar
1pts0
softwareengineeringdaily.com 7y ago

Scaling Hashicorp with Armon Dadgar and Mitchell Hashimoto

crablar
2pts0
blog.aboutamazon.com 7y ago

Amazon Scout

crablar
3pts1
softwareengineeringdaily.com 7y ago

Software Chasms with Martin Casado

crablar
2pts0
softwareengineeringdaily.com 7y ago

Why Is Storage on Kubernetes So Hard?

crablar
1pts0
medium.com 7y ago

Writing Music with On-Demand Musicians

crablar
1pts0
softwareengineeringdaily.com 7y ago

Dave Patterson on Computer Architecture

crablar
3pts0
softwareengineeringdaily.com 7y ago

Why Airbnb Is Moving Off React Native

crablar
6pts0
softwareengineeringdaily.com 7y ago

Edge Computing and the Future of the Cloud

crablar
2pts0
softwareengineeringdaily.com 7y ago

[podcast] React Native at Airbnb

crablar
1pts0
softwareengineeringdaily.com 8y ago

Interview with Alphabet Chairman John Hennessy

crablar
1pts0
softwareengineeringdaily.com 8y ago

OpenAI: Compute and Safety

crablar
2pts0
softwareengineeringdaily.com 8y ago

Autonomy with Frank Chen

crablar
2pts0
www.softwaredaily.com 8y ago

The Gravity of Kubernetes

crablar
3pts0
www.softwaredaily.com 8y ago

Justin Kan: Legal Technology

crablar
1pts0
softwareengineeringdaily.com 9y ago

Computer Logic with Chris Dixon

crablar
1pts0
softwareengineeringdaily.com 9y ago

Google Early Days

crablar
1pts0
softwareengineeringdaily.com 9y ago

Off-Grid Social Network [podcast]

crablar
2pts0
softwareengineeringdaily.com 9y ago

Uber's Postgres Problems

crablar
1pts0
medium.com 9y ago

You Are Not a Commodity

crablar
2pts0

Bluffing was important to the extent that I had to convince the listener that I understood the topics being discussed when I did not.

In general, I would discourage bluffing in a business like SE Daily. I'm on display for 250 minutes per week. It would be very easy to get caught in a lie.

This is Jeff from SE Daily. Thank you so much for these comments.

I did try to address the downsides as best I could and I think they are even better addressed in the follow-up with Preethi.

Most of the downsides of leaving your job are not instability because for most people in tech, that instability can be stabilized with stuff like debt, contract work, living in super cheap housing etc.

The main reason people do not go out on their own is either:

-lack of recognizing there are alternatives to the corporate meatgrinder

-laziness and addiction to video games, drugs, or other consumptive behaviors

-shame/defeatist/nihilist attitude

The epidemic scale of all three of these in tech industry is pretty disgusting--all the more reason to jump ship.

If you are unhappy as a programmer you should quit your job immediately and try sales/marketing/anything else.

I was disappointed with the way companies I worked at organized their programmers so I started Software Engineering Daily, a podcast about software.

This economy rewards software skills and general acumen as much as programming.

I was thinking it is a catchy name.

You are turning a casino into a nexus for mechanical turks. What is complicated about it?

It's also not meant to be offensive, if anything it is a compliment to Turkish people. They are good at solving problems with no definitive solution.

The bets are contrived for sure, but that was for the purpose of simplicity.

I believe the LinkedIn profile betting example is something feasible in the future, that we can't imagine very well by today's mores.

Example: you have a minimum-sized team that can work on that Trello board. One person for each column. After putting 20 songs through the assembly line, you find that things are getting bottlenecked at the percussion engineering part, and you are missing deadlines. So you hire another percussion engineer.

It's like a service-oriented architecture. If there is a lot of demand on a service, you spin up another copy of it.

I've written an album that's on Spotify, and several hundred other songs. I've probably put 3000-5000 hours into writing and thinking about music.

I'm continually proud and disappointed with my own results. I know I could do more if I was working with a team.

Passing an entire song between phases is only one model. Within that model, the spec I prefer is: whoever is receiving the song gets to choose what format he receives it in. Lots of small files, one big wav, whatever.

I have heard good things about Splice, which allows git-like collaboration.

What I want to underscore: there are great tools for individual and small-group creativity. I'm interested in processes for a large team that allows asynchronicity and scalable development.

As in many industries, we settle for the best music we have. I posit that our music would be better if it were written with some engineering principles.

Yes there are many good engineer+musicians. But I've never seen a group of musicians use a KANBAN board.