3,476 karma · joined April 10, 2007
If they did a bunch of unethical stuff that adds up to fraud, as you agree, what does it matter if some individual actions, if you completely take them out of context, look at them through the right lens, and create a distinction between “unethical” and “bad,” aren’t necessarily bad? Maybe the reason no one is saying that is because no one is doing that, because it’s not relevant.
The individual actions are certainly sketchy, IMO. And red flags. Is there a definite semantic difference? It seems like splitting hairs. No single action by itself implies fraud, though significant acts of lying make a case.
Theranos’s level of deception is not the norm. Nor is it legal or ok.
You conclude by sort of saying you just aren’t going to focus on the misconduct aspect of things. But it is still there.
If I were literally the only audience for some writing, it would look like my personal notes.
I could be a core part of my audience, or farther from it. I consider myself to be part of the audience for what I'm writing right now, since the words are coming to me as I'm writing. If I'm telling you some information I already know, or documenting some code, then a future version of me that has forgotten the information could be part of the audience. In some cases--and I presume it would be even more cases if I were a professional writer--I am farther from being part of the audience. Then it's important to know my audience well enough to be able to put myself in their shoes a bit. For example, if I were going to write a lesson teaching programming or calculus to someone from scratch, I would need to understand what points my audience needs broken down and explained. I might need experience as a teacher of these topics to do that. As another example, if I am writing to an audience that has different life experiences and privilege from me, and I don't take that into account, my message might land awkwardly or fall flat.
The bigger the creative undertaking, the more important it is that you are bringing something into the world that you, personally, very much want to see in the world based on your personal desires and preferences, in my opinion. If you are going to write a novel, or pitch a TV show, or open a restaurant, it's got to be your thing. Specific and personal is good. You have to keep a somewhat general audience in mind, though. For example, if you are very tall, don't open a restaurant that is only comfortable to sit in for very tall people.
Does this apply to start-ups? It can. Not every aspect of a start-up is a creative work. Sometimes the code is the creative work, and the business idea is what pays the bills. Sometimes the business is where the passion is, and the software is a means to an end. Ideally, different people on a team bring their creativity and passion to different aspects of the product. However, a very driven founder may just want to see his or her idea exist in some form, and not find, cultivate, and encourage a good designer's creativity. Sometimes "design" just means making a whole lot of product and aesthetic decisions that need to be made, and it's not based on anyone's coherent creative vision. When there are a lot of decisions to make and seemingly no objective basis for making them, and no designer that has the team's trust and respect (giving them earned power to make decisions), start-ups just ship things and see if people like them, using "user feedback" as the missing objectivity.
I don't know what designers mean when they say to each other, "You aren't designing for yourself." I have been on projects where I had to remind myself that I wasn't in the target market, though, and it sucked. For example, working on a tool for programmers, and being a programmer, but it not being the kind of tool I would want to use. I am a very creative person, and I am best suited to thinking of my work as undertaking a big creative project.
I think PG thinks of start-ups in terms of hacking, which he relates to painting (famously) and to some extent writing, emphasizing individual creativity and craftsmanship, so it's a similar sentiment.
I think the blurb about the downsides of Wasm is just too generic, it’s a sort of “why Wasm isn’t preferable to JS in all cases” for the uninitiated. It may not be meant to imply that number crunching is the use case.
This approach may indeed have limitations in terms of applying common knowledge and keeping track of state and context in a narrative, across many sentences. I played with GPT-3 for creative writing and found it was not able to keep track of characters and objects and their states very well. For example, we know that if we drop a coin into an empty piggy bank, the coin now resides in the interior of the piggy bank, and the bank will make a noise when shaken, and so on. GPT appears spotty on that stuff. But I also think this is expecting too much of it, as a text prediction engine that sometimes produces a very plausible series of sentences that does take some context into account.
The other point people are discussing is, are we humans doing something fundamentally different when we parse a sentence and find there to be one "correct" parse (along with one or two close-but-clearly-incorrect parses), in our opinion (which we feel confident about and can explain), compared to an AI that will offer a few different "guesses" as possibilities? I think humans are probably doing more cross-checking via different systems, but these systems could be built into the machine model. For example, if we are sure that parse A is correct and parse B is incorrect, and we can explain why, perhaps our confidence comes from our ability to explain, and the machine should be trained to produce logical explanations of its decisions. Or perhaps some of us humans have developed a sort of ambiguity detector, because of the likelihood and cost of certain misunderstandings, which triggers a more careful analysis of the grammatical situation, and the model needs something like that to be more human-like (or more like a careful and conscientious communicator, anyway).
I think it's correct that, ideally, there would be a framework that handles real-time collaboration, undo/redo, and offline support for you, and then you build your app with these problems already solved. I will probably create such a framework eventually. I don't see it as a database engineering problem, it's more like a framework or application architecture, which every app like Google Docs or Figma has its own version of. Writing such a framework is not too much harder than writing such an app, it just requires a little more abstraction and some documentation.
If you've never written an undo manager, sync engine, etc., and you aren't writing a complex app, it's hard to arrive at the right design by thinking about pure data sync. Also, storing and querying data are solved problems; it's more a question of coming up with a generic data model for an application and defining its semantics.
I think Parcel 1's biggest issue was being really ambitious, and then never reaching maturity, in that it had bugs that weren't fixed. It wasn't maintained. So it had its own file watcher, for example, I believe, which is great in theory, but not when it's buggy and unmaintained. My personal style would be if I'm going to write my own version of something, write it in a really high-quality way, and keep it simple, either in API or implementation. Maybe reuse the same module for Parcel 2 and improve it, keeping the same API, or if I'm going to rewrite it, use the rewritten module in Parcel 1, or something. I wouldn't just write my own library for X, and Y, and Z, and put it out there, get a lot of people using it, and then move on. I love writing my own versions of things and taking on fun and ambitious projects, but I'd rather nobody use the code I write in my spare time, for free, and don't want to maintain, than create a liability for people.
Another issue I ran into is Parcel insisted on running "npm install", which was a feature that you couldn't turn off even if it didn't suit your project structure. This violates a few principles of mine.
It's an attempt to be "magical" in order to reduce the amount of configuration. "Magic" is not a good thing. Think about what makes a magic trick a magic trick: obfuscation. It's magic because you don't know what's happening, but you get one moment of delight out of it. Overall it increases complexity; it's the opposite of making things simple. Rich Hickey talks about how "simplicity" properly means simplicity of behavior, not fewer words on the screen. Keep the tool simple and understandable, and the way you instruct it what to do simple and understandable. If you want something to work well out of the box, by all means, build popular things like TypeScript into the core; have sensible defaults and explain what they are. But configuring a piece of software is a dialogue where you learn what the capabilities of the program are. There's no place for "do what I mean" in good UX.
Also, build tools should not treat development as something that happens from a unix shell, and try to "automate" it by shelling out to this and that. That's error-prone and likely not to be very universal or focused. Imagine if Webpack's core shelled out to "git" or something (to make up a random example). It would be ridiculous.
The biggest way to improve on Webpack IMO would be to make something that is both easy to get started with and easier to understand and customize for professional developers. Keep in mind that Webpack has been mature now for a long time, and it has extensive docs and guides, and tons of plugins, and you can write your own plugins without too much fuss... any alternative that is buggy (until further notice, maybe years from now if ever) and poorly documented (until further notice, ditto), and not inherently simpler or easier to understand or troubleshoot, while also having less of an ecosystem of available plugins, etc. is just not a good substitute.
Reading between the lines, it’s statically-typed, compiles to assembly, and I haven’t seen a type annotation yet, but I’ve seen a “let rec,” so maybe it’s similar to OCaml? Or even Ocaml in disguise again? But perhaps they decided to obscure that for marketing reasons, as if adopters of hot-off-the-press programming languages are just programmers looking for something nondescriptly “modern”, rather than programming language enthusiasts.
Also note the bulk of the article is about edge cases that are unlikely to occur in practice. It helped me understand what they were talking about when I realized this. You aren’t actually going to inherit a private field through the prototype chain or deal with partially-initialized objects, in all likelihood.
Personally, as a TypeScript fan, my class-oriented code uses the “protected” keyword a lot, and it suits my purposes well. I don’t need runtime “safety,” and I find that truly private fields to one class (not subclasses or tests, for example) have limited use.
Paul’s point about not being Reddit, I think, is you need good moderation, and you need to be willing to block and ban. Despite this, Jeff assumes HN limits downvoting in order to not hurt people’s feelings or something, which is a total straw man or non sequitur.
From my armchair, I gather that good communities require good moderation, so if you are trying to scale moderation, that’s your work right there, and a downvoting mechanism doesn’t take the place of that. Ideally mods are people who have organically earned trust and power or are known and trusted by other mods or leaders. Karma scores alone don’t cut it. The mods can use tools to be more efficient and not require an army. If you are running a site that relies on mods, you need a good relationship with your mods and to give them good tools and guidelines.
Pros/exciting things:
1) There's a simplicity in using VS Code for writing notes and docs if (and probably only if) you already spend your day in VS Code, like I do.
2) The Markdown Preview Enhanced VS Code extension (which is a dependency of Dendron) is super cool for having so many "batteries" included. For example, check out all the diagram types it supports: https://shd101wyy.github.io/markdown-preview-enhanced/#/diag... . I still use it, separately from Dendron.
3) Storing my data as plain text on disk (backed up by GitHub or Dropbox) has nice properties compared to how SaaS apps do it (e.g. if you use Notion, say, your data materializes out of "the cloud" when you launch the app, and otherwise has no tangible existence). When my data is plain text on my local disk, I own it; I know I can export it, I can run whatever editor or program on it; I can access past versions (via git or Dropbox); I don't have to worry about it being corrupted, or accidentally deleting some of it, or not being able to access it because of server issues, or not being able to export it, or being offline, and so on.
4) The Dendron docs ("wiki") site is created using Dendron. It's a cool thought that I could create a nice website of documentation or notes without leaving VS Code.
Cons:
1) Can't access my notes from mobile.
2) Major warts in navigating between notes. Each note has a tab for editing it and a tab for viewing/previewing it. Opening a note behaves differently depending on which tab is focused. Clicking links to go from one note to another doesn't work very well.
3) Poor full-text search (just VS Code's code search).
4) You can't specify an order for notes, only unordered hierarchy, and you can't easily view multiple notes at once, which means keeping lots of short notes, or using different notes for different sections of a document, doesn't really work. There's a tension in any note-taking tool between short notes and long notes. Should notes be as short as possible? Or stretch into long documents? The ideal tool IMO would blur the difference between an ordered hierarchy of sections within a document and an ordered hierarchy of notes within some grouping. Dendron makes it seem like it is for keeping thousands of small notes, but the ways in which you can view, organize, and navigate between notes (lack of good "browse," search, links, lists, seeing multiple notes, next/previous note, and so on) are so limited that it makes more sense to write long documents. In which case, all you really need is Markdown Preview Enhanced and the file system.
It's been a few years since I was reading in-depth about Bitcoin, and I don't have references, but off the top of my head:
* It's bad for the environment, "wasting" so much electricity on more and more literal busywork... or is it? Apparently it depends where your electricity is coming from (it had better be cheap if you want to make money mining!) and whether you are actually causing additional electricity to be generated or just consuming surplus, or so I've heard.
* Control and power over Bitcoin is not all that distributed in practice. Mining a block would take prohibitively long for an individual, so there are mining pools where participants share in the spoils. Mining pools and exchanges have a lot of power. Just as the infrastructure of the Internet is run by big telecommunications companies whose routers talk to each other, there are various major players that make Bitcoin run, and there are occasionally decisions affecting the future and fate of Bitcoin, and Bitcoin politics, like disputes over protocols.
* In theory, Bitcoin is hard to fraudulently "take over" because you'd have to have more computing power than the rest of the miners combined, but if you control mining pools, or are China or something, I believe you could do it (and no one would necessarily know?).
* The rise of Bitcoin as a currency (not just a ledger/clock) whose value seems to just go up and up raises a lot of questions (IMO) about whether this is a good property of a distributed ledger system.
Even if Apple’s motives are somehow nefarious, Facebook is being scummy in the first place, so it’s a fair move for Apple to take advantage of that, IMO.
Contrary to the article, there is far too little emphasis on morality and good character when it comes to "public figures," especially in politics and business. What's new is there is some accountability in this respect, sometimes, in some domains. Actions have consequences, and no one is entitled to positive public opinion, let alone a position of power and influence, regardless of how bigoted, abusive, or otherwise uncouth they are by 2020 standards. There are some rare sincere apologies, and careers that continue after apologies, and careers that continue despite no responsibility taken and no remorse expressed.
This is a time when we have the likes of Trump and Kavanaugh as public figures. No apologies. No consequences. Anyone who is talking about "virtue" and quoting the Bible who would defend these men has surely lost their way. If we're talking about the cases where there are sincere apologies, I think those apologies are definitely taken into account.
I doubt people are more anxious about saying the wrong thing than they should rightly be, especially considering the anxiety they probably cause on a daily basis if they are so immature and uneducated about how their words and actions affect those around them.
Our sense of "continuous consciousness" is already an illusion, built from a series of moments. There are a lot of things about the brain/mind like that that I think make tulpas less unbelievable the more you think about it. Another is that there is a lot of diversity among "normal" brains. If someone can rotate a 3D shape in their head and you can't, you could say one of you has a "real mental issue," or just acknowledge the diversity. Also, a lot of our "thinking" is not conscious; it seems like we experience certain thoughts as "our thoughts that we are consciously thinking" because some process picks out a thought here and there and presents it that way. If another process were to come along and pick out a different 1% of our ongoing thoughts and present it as a coherent stream of consciousness, conforming to a certain personality, it could be another consciousness.
I don't think the brain/mind has one CPU and one program counter and that's that, and anything else is an illusion; I think it's got lots of cores and lots of threads, and if anything the idea that there's one hardcoded main thread is the illusion.
There’s nothing legally or ethically wrong with having something like Twitter that is more of a neutral communication channel. I’m sure it exists. It’s just that Twitter is popular. Regulations that make something like the-Twitter-we-actually-have illegal are a step in the wrong direction. Twitter was started by human beings with certain values and goals, like making it easier to tell your friends what you are up to, and making money. If they don’t want blood on their hands, that’s their choice.
Facebook and Twitter are like giant newspaper companies that, unlike paper newspapers, which can get in trouble for reprinting someone’s illegal words, are free to distribute others’ words, moderated or unmoderated. No website that you post content to has to distribute that content for you if it doesn’t want to. Twitter is not air.
That said, I don’t know what Facebook and Twitter should do, if there is such a thing as that. I think Twitter could easily justify not blocking Trump, by making the argument that they are a communication service, and they don’t want to start editorializing, but clearly that is not their stance! Facebook curates and bumps content up and down by its very nature, so Lord knows what it “should” do with itself.
We probably just shouldn’t have these giant monoliths.
The question about project scope and resource allocation is also hard to answer in a general way, as I'm not sure why it would be harder in the world I'm suggesting.
A lot of the rest applies to big companies.
However, I would change the conclusion, because the thing is, the culture of "little tasks, little trust" has taken hold even where there is no bureaucracy and no specialization of roles. It happens at start-ups as small as three people.
The antidote is simple, in the start-up case: Give each person one or two big projects to focus on, based on their strengths and interests. Carve up the work by large areas, and give people ownership and responsibility. Look at each person as individual. If someone has no talent or interest in product decisions or UX decisions, they'll need support on those, or a project that doesn't require them. If they have interest and some talent, mentor them. If, as a company, you are trying to make progress on too many things in parallel, or have a shortage of talent in certain functional areas, be real about that.
Frameworks and style guides and even "database guys" aren't a problem, if they are good and support you. However, I think the ideal is probably to have small project teams that grow from one to, say, five people, each containing engineering, product, and team management talent, and not enforce conformity across project teams over team productivity and happiness.
Edit: Though honestly, a lot comes down to individual preferences. A lot of engineers love being handed a style guide. A lot of engineers love doing tasks off lists.
The problem as I see it is software is not developed as interoperable "components," and it's getting worse. At least you can store a text file on your hard drive, sync it with Dropbox, and edit it with the editor of your choice — meaning app, file format, and storage are separate concerns — but for a web app or cloud-backed native app, these distinctions may not exist, as the representation and storage of a document are completely hidden. Apps have always been pretty monolithic to start with, often with proprietary file formats and limited interoperability. Then there are social networks. Theoretically, Facebook, LinkedIn, et al. could all use a common protocol analogous to SMTP.
Email and the web are success stories of standardization and interoperability. Browsers are very highly interchangeable for a very complex document type! However, it's made less exciting by the fact that the web is being used to deliver software written to a standardized API, not to collaborate on documents and information using standardized formats and representations, and not to connect and communicate using common protocols.
The relationship between interoperable software components and making technology available to society: When we have a ubiquitous standard and a go-to, legally usable implementation for X, I feel like we can say we "have the technology" to do X, as a society. For example, we have JPEG and libjpeg. We have the technology to compress (to JPEG's level of ability), store, and exchange images. Is the technology to, say, collaborate in real-time on a spreadsheet available to society? Is there a go-to implementation and a document explaining exactly how it is designed to work?
I'm not saying the world is wrong and should be a different way (e.g. social media sites should all use a common protocol). Obviously there are reasons we got here, and there is no simple argument that things could or should be drastically different. If the root-cause analysis were continued, I would look at how software is developed, how it is funded and monetized, and so on. Nobody was funding OpenSSL development, for example, even though it was a ubiquitous implementation of a ubiquitous standard and a great example of everybody reusing the same component. Companies like IBM and Microsoft, selling suites of business software in the 20th century, were building monolithic office solutions and not small interoperable tools, for business reasons, while Unix took the polar opposite philosophy.
Calling people out for calling people out on grounds that it’s un-American seems to be what this article is trying to do. There’s still no right to have a TV show or right to not be yelled at.