1,988 karma · joined December 9, 2014
My point was preciously to challenge STOA in domains, not questions with well known answers.
What I can imagine though is that
- the value of merged PRs might drop (as it's not a good metric anymore)
- while the cost of submitting them goes up (as price per token is radically changing, e.g. Github announcement just this week)
so maybe it's also only temporary.
Also if all this is correct, including the value of PR on popular repository being more important, then the long tail of projects might not have to worry about this.
How do you do that efficiently so it can scale?
I feel like 1/10 comment I make on HN are about this.
So merged PR were until LLMs a good proxy for the ability to code and contribute to a software project. Consequently they were used to estimate if a candidate was potentially good for a position. Merged PR on popular project were thus precious credentials one could "trade" for potential work. Since then the desire to provide PR changed from contributing to a project for its own sake, to make the actual project progress, to signalling.
A new proxy must be found to establish the ability to contribute to a project.
What does it do that a paper version with magnets can't though? Does it track time? Rank? Something else?
Indeed a video on a phone provides very limited agency. I was mostly trying to highlight, as someone else pointed out, that demanding content will not have the same effect. Thus blaming the device itself is wrong.
Edit: shit... now when I acknowledge my mistake I sound like a sycophantic chatbot! Ugh. Edited to replace "You're right" by "Indeed". I'll have to remember that.
What actually does make "old" tech good?
I'd argue it's agency. It can be the physicality of it too but if so then one has to pinpoint actually what it is, e.g is the presence of CD covers in the living room as reminder that you do have a collection? If so would a poster suffice?
I think kids can absolutely use contemporary tech but it has to be done responsibly.
A smartphone or a laptop is not the problem. The problems are :
- advertisements prompting for "more"
- friction-less unlimited availability
- unmetered unplanned usage
- content that requires no effort, no actual thinking, to consume
but holding the physical medium or have a "retro" look is superficial. It doesn't actually matter.
You can absolutely give a smartphone to a very young kid, say a 5 years old. What you can not do though is hand them that smartphone with installed an app that will provide limitless uncurated videos or games. Give them a phone with a 2hrs long documentary on animals or with challenging pedagogical games and you will see that they enjoy it, for a bit, then have to move on. It's NOT the device, it's the content and the software that makes that content available. I really get tired of "screen" time. No kid get hooked on hard to complete digital homework. They get hooked on apps designed and providing content itself made to be addictive.
It's really not about the shape or age of the device.
PS: I shared some resources at https://forum.techreclaimers.club/d/36-reclaming-for-kids/2 to provide actual alternatives.
You absolutely are. That's precisely why they were forced to make the browser not a core part of their OS.
The entire strategy of Microsoft has been since its inception to force people to use their solutions! They got the OS on the computer itself, not something to install after with a conscious choice. Once they do this they bundle writer, spreadsheet, etc suite as one-way interoperable, then browser then online suite, then cloud, then AI... and it doesn't start with with your CTO or CIO, no it starts in school, giving licenses for poor students who can now "afford" the tool and be trained for life.
Microsoft a single uninterrupted chain of bundling despite being an illegal practice. Of course none of that would work on merit itself so they do the lobbying to insure it's used in institutions and everywhere else they can to insure that their tools are basically required.
They've been there for a while now. Sadly.
You do not, never EVER, start from a blank slate.
Step 0 is to actually challenge the value. Before you even start you spend a LOT of time with the person with a need to narrow down what they actually need. Not what they think they want but what's genuinely problematic for that. Again, NOT how to solve it but what's a thorn that's painful for them, not for what you imagine it might be. This honestly often get uncomfortable quickly because you have to ask "Ok but have you tried this? What about this quirky thing?" because it challenges their own attempts. If you don't spend a significant amount of time in that space you WILL implement faster, that's obvious, but you are very likely to efficient "solve" the wrong problem. You will solve what you can solve easily. Think about it like looking for keys where there is light, not where you lost them.
So... that's before one has even started to code, it's mostly uncomfortable discussions. Only once there is some confidence from both parties that the problem is identified can implementing might make sense. Then you don't! You do NOT touch a line of code. Instead you take whatever you can, post-it notes, Lego bricks, existing software, you tape all that together and you ask "Would THAT (very ugly barely working monster) kind of solve it for you?". So you do not build anything new, you ONLY stick together the BIGGEST existing parts.
Only then you might eventually build something but STILL you don't start from a blank slate. You are going to find the highest level of abstraction you can find. They want something related to the Web? You don't freaking build a Web browser, or a even PWA, you paste a code snippet in the console.
You always look for the way with the MINIMUM amount of new code. It's never about implementing faster. It's about NOT implementing faster.
Now the fun part (arguably) actually begins when you have done all that but it's still not enough. You use a CMS or a browser or whatever large exiting verified code base and the need is not solved. Then you rely on the built-in extension system of that code! Guess what, there might even be an existing plugin that does what you thought was novel.
Finally, finally you did find no extension for that existing quality open-source large code based so you HAVE to build it. Well, not so fast, is there another piece of code from another software that does it? Does it have an API? Can you connect to that API to get that functionality in that extension?
Then you have done it, you brought together 2 large pieces of software but you only coded the connector between the two.
Your prototype is, in practice, 10 lines of code.
TL;DR: yes, good prototypists code very little and yet still end up with genuinely novel work.
Convinced you can distinguish A from B? Ok! No problem, let's try! Can be at the dinner table for fancy wine or with agents, it's all the same, you try an option, another option, maybe all options from the same, and if you reliably can't tell well kudos, you are just like the rest of us!
It's easy to "know" in retrospect but blind test is where genuine difference can be found. Or not.
I did find https://cve-north-stars.github.io/docs/CVE-analysis#seeking-... though as an example, quite interesting.
- what is X, I just do Y
- wow I can see so many limits of Y, now I do X
- I use X for literally everything
- now that I properly understand the limits of Y but also the heavy constraints of X ... maybe Y is enough
- I use Y for literally everything
rinse & repeat. The thing is with actual usage and actual context one does learn and thus can get away with a lot more "basic" solution but it does require genuinely understanding the limits.
Damn, on point. So hard to go over that hump but so worth it, every time, in retrospect.
Interesting that you remember CVEs by ID and how they relate one to another. Do you know if they are visualization of CVEs? I'm wondering if that would help newcomers to security to get some memorable insights.
PS: yes, I might or might not have a degree in corporate strategy & PR.