lowenbjer

6 ms·

1.
by lowenbjer 6mo ago
Fair enough! Can't argue with that
2.
by lowenbjer 6mo ago
I tried tidal for the Lossless (dont care about the 24bit, i care about no EQ and compression added to music) but i went back to spotify for their recommendation model. Its a moat for me.
3.
by lowenbjer 6mo ago
Fair point, for me there is no scrolling required though, its like nr 3 in the list. I wonder how long it will take for AI to learn how we work with software on an individual level and adapt the UI to fit our usage patterns.
4.
by lowenbjer 6mo ago
I get that it looks bad to have vibe coding bugs creeping into your codebase for such a big company, but isn't it common sense that owning your misstakes taking accountability for them generates respect?
5.
by lowenbjer 6mo ago
Three dots next to the song title, menu opens, "Add to Queue", done.
6.
by lowenbjer 6mo ago
"the spotify subreddit is actively removing discussion of the problem" This sounds like terribly bad form, won't buy them any goodwill down the line.
7.
by lowenbjer 6mo ago
Agree!
8.
by lowenbjer 6mo ago
Check back in 2 years time, for now it has survived fine. Someone will be tuning it to write the documentation soon, instead of just blocking! Jokes aside, i think LLMs will enable us to handle information in a much better and smoother way.
9.
by lowenbjer 6mo ago
Cursor, Sourcegraph Cody, and honestly just Claude with a well-maintained project README already solve the "ask questions about the codebase" part reasonably well. The actual hard part of joining a new team isn't the code (to
10.
by lowenbjer 6mo ago
My take after running engineering teams at multiple companies: documentation survives when it lives next to the code. File-level header comments explaining each component's purpose and role in the architecture. A good README tying it a
11.
by lowenbjer 6mo ago
I've been a CTO and founder several times. The bottleneck was never "getting the work done." It was always translating between the business reality (runway, revenue, growth, what customers actually want to pay for) and what t
12.
by lowenbjer 6mo ago
Ha, same. I wrote a VOD transcoding orchestrator in Elixir that triggered libav transcodes and custom packaging code in Python. Loved the syntax, and in particular the pattern matching in function headers. It was so clean for recursive bran
13.
by lowenbjer 6mo ago
I know that feeling. Just because a tool is good doesn't mean you enjoy using it. I moved deeper into streaming infra with Python, C/C++, Go, and funnily enough Elixir. Then a complete path change into fintech and later AI/ML
14.
by lowenbjer 6mo ago
I worked on lab automation and scientific software early in my career. One piece of advice: keep it ruthlessly simple. In most software a bug is a bad UX. In scientific software a bug can mean contaminated samples or months of invalidated r
15.
by lowenbjer 6mo ago
I was part of building the streaming frontend for one of Sweden's largest broadcasters in Rails about 10 years ago. Handled 1M+ concurrent users on Heroku with horizontal scaling. Fun fact: someone on the team literally stayed up monit