342 karma · joined April 13, 2011
When our tools get so good that our employers don't need us, we won't need them. In a market where the engineers are competing with the manager class whose core skill is politics and bullshit, who would you bet on long term?
While job losses are a concern, I think the more significant impact will be on the way companies operate. As firms exist to economize on the cost of coordinating economic activity, the streamlining and reduction of coordination needs brought about by LLMs will challenge the very foundations of many businesses. In this new landscape, individuals and small teams might outcompete larger organizations.
Freelancers and solo entrepreneurs could find themselves better positioned to compete in the market, driving the rise of smaller, agile businesses that can innovate rapidly and cater to niche markets. This shift will also change the skills needed for success in the field.
Overall, it's an exciting time to be part of this industry. Far from being a time to quit, it's an opportunity to adapt, grow, and harness the power of LLMs to reshape the world of work.
One transformation will come when a single developer can do the work of a team of ten today. Like solo content creators who no longer need large studios to finance and organise massive production teams and expensive equipment, we'll see more independent developers and small teams creating innovative software with some artistic character. Without the drag of management and upfront financing, the threshold for success will be much lower.
Another will be a market for lemons. Employers will have to find ways to establish competence at building high quality, understandable and maintainable systems. AI can already pass Leetcode-style tests so these are clearly not the right measures.
This is my best optimistic take on things. The rest of the time I'm worried the AI is coming for our jobs.
One transformation will come when a single developer can do the work of a team of ten today. Like solo content creators who no longer need large studios to finance and organise massive production teams and expensive equipment, we'll see more independent developers and small teams creating innovative software with some artistic character. Without the drag of management and upfront financing, the threshold for success will be much lower.
Another will be a market for lemons. Employers will have to find ways to establish competence at building high quality, understandable and maintainable systems. AI can already pass Leetcode-style tests so these are clearly not the right measures.
This is my best optimistic take on things. The rest of the time I'm worried the AI is coming for our jobs.
I think the real problem with python packaging is a cross-language one. Show me a language that can elegantly handle building C/C++ dependencies across platforms. This is where things really break down. Python is unusual in this because it relies on C/C++ libraries for performance in a lot of domains.
We just accept that our fragmented software landscape spans several backend technology stacks, web browsers and two dominant mobile platforms that are in constant flux. ES6, Typescript, Swift and Kotlin didn't even exist a decade ago and their constantly shifting ecosystems are nearly impossible for a single developer to keep up with. Higher barriers to entry work well for the large companies that dominate our industry so they continue to churn out complexity as best practice.
Allowing a single developer to deliver customer-facing applications without the context switch and coordination overhead of a team is a big deal. In the 80s and 90s, this was possible. Today, even deployment has become a specialised role. Not every engineer wants to be forced into a backend or frontend role in an agile team with product owners and ceremonies. There needs to be room for the craftsman in our industry. This is a step towards empowering the individual hacker again.
Liveview Native is not hugely compelling if you're only looking at it from the perspective of an established company or funded startup that can afford a team of more than 3-6 engineers and devops. As a solo dev or bootstrapped startup with limited resources, this is a killer feature for elixir and phoenix.
This would track and save all resources that were accessed as events. I mean online and offline documentation, specs, pdfs, architecture diagrams, code examples and other parts of the codebase, Jira tickets, bug reports, application screens and output, tests run, failing tests, compiler errors and emails. Everything that the human took in as input before outputting that code. What was Bob looking at when he wrote this line of code? If you had been sitting next to him that week, what would you have seen?
When looking at code, a recommendation engine would show that context, using event data and view frequency to compute relevance.
To do this properly would likely need an isolated developer environment separate from any personal use. Another option would be some kind of ML that would filter out irrelevant events or give the developer a chance to manually edit this data at commit time.
A simplified version of this would track the web resources accessed and allow the developer to manually insert additional links, notes and documents.
This is a tool I would pay for. Call it Retrace.
The same pattern repeated itself in the early 20th century. Truly revolutionary ideas may take a generation to gain popular acceptance.
They had vacuum tubes in the 19th century, atomic theory and Maxwell's equations by the 1860s. I find it difficult to believe that they were incapable of isolating the electron.
I doubt that this has been the obstacle to a unified field theory.
The study reported that married women were happier only when their spouse was in the room. When their spouse was absent their response was miserable. The problem is that the original survey defined absence as a spouse no longer living in the household.
https://www.vox.com/future-perfect/2019/6/4/18650969/married...
https://www.youtube.com/watch?v=Yval98eOyZc
http://minikanren.org/workshop/2020/minikanren-2020-paper10....
"Above the line" if len(s) % 2 == 0 else "Below the line"The popups are intrusive. I have limited patience for that kind of thing when shopping online. When there's money to spend (and car money too), my mental Internet filter is in the strictest no bullshit mode. Popups lower trust, go unread and would have sent me back to Google.
A tumbling probe that doubles as a cosmic pointer to home. Cool.
Doing this even after becoming a world famous physicist led to the Feynman Lectures in Physics - written as much for his own benefit as for his students. However, I am not sure he used this strategy when learning entirely new concepts the very first time.
It makes sense to do this as practice. To build new theoretical structures, building new constructions of the stuff we already know is a great way to sharpen a toolbox of problem-solving techniques and reveal potential shaky theoretical foundations.
Edit: Also comparing a Doctoral student who "helped build the telescope" to a cleaner is rather unfair. Francis Crick was a PhD student when they worked out the structure of DNA.
What is the minimum viable human brain? If our brains are indeed highly-redundant scale-free networks, would it be possible to eliminate a precisely targeted 99% of neurons without significant degradation? Can we simulate 1% of a brain on today's supercomputers? How about emulating an existing brain? Do animals have the raw hardware to match or exceed human intelligence? Can we download human 'software' into modified animals instead of machines? Are we already being simulated?
This would keep me up at night too.