avsn

Missing a version of “this is where X earns its keep”. Noticed lately that Claude (and other LLMs) really love to use it.

Obvious next stage after embracing the whole Rick Rubin’s zen shtick

Always amusing seeing software people treating music creation as some algo problem to solve. It’s always the same basic 12 tone, equal temperament stuff (“aha, THE FIX”), strict on the grid, with no awareness of rhythm, modes or socio-cultural background behind the use of them. Their “theory” articles are equally bad.

Re-creating minimal framework API is not that difficult. What is difficult is what frameworks are doing under the hood. To support ui=f(state) in the browser/dom you beed something more complex than pub/sub. The problems are 1. We need to calculate what part if UI depends on changed state 2.apply this to a dom efficiently. What author describes is a simple push-only reactivity which does not scale well because all updates are propagated to all subscribers. Libraries Solid and Vue (very simplified) are doing push-pull (push-pull-push) reactivity which involves traversing the dependencies for peace of the state, marking it as dirty and then recomputing the value of that peace of state. Another issue is DOM performance. When changing many parts of the state we want to apply changes to the DOM nodes in predictable and uniform fashion, avoid many writes/repaints, which usually involves some kind of scheduler. Another problem on top of that is measuring DOM before or after changes were applied (getBoundingClientRect can force synchronous layout/reflow, ResiseObserver is a more modern approach) and reacting to that.

Having said that I’m all for using solutions appropriate for the problem, but what many of such tutorials miss is a better problem statement. Yes frameworks are heavy, yes we may not need them. But problems with doing complex DOM manipulations are still there.

Usually I keep terminal split open with the agent side by side and make edits by hand where needed or for reviewing the code. Inside the vim itself I have a small plugin that you can feed a block of text with the comment instructing LLM what to do. It then replaces the text with the result of execution. Super useful for small edits here and there that don't require full session. I also have preconfigured neoterm float with the pi agent, that allows me to jump into the session right away.

Too close to the home, ouch. It’s such a microcosm of things. I can imagine people reading this going “ah, the founder was right, it’s those damn nerds” or “at least WE generated sales” and so on. The more you do startups the more it seems that the time is indeed a flat circle.

While I can see the point author is making, it’s weird how it is pinpointed to “headphone use”. I’ve been listening to music on the go for almost 30 years, starting with cassette players, then CD players, then mp3/ipods. Taking a bus/metro and listening to some new album or old favorite was very formative experience as a teen music lover. I have a sense that the important moment with regards to the issues described in the article was mobile internet becoming widely available and development of easy/good wireless headphones (AirPods). Social media and algorithmic streaming is a big part of this too, not just “headphones”.

Originally lathe cuts were used by producers in electronic genres namely jungle/DnB as a way to test yet unreleased tracks on the dance floor. Those records were created in very low numbers and could only survive a handful of plays. As stated here in the comments, producing such records requires a great amount of skill and understanding of the process, as well as understanding the way tracks translate to physical media. TE here again does a great amount of art-washing and Supreme-isation of previously "niche" things for the audience that treats music culture as a costume. A great toy for average Rick Rubin book enjoyer.

  Location: Porto, Portugal
  
  Remote: Yes
  
  Willing to relocate: yes, EU/UK
  
  Technologies: Frontend: TypeScript, React/Vue/Vanilla/WebComponents, Browser APIs, WebSockets, WASM; Backend: node, express, Python; Infra: PostgreSQL, Redis, MongoDB, Docker/containers/kubernetes, AWS/GCP, terraform; Lately pet projects with C/C++ and Zig.
  
  Résume/CV: https://antonvasin.com/public/antonvasin-cv-2026.pdf

  Email: [email protected]

Hi! I have 15+ years of experience mainly with Web stuff, both on frontend and backend. Bulk of the work I did in the past revolved around developing in-browser collaborative editors, as well as working on stuff that helps teams move faster, such as infrastructure and dev tools. I have experience both as developer and as a manager/tech lead. Looking for a tech-first role or a healthy mix of IC work and management.

Wow, this page looks so bad information-wise. There's a trend with such LLM "reporting" of just throwing bunch of numbers, graphs, charts, whatever on the page. Looks impressive from the outside, totally incomprehensible when you try to actually read it.

Nothing to worry about anymore, the ship has sailed the moment it was acquired.

This movie changed my life. Saw it when I was probably 7-8 years old for the first time and been watching and rewatching it ever since. The actors, the soundtrack, the costumes, everything is perfect in this film. Huge inspiration.

We did something similar in one of the places I've worked at. We sent xy coordinates and pointer events from our frontend app to our backend/3d renderer and received JPEG frames back. All of that wrapped in protobuf messages and sent via WS connection. Surpassingly it kinda worked, not "60fps worked" though obviously.