vemv

25 ms·

241.
by vemv 7y ago
I use github's kanban board and like the concept of Kanban overall. Some people don't realise that Kanban is quite the opposite of Scrum. One variation that has worked for me / peers over the years is having a "Next 5&qu
242.
by vemv 7y ago
Agreed that post-hoc security cannot work very well. Hope it becomes more and more obvious industry-wide. One thing I do to practice "continuous security", is to accompany each code review with an additional code review, solely fo
243.
by vemv 7y ago
The article's phrasing doesn't seem that correct: yesterday's historical curiosity is not necessarily today's historical curiosity ( today being 3000 AD).
244.
by vemv 7y ago
Wondering if the choice of a 16" screen was mainly for thermal reasons (bigger screen -> bigger chasis overall). FWIW 6-core over 15" (2019 model) is working nicely for me, but I suspect 8-core might be a bit too much for 15&qu
245.
by vemv 7y ago
I'd help a lot if the project showed rationale, alternatives, its taken choices and the corresponding tradeoffs. Otherwise, one is essentially invited to blindly adopt someone else's design, which is particularly reckless in distr
246.
by vemv 7y ago
People who care enough about music to pay a monthly fee, surely are also invested enough to develop their own tastes? IOW, who pays for listening to "radio" (Top 40) music? There's an audience for Top 40 music, but they wil
247.
by vemv 7y ago
15 years ago, a niche artist could earn tens of thousands a year by selling CDs and especially digital albums. Not enough to make a living, but definitely an encouraging amount that enabled touring and buying more music gear. Now in the Spo
248.
by vemv 7y ago
You're not saving them any work by creating that PR. That's better discussed and agreed on in advance.
249.
by vemv 7y ago
prefixes such as "fix: " are better expressed at the bottom of the commit message body. They are metadata, and as such they shouldn't take more attention than the actual data. This matters when you are in a bug hunt in produc
250.
by vemv 7y ago
> it only makes it worse because you have to think to yourself "he might be right" Seems a self-defeating statement. Thinking isn't wrong. Neither it is that someone else is right.
251.
by vemv 7y ago
Hackers from a variety of languages could be attracted by the high core count, which allows one to test parallel programming easily and reap its benefits first-hand. I myself code in Clojure, have trivially parallelized some productivity to
252.
by vemv 7y ago
I see now, thanks!
253.
by vemv 7y ago
They could be there as a guardrail for a worst-case scenario, without them being particularly needed for the average use case.
254.
by vemv 7y ago
Pro tip: as you speak, after each message (sentence, couple of sentences) make sure your interlocutor understood that part - verbally or not. It's not the same as using short sentences - personally I don't expect/allow to be
255.
by vemv 7y ago
> Don’t use Objective-C/Swift on the audio thread. His argumentation is that Objective-C uses locks internally. But isn't it possible that those locks (as opposed to application-level locks) cause just negligible pauses, beca
256.
by vemv 7y ago
Probably I agree with you. I was mostly pointing out the weak writing: over<x> and <y> madness are always sub-optimal, for all values of x and y.
257.
by vemv 7y ago
> No mentions of microservices, serverless architecture, application boundaries, event-driven architecture, and the lot. I see why one would want to escape the mindless name-dropping that can be prevalent elsewhere, but at the same time,
258.
by vemv 7y ago
> Oversimplification and architecture madness are sub-optimal. Let me point out, you are essentially saying "bad things are bad" here.
259.
by vemv 7y ago
It's development and not developers the thing being iterated, right? It's as if I wrote "developer deployment".
260.
by vemv 7y ago
I've read the blog posts in the past, and it seems quite likely that Dark could be a large conflation of concepts (as opposed to composition), which repeatedly traded off desirable properties for faster deployments. The opposite is not
261.
by vemv 7y ago
From the landing page: > Speed of developer iteration is the single most important factor in how quickly a technology company can move. What? "Speed of developer iteration" barely makes any sense, it's poor wording. In any
262.
by vemv 7y ago
I find the bucket-of-crabs observation super interesting. It's likely a problem not often talked about (nobody likes to admit or suggest envy). At the same time, there is some justification when developers get put off by certain OSS pr
263.
by vemv 7y ago
https://hackernoon.com/stop-using-io-domain-names-for-produc...
264.
by vemv 7y ago
> Second-class-citizen APIs are always trouble. An unlikely absolute: nothing prevents the second-class citizen from gaining traction and eventually becoming first-class.
265.
by vemv 7y ago
Related read - here is an explanation, coming from a Clojure folk, of why Kafka (Streams) might play a crucial role in your next architecture. https://www.confluent.io/blog/toward-functional-programming-... Has been a
266.
by vemv 7y ago
As an idea, someone could implement a middle ground solution between `pass` ( https://www.passwordstore.org ) and a cloud solution. Key design: encryption/decription happens locally, using standard open-source tools such as G
267.
by vemv 7y ago
I might be wrong, but last time I visited the US (coming from Europe) I couldn't find in Whole Foods _fresh _ veggie patties. Those are kept in the fridge, not in the freezer. They are somewhat processed, but surely not as heavily as B
268.
by vemv 7y ago
This is not Reddit.
269.
by vemv 7y ago
Likewise my Clojure jobs tend to involve reviewing multiple devs' code. It's certainly possible to converge towards some shared notion of what constitutes maintainable code. We additionally have an internal styleguide plus some fo
270.
by vemv 7y ago
You are absolutely free to decompose computations into more `defn`s, `let` statements, or threading operators. Or mix and match those.

More ›