Not true for everyone. I learned Rust from The Rust Programming Language ("The Rust Book") and "Rust for Rustaceans." Sure, coming from C/C++, I could have learned the syntax online but learning best idioms and styles required the time and commitment to read a book cover-to-cover. In fact, I've probably read each page in "Rust for Rustaceans" at least twice to ensure that I understood some of the more subtle points. I could have developed a half-baked notion of how the borrow-checker worked by fooling around and reading blurbs on Stack Exchange. But Rust for Rustaceans made clear the more subtle points that might have taken years of tinkering to understand. Thank goodness people still write excellent books on computer programming.
I have a gut feeling that human as a creature learns better when looking at the information from several different angles, both physically and mentally. Been physically I mean looking at the same concept on screen and on hard copy books, perhaps taking notes and mark relevent sentences with a highlighter. Similarly, seeing a concept on physical book and write some short code snippet is viewing the concept from different mental angles. Though I don't have a proof for that and have yet to find a formal research on this topic.
The pedagogy suggests that you retain more when you also have a spatial element to what you are reading - eg you recall not only what the text was but where exactly on the page you read it, and perhaps also how far through the book it was.
Textbook designers know this and use images, callout boxes and insets with case studies/graphs to break up text on pages so that your brain gets extra context to map 'what' to 'where'.
This is (imo) why infinite scroll and mixed order algorithm feeds are such brainrot (even if you are looking at educational content). You try to recall something you read but it was in an ephemeral location in an always changing stream of content.
This is true: a way to remember things is to construct a “memory palace” in a place you know well, where different pieces of information correspond to different locations inside the building.
The solution explorer from Visual Studio flashes into my mind when I think about the codebases I'm most familiar with, and thinking about the code makes the code file come to mind like it's a big piece of paper and it's all represented physically in some form in my mind. I wonder if the way this happens acts like something of an exploit to get those physical textbook benefits.
> I have a gut feeling that human as a creature learns better when looking at the information from several different angles
Ever write a piece of code, pore over each line, test the hell out of it, and only when you actually submit the PR and see the diff rendered in your review tool that you spot some totally bone-headed thing you've done?
Viewing a familiar concept in a new context gives you new insights with surprising frequency. Context shifts the priors in the mind. That's why, yes, combining reference/LLMs/tutorials and comprehesive pedagogic tours on rails gives you the best perspective on a new domain.
(BTW: it's due to this effect that company offsites and retreats are good investments, not wastes of money.)
Absolutely. Whenever I learn a new thing I'll always approach it from different angles - sources from people with varying skill levels (it can be useful to know how another beginner dealt with something!), video form, written text, reading the theory, seeing the applications, trying it yourself in various forms, different constraints etc. For example, since we're on hn - writing some data structure or algorithm you're learning in a few different languages. Doing all this helps massively with building up to true understanding.
(cooking - when learning a new recipe, I'll always find a few versions from reliable sources to compare, see what they have in common, and try to understand the reasoning behind differences)
I learn the same way but there are different people who learn in different ways. Also some people come with some concepts already understood from past experience or education, it’s easier for to pick things up without needing various angles.
Getting a book is my goto to learn anything new. I taught myself PHP and ended up finding a book 4 years later when I was looking for an answer to something. On the next page was something that would have saved me tons of time so I read the whole book.
Since then I’ve read books on Ruby, Go, Elixir, Docker, K8s and a lot more. By far the best way to get a semi complete understanding of anything without scraping together data from the internet yourself, because you won’t easily know the gaps.
My method is to get some hands-on experience first with the technology: Tutorials, Getting Started pages, the first chapter of a book. The fumble for some time and getting exposed to various sources of information. Then I take a book and skim it from start to cover, stopping at interesting bits. Then I reread various parts.
Sometimes I start with reading the books. But I already known I won't retain anything deeply. But it will gives me all the right keywords to learn more about the technology.
It always amaze me when I see fellow programmers struggle with problems that could have been solved easily by just reading that introductory book on the subject.
I came here to say almost the same thing. I've been learning rust in my free time because I don't do enough programming at work to scratch that itch any more, and I've been using the rust book as a reference.
Thanks for the rec for "rust for rustaceans" I'll have a look into it.
I've only been using chatgpt for points where i'd normally go ask another dev for another set of eyes to debug something, otherwise all my learning and doing has been mostly the rust book, crates, and blogs about rust, ecs, roguelikes etc etc. It's been so fun!
There is necessary complexity and un-necessary complexity. Often the modern world seems to be layering on un-necessary complexity and frequently this is not to the individual's benefit. Consider for one, picking health insurance. It should be easy to line up 5 or 6 plans, compare them on coverage and price. However, it is against the insurance companies interest to compete directly. Much better to make it so complex that the average consumer can't compare realistically products. (Doubly so since we don't know what is covered until the doctor asks.) The government could make it easier on consumers by clearly defining coverage levels and allowing companies to compete on price.
This is why it is good lab procedure to always "run a blank." A blank is simply a sample that is constructed exactly like a real sample but without the thing you are studying. This way you quickly learn about contamination from tools/gloves/environment etc.
Here's a very naïve example to help illustrate how you can do a "blank" (a control).
Say you're testing a sample of water in a test tube. Repeat all steps in exactly the same way, but use distilled water. You can even do all the steps and use no water! (Including having an empty container and pouring nothing from the empty container into the test tube).
By doing things like this you create samples that allow you to look for contamination. How do you know that the thing you're testing has microplastics? (Or whatever) because it has more than the blanks/controls. That's it. Congrats, you've isolated a variable in your experiment.
Btw, this is pretty common practice. In fact! Here's a video of someone doing exactly that "nothing" control looking for microplastics. Those steps are done at 10:20.
> Repeat all steps in exactly the same way, but use distilled water. You can even do all the steps and use no water!
This is where I get lost. Maybe I don't understand what a blank is.
If you have access to distilled water that you have excellent reason to believe is free from what you're detecting, then great. But my point is we don't have access to animal flesh guaranteed to be free of microplastics, do we? Because they're everywhere in the environment.
And if you use no water at all, it seems like you're missing the entire vector of contamination from acquiring and transporting the water. E.g. if the water container is producing contamination, then your blank of no water isn't revealing the source of contamination! The blank isn't helping at all.
I don't have any issue with the concept of a blank sample when they're feasible. My issue is, I don't see how you can produce a blank sample of animal tissue without microplastics specifically because microplastics are everywhere in nature, and I don't see how a slide with zero animal tissue at all is a useful blank.
> If you have access to distilled water that you have excellent reason to believe is free from what you're detecting
Don't make assumptions.
> we don't have access to animal flesh guaranteed to be free of microplastics, do we?
Don't make assumptions.
These two assumptions could potentially be at odds.
> And if you use no water at all, it seems like you're missing the entire vector of contamination from acquiring and transporting the water.
Don't use water? Use another liquid that doesn't interact the same way. I gave examples, they are clearly non-exhaustive.
I don't have an answer for you for the exact process but I'm also not a scientist working on these experiments. But the people who are doing the experiments are. They know the answers to these questions. A lot of it is going to be detailed in the papers but some won't be because it's more common knowledge among the niche, but you'd likely learn it if you pursued a PhD in the domain
Just so you know, the tone of your comment is extremely off-putting.
I don't have the slightest idea why you're rudely telling me "don't make assumptions", especially if you don't have additional information to add. And the suggestion to "pursue a PhD in the domain" if I want answers is exceedingly obnoxious.
If you don't have helpful answers, you don't need to leave a comment. You don't need to say that you don't have answers but add a bunch of rude sentences while you do it. Better to just not reply at all.
> Just so you know, the tone of your comment is extremely off-putting.
Didn't mean too, but if we're speaking about tone then it's worth noting you're being overly defensive. When you were trying to seek clarification you're approaching it in a combative way. As if from the stance that you're right and I'm wrong. I'll admit my patience quickly thins when talking on the internet as I just don't want to argue.
Also, you're well known here (why I'm responding now) and I think that also makes it important that you help set the culture here. To act in good faith like the guidelines illustrate. I'm not accusing you of arguing in bad faith (there's a lot of middle ground) but you should take just a few more seconds to consider an alternative interpretation (e.g. if your instinct was to interpret my ask for stronger good faith as an accusation of bad faith then you interpreted as the weakest version rather then the strongest)
I have a point here. It is that nuance and small details matter.
> I don't have the slightest idea why you're rudely telling me "don't make assumptions"
I'm sure I could have said it better, by my tone was neutral. I'm not a LLM, and I'm not going to preference everything with "brilliant" or "great question", I'm just going to respond. *I'm not calling you dumb*, I'm just pointing out your error.
The problem with your understanding is that you are making erroneous assumptions. This needs to be pointed out to get you unstuck.
In science it's all about assumptions. People frequently throw around the term "from first principles" but you don't really hear that from scientists. First principles are hard to find. You derive them. Your first principles are your axioms. Your assumptions. They always exist, explicitly or implicitly. The problem is you probably didn't recognize you were making assumptions. That's fine though, because it's common. It's hard to avoid.
> If you don't have helpful answers
You're right. But the thing is I was being helpful. Maybe not in the way you wanted, maybe not optionally, but I'm human.
> You don't need to ... add a bunch of rude sentences while you do it.
I didn't.
Theres no name calling.
There's no attack.
There's not even an implication that you're dumb.
I did assume you don't have a PhD in chemistry or biology, but I'm pretty confident given your question (was I wrong?). I also said I don't have that qualification (but I do have lots of experimental science training) and that there were things I don't know either. So if you interpreted me as calling you dumb for not having that background then you need to recognize I would have been saying that about myself too! And that you didn't need this comment to infer that.
> Better to just not reply at all.
Maybe. But that could apply to your own comment. You wrote yours to try to resolve things, right? That's why I left this comment too. But it's up to you how you interpret it.
So if you're studying slices of e.g. brain to look for microplastic particles, what would be a material with similar properties, that you would then go through the same steps of preserving, preparing, slicing, mounting, etc.?
I'm genuinely curious. Are there standard widely used stand-in materials for animal flesh, for plant materials, etc.?
The point is that blank lets you measure that level of "background" contamination, which you then use to correct the measurements made on actual samples.
Suppose you measure around 100 plastic particles per unit in your blank and 1000 in a sample of A. This suggests that A enriches (sheds, etc) microplastic particles. On the other hand, if you found (say) 101 particles/unit in a sample of B, you'd conclude B doesn't do that.
But in your example you still don't know if it was your testing process that shed 100 plastic particles or if your distilling process shed 100 plastic particles, meaning you don't actually know if B was or was not the source of the plastic particles. Was it your testing process that introduced those 100 particles, was it the distilling process that introduced them, 50/50, or something else?
B would be inconclusive against what you'd hope to be some kind of background, as its not significantly more but one couldn't conclude the source didn't shed that 100 because you don't actually know if in the blank the 100 particles of contamination was definitely your testing process or the source material genuinely having 100 particles of contamination.
I do agree though, in the A case one could pretty easily conclude whatever generated that sample is adding way more particles than an attempt at a baseline/background.
> B would be inconclusive against what you'd hope to be some kind of background
Correct. And this is why scientists use null hypothesis testing. You disprove things in science, not prove them. I think that's why you're confused. In the first situation you disproved that it comes from the background
I interpreted that sentence as more casual language. Maybe I'm wrong to assume that. But I didn't write it either.
Either way, the difference didn't matter to answer your question. Them getting that part wrong doesn't make the other part wrong nor hard to understand.
So why even bother mentioning the distilled water? And if you're testing an aqueous process don't you pretty much need some fluid to put through the process?
So then maybe don't give the first if you know its a flawed example? Its not that hard to grasp.
> You don't need some fluid
Entirely depends on your testing procedure, and not something always true. Like in the video you posted he pretty much needs to have some kind of fluid through the process. Otherwise, he'd be missing out on contamination in the process of artificial mastication, running through the filtration process, etc. Sure, examine a dry and plain filter as well to see what the filters look like and ensure they're not just completely covered in particles as well, but you're then missing out testing quite a lot of the rest of the process.
> So then maybe don't give the first if you know its a flawed example?
It's not a flawed example. As you can understand from the other poster talking about baselines.
> Its not that hard to grasp.
I agree!
> Like in the video you posted he pretty much needs to have some kind of fluid through the process.
And it looks like you're understanding too!
But if he used a different process he could have used it dry. There's a lot of ways to skin a cat. Different ways create different constraints.
So I'm confused here, did you just want to argue or did you actually want to understand? Because at this point it seems like you understand. And frankly, I don't want to argue
Sure seems like you do with all your passive aggressive takes of asserting I'm confused or can't read or can't understand things and that I lack understanding the most basic scientific concepts like null hypothesis testing.
My question was simply:
> But how do you know your source of distilled water isn't also contaminated?
You could have just replied with "you don't, and it doesn't always matter depending on the questions being asked and the processes being used" but instead you've drawn it out to this many comments.
Instead you chose to say "you read the rest of my comment" instead of actually answering my question and then talk down to me over and over.
Some of the other comments seemed to be acting like running a blank is a fool proof way to just make sure you get a clean answer, and my point was to show there are still limits to "just run a blank". And that's shown by the sibling thread here with the other poster thinking if your blank has 100 particles and your test sample having 101 that means the test process obviously introduced the particles, which is a flawed understanding of the results of the test. The results are inconclusive, it did not prove the sample contained no particles to start.
I don't believe the point is to construct a blank without them. Rather, the point is to capture what is already there (contaminants) so you can calibrate during the real sample.
Both things can be true. A better O-ring with the same joint might have prevented the disaster. A better designed joint with the same O-ring might also. Feynman knew that a little theater would go a long way. The O-ring explanation, albeit a partial explanation, made for good theater.
Maybe not so much "oblivious to safety" as "oblivious to probable risk." We worry to much about low risk events (like airline flights) and don't worry enough about higher risk events (like trips-and-falls, driving a car, poor diet...)
I really enjoy how Julia handles images. The abstractions really streamline developing image processing algorithm that are independent of pixel representation. Like so much of Julia, the first time I saw it, my mind was warped. Julia is worth learning if just for all the clever design choices.
If the drive isn't encrypted, is it possible that controllers use some kind of encoding to balance out the number of bits, so that there's not a long run of 0s or 1s?
And yet all countries with socialized systems pay less per capita for healthcare than we do and pretty much all have better health outcomes. Further privatizing our system will only make it more dis-functional. Healthcare isn't a normal marketplace. * When you really need it, you can't shop around. * There is a knowledge asymmetry built in. * A civilized society can't just let poor children die of preventable causes.
This is just the lazy comment of someone who believes all the right-wing propaganda about government. In my experience, government employees take pride in doing a job worth doing and doing it well.
reply