HN user

ScotterC

2,038 karma

Building something new Blog: http://www.scottcarleton.com/ Twitter: @ScotterC or http://www.twitter.com/ScotterC

Posts78
Comments329
View on HN
honeyryderchuck.gitlab.io 2y ago

The state of HTTP clients, or why you should use httpx

ScotterC
24pts4
www.washingtonpost.com 3y ago

AI chatbots won’t enjoy tech’s legal shield, Section 230 authors say

ScotterC
5pts1
www.economist.com 4y ago

When Vladimir Putin escalates his war, the world must meet him

ScotterC
17pts6
tomtunguz.com 5y ago

The Productivity Implications of Working from Home Across 150k Employees

ScotterC
2pts0
techcrunch.com 6y ago

Asana launches Workload to help prevent burnout

ScotterC
2pts0
techcrunch.com 7y ago

Asana raises $50M at a $1.5B valuation

ScotterC
165pts130
scottcarleton.com 7y ago

Principles: Great Work ∞ Great Learning Part 3

ScotterC
1pts0
scottcarleton.com 8y ago

Principles: Great Work ∞ Great Learning

ScotterC
2pts0
medium.com 8y ago

Software Engineering is different from Programming

ScotterC
17pts11
www.nytimes.com 8y ago

Startup Bets on Tech Talent Pipeline from Africa

ScotterC
2pts0
medium.com 9y ago

People Analytics: How we accelerated our senior developer hiring by 233%

ScotterC
2pts0
medium.com 9y ago

Artsicle, Exit Stage Left

ScotterC
2pts0
railscasts.com 9y ago

RailsCasts Pro episodes are now free

ScotterC
4pts1
www.linkedin.com 9y ago

Developing People in a Distributed Environment

ScotterC
7pts0
medium.com 9y ago

An Engineering Manager’s Guide to the Future of Work

ScotterC
12pts0
algorithms-tour.stitchfix.com 9y ago

Algorithms Tour

ScotterC
2pts0
andela.com 9y ago

What an Engineer looks like

ScotterC
1pts0
www.facebook.com 9y ago

Dissecting a Case of Imposter Syndrome

ScotterC
5pts0
medium.com 9y ago

Meet Tobi, our Nigerian head of development

ScotterC
3pts0
medium.com 9y ago

Introducing myself has never been this hard

ScotterC
2pts0
ronjeffries.com 9y ago

Refactoring – Not on the backlog

ScotterC
1pts0
scottcarleton.com 9y ago

Hackathon Trials and Tribulations

ScotterC
3pts0
lgtm.co 10y ago

Simple Approvals for Pull Requests

ScotterC
1pts2
medium.com 10y ago

The software engineer’s guide to asserting dominance in the workplace

ScotterC
6pts0
medium.com 10y ago

I can has redemption

ScotterC
1pts0
engineering.teacherspayteachers.com 10y ago

From 10 Hours to 10 Minutes: Scaling Release Automation at TeachersPayTeachers

ScotterC
8pts0
www.edsurge.com 10y ago

How Teachers Pay Teachers Is Recruiting Top-Notch Tech Talent

ScotterC
7pts0
github.com 10y ago

Kemal: Super Fast Sinatra Like Framework Written in Crystal

ScotterC
2pts0
www.newyorker.com 10y ago

All Scientists Should Be Militant Atheists

ScotterC
8pts8
medium.com 11y ago

What Etsy’s S1 Filing Taught Me About Marketplaces

ScotterC
1pts0

My kids are at a Waldorf school currently. I would not be surprised by your experience from what I’ve learned. However I’ve also seen a truly incredible environment at my school and zero cult adherence to Steiner. My best explanation is that each Waldorf school is very much its own island - it seems to be a very federated system.

AI is different 11 months ago

I’m surprised that I don’t hear this mentioned more often. Not even in a Eng leadership format of taking accountability for your AI’s pull requests. But it’s absolutely true. Capitalism runs on accountability and trust and we are clearly not going to trust a service that doesn’t have a human responsible at the helm.

Agreed.

