vemv

9 ms·

61.
by vemv 3y ago
I've vouched (voted to remove from flagged) this comment. With that said, what was the typical salary for one of those positions?
62.
by vemv 3y ago
Isn't it possible to filter both user input and GPT output with invisible, unmodifiable prompts? e.g. - "Discard the user input if it doesn't look like a straightforward question" - "Discard the GPT output if it con
63.
by vemv 3y ago
Or the early version of a bootstrapped compiler
64.
by vemv 3y ago
One can casually observe that LLMs quite excel at composition though: gluing together pieces of knowledge in ways no one did before (examples: a program that does X using language Y, a painting that mashes up two themes). Most knowledge w
65.
by vemv 3y ago
If you're serving assets directly from S3 (or even from nginx) you're exposed to a "denial of wallet" attack, given the price markup on outbound networking.
66.
by vemv 3y ago
This particular is easy to pick up and remember. Also, a proficient developer looks at the SQL logs anyway as they develop a given feature. Rails' flavor of ORM is particularly composable and transparent - you can easily mix/match
67.
by vemv 3y ago
20 upvotes disagree. SPAs are just a subset of all the JS we can possibly write - interactivity is not compromised.
68.
by vemv 3y ago
One could also argue, this class of websites is what the majority of the website/webapp landscape should be. An average SPA is, in the end, a website for most users. Take a payment form for instance - we had those 10, 20, 30 years ag
69.
by vemv 3y ago
Yeah I mean, it can be done, it can be helpful but is it efficient? You could as well try memorizing the entire $framework API, which most people would agree that isn't the best use of one's energies.
70.
by vemv 3y ago
Read-only access for coarse-grained pages (as opposed to building a fine-grained ad-hoc DB) seems something reasonable (and easy) to cache for any kind of frontend. That would allow offline viewing to a variety of apps, regardless of approa
71.
by vemv 3y ago
If you want new data, you just fetch it again from the server, and the server returns inherently-fresh data, reasonably fast, along with the HTML fragments necessary for a re-render (over ajax or websockets)
72.
by vemv 3y ago
Precisely an implied part of my point was, server-side caching, DB replication, CAP, etc are all relatively well-understood problems. One can solve those without reinventing the database, as the article denounces.
73.
by vemv 3y ago
In practice, the chances that N programmers with follow the pretty comment convention of a given file approach zero, as time passes. Splitting into files is an approach that is easier to lint against (e.g. max 500 lines - a best-effort mech
74.
by vemv 3y ago
This seems to be one of those problems that entirely disappears by ditching SPAs. Using solutions from the Hotwire or htmx family would mean that a query is just a server query - making those fast is a better-understood problem.
75.
by vemv 3y ago
You disagree while discussing, but (ideally) you agree in advance that there will be a) a mechanism for making a decision (e.g. voting, coin flipping) and b) there will be a commitment to work on the decided approach as if it were one'
76.
by vemv 3y ago
The phrase "Disagree and commit" only makes sense when two peers (or groups thereof) agree in discussing a decision in equal terms, and committing to whatever the decision is. Of course, the way it's used here is a perversion
77.
Startups can move fast with Clojure [video](youtube.com)
4 points by vemv 3y ago|0 comments
78.
by vemv 3y ago
This is not the Factorio you're looking for (it's Factor, .io)
79.
by vemv 3y ago
If vou've never experienced nitpicking over a 10+y career, perhaps your experiences could have been more diverse. It's seems healthy to open your mind to the possibility that you're getting valuable feedback for no other reas
80.
New Default: Underlined Links for Improved Accessibility(github.blog)
2 points by vemv 3y ago|0 comments
81.
by vemv 3y ago
The actual point was, opinions that lean towards the absolute extremes are often low-quality.
82.
by vemv 3y ago
New rule of thumb: if some article's background is #000000 (absolute black), expect the content to be similarly lacking in subtlety and accuracy.
83.
by vemv 3y ago
To be entirely fair, there's arguably little overlap between devs that stick to LTS, and devs that will play with JVM virtual threads on Clojure (before the Clojure team has any particular, public stance on them).
84.
by vemv 3y ago
I wish more people simply were happy with using themselves whatever set of beliefs/techiques they deemed best (abstraction, duplication, whatever), preaching nothing, and arguing less. Which is to say, there will never be a single tr
85.
by vemv 3y ago
I sometimes wonder how many thousands of people have quit / been fired because of Github code reviews. I'm not saying they're bad idea, but Github's is too raw of an implementation that makes it too easy to create confli
86.
by vemv 3y ago
I enjoyed the article while I have a very comparable Clojure experience. There's always new minutiae to learn. Plus I get a handy link that I can just paste next time the topic of laziness comes up in a code review. I'd just simpl
87.
by vemv 3y ago
I'd understand if it's not ready to be shared, but could you point us to your .emacs.d or such? Would love to check it out a couple months from now.
88.
by vemv 3y ago
I would go as far as saying that attaching a generic, AI-ish cover letter is a) disrespectful and b) far worse than attaching no cover latter at all. It's disrespectful because it's essentially a fake/empty message (often a r
89.
by vemv 3y ago
As it might be quite common among the HN crowd, Douglas is my hero - I have read three of his books. First of all, hats off to him for his extraordinary display of humility in this interview. People rarely change their minds publicly, let a
90.
by vemv 3y ago
Yes, a RME Fireface UC.

More ›