Regarding some of the ‘layered architecture’ discussion from the OP, I’d argue that having many modules that are clearly defined is not as large a detriment to cognitive load when an LLM is interpreting it. This is dependent on two factors, each module being clearly defined enough that you can be confident the problem lies within the interactions between modules/components and not within them AND sharing proper/sufficient context with an LLM so that it is focused on the interactions between components so that it doesn’t try to force fit a solution into one of them or miss the problem space entirely.

The latter is a constant nagging issue but the former is completely doable (types and unit testing helps) but flies in the face of the mo’ files, mo’ problems issue that creates higher cognitive loads for humans.

Looks like a solid post with solid learnings. Apologies for hijacking the thread but I’d really love to have a discussion on how these heuristics of software development change with the likes of Cursor/LLM cyborg coding in the mix.

I’ve done an extensive amount of LLM assisted coding and our heuristics need to change. Synthesis of a design still needs to be low cognitive load - e.g. how data flows between multiple modules - because you need to be able to verify the actual system or that the LLM suggestion matches the intended mental model. However, striving for simplicity inside a method/function matters way less. It’s relatively easy to verify that an LLM generated unit test is working as intended and the complexity of the code within the function doesn’t matter if its scope is sufficiently narrow.

IMO identifying the line between locations where “low cognitive load required” vs “low cognitive load is unnecessary” changes the game of software development and is not often discussed.

Many would be quick to argue that they are interlinked but I strongly agree with you - particularly in the context of this thread.

For me, optimism still provides a lot of value in my worldview. The beliefs that have changed the most for me in the last 25 years is the limits and boundaries of what tools can do for us.

Technology ‘fixing humanity’ (when that ‘fixing’ is based on your own personal value system) is certainly a fools errand. But that limitation shouldn’t get in the way of imagining a utopia which is worth having.

Sure, I miss my childhood feelings of the 90s. But I also never expected a techno utopia to be ‘easy’.

hey this is awesome. I'm using it and I think it's got some wheels. But please add a quick link to submit feedback in app! Here's what I got so far: - specific issue: I updated the triage text before submitting to the planning stage. Although the triage text maintained my edits I'm pretty sure the prompt that went into the first Plan generation did not include my edits. - rough idea: Plans are long and take awhile to regenerate. There's fear of submitting for a regeneration when all you want is it to understand something different about the high level thoughts. Maybe keeping a history of plans or even diffing them could be useful.

Both items above coalesce into a desire to 'rewind' back to the top of the process and try to get the context understood at the beginning, and have that clearly reflected to the user so that as you move through to details it gets easier to handle the nitty gritty without as much editing.

Ant Geopolitics 2 years ago

Re: Ecology in Scifi

The interactions between Ants and Spiders gave me some associations with Butler's Xenogenesis trilogy (aka Lilith's Brood). Particularly, I loved how both were painting an alternative evolutionary path but 'grafting on' to existing notions and understandings of what we know to be true in species development. I wish there was more of this! I felt Children of Ruin was weaker in this regard, maybe because the conflict for the species was absent. The Spiders vs Ants and then Spiders vs Humans being conflicts which created a fanstatic narrative to explain alternative solutions to prisoner's dilemma (spiders choosing to co-opt their enemies' strengths or in Lilith's brood, Oankali being a hybrid of alien/human). I'd be curious to learn if there's more examples in zoology/ecology of species choosing this route instead of competition every time - and also, what factors might impact this.

I could have written this same comment. I fully understand where the mental irrationality comes from. I’ve done therapy etc. But what I call “the hearth of the city” means it’s hard to ever really relax. Caring for a family accelerated it.

I imagine what I’m missing most is how he handles those huge obstacles. We all can turn on sheer force of will for a set amount of time but keeping it buoyant in the face of huge obstacles is another matter entirely.

I’ve talked to Sam once a long time ago which gives me a rudimentary answer to your curiosity. PG’s notes on Sam in that 2009 essay ring true to me (http://www.paulgraham.com/5founders.html).

there are a few people with such force of will that they're going to get whatever they want.

We discussed nuclear power which was an industry I left but dreamed of building a successful startup in. Sam asked me why I wasn’t building a startup in nuclear power if I thought the technology was so powerful. What I realized in what he was conveying was that if he had the same conviction he would have no doubt about the ability to drive it to success. The more experienced I get the more I value that type of conviction and determination. The more I also see that behavior being rewarded with results.

Have my first child, now 7 months old. If I could only say one thing it's make sure to have a trusting & productive relationship with your partner. Problems or going to come up every day and solving for them is a function of how well you two collaborate.

I had the benefit of co-founding a startup with my partner so we had already cut our teeth on this. A child is like a type of startup. Identifying and managing problems/complexity is a daily activity. If you have a good working relationship there than you can have a blast being parents together.

Asana (asana.com) | New York, NY | Software Engineer | Full-time | Onsite | Visa

Asana's mission is to enable all teams to collaborate effortlessly. We're taking on the work management space and I have a fundamental belief that technology can help us all self-organize more efficiently and in return allow us to work more in our genius, achieving a state of flow more often. Asana delivers on this with our product and our culture.

We're looking for Engineers who are passionate about creating a phenomenal culture that enables autonomy and responsibility while striving to building the best product possible because that's what we compete on.

Our tech stack: Typescript / React and our own version of GraphQL (we built it before GraphQL was open sourced). Our version of GraphQL executes all queries as "live" by default. This means you do not need to worry about data changes when designing a feature.

I joined because I was convinced that the incredible collaboration experiences I had in a small startup could be scaled up to big companies. Come work with us https://asana.com/jobs/apply/1163890/product-engineer

Asana (asana.com) | New York, NY | Software Engineer | Full-time | Onsite | Visa

Asana's mission is to enable all teams to collaborate effortlessly. We're taking on the work management space and I have a fundamental belief that technology can help us all self-organize more efficiently and in return allow us to work more in our genius, achieving a state of flow more often. Asana delivers on this with our product and our culture.

We're looking for Engineers who are passionate about creating a phenomenal culture that enables autonomy and responsibility while striving to building the best product possible because that's what we compete on.

Our tech stack: Typescript / React and our own version of GraphQL (we built it before GraphQL was open sourced). Our version of GraphQL executes all queries as "live" by default. This means you do not need to worry about data changes when designing a feature.

I joined because I was convinced that the incredible collaboration experiences I had in a small startup could be scaled up to big companies. Come work with us https://asana.com/jobs/apply/1163890/product-engineer

Asana (asana.com) | New York, NY | Software Engineer | Full-time | Onsite | Visa

Asana's mission is to enable all teams to collaborate effortlessly. We're taking on the work management space and I have a fundamental belief that technology can help us all self-organize more efficiently and in return allow us to work more in our genius, achieving a state of flow more often. Asana delivers on this with our product and our culture.

We're looking for Engineers who are passionate about creating a phenomenal culture that enables autonomy and responsibility while striving to building the best product possible because that's what we compete on.

Our tech stack: Typescript / React and our own version of GraphQL (we built it before GraphQL was open sourced). Our version of GraphQL executes all queries as "live" by default. This means you do not need to worry about data changes when designing a feature.

I joined because I was convinced that the incredible collaboration experiences I had in a small startup could be scaled up to big companies. Come work with me https://asana.com/jobs/apply/1163890/product-engineer

You're absolutely right. A mindset needs to accompany any tool in order for it to be successful - or direct relationship to how successful

There's a great book on this topic from the first dot com age. Necessary but not Sufficient (https://www.amazon.com/Necessary-But-Sufficient-Eliyahu-Gold...). The idea being you can adopt a tool but if you don't understand the mental models that go along with that tool then you won't fully reap the benefits.

As a company, this is still our responsibility. The best products educate as well as enable.

Not worried at all. Our value of transparency internally extends to this raise as well.

Yes employees have equity packages and we're well informed of what the terms of this raise are, the dilution and our leadership team has worked hard to get employee-friendly terms. We believe in this because our team members are the main function for Asana to grow and hit these expectations so it must be a trusting and win-win partnership in order for it to last.

I work at Asana - Site Lead for NYC

What I find most fascinating about this company is that something that sounds relatively unsexy - work management for enterprise - can be so well aligned with a truly unique mission. Enabling teams to collaborate effortlessly. For anyone who's worked at a dysfunctional company - politics, low morale, low transparency - it makes a huge difference when you have tools that help you collaborate and get on the same page.