I feel like it has something to do with the fact that there’s less content, so when you post something, it’s actually going to be seen by people.
I didn’t post or comment anything the last couple years on Reddit, largely because it increasingly felt like shouting into the void.
I am/was in the same boat as you: For a long time, I just didn’t care that I was giving away a bunch of information in return for convenience, and didn’t get why people cared so much.
I don’t really know what triggered it, but at some point I became painfully aware that the only goal these companies have is to squeeze every possible penny out of selling me. I started noticing that the stuff they ask you to confirm is 95% stuff they want because they can sell it, or use it to get you hooked to their service, and 5% (at best) stuff they need to make the service good for you.
This triggered a change in my perspective: Now it pretty much makes me sick to my stomach to think about all the companies that are drooling over me, trying to make a buck by getting me to click something I’m not actually interested in, or don’t actually need.
These people have a vested interest in manipulating me, and by giving them my data, I’m giving them the tools to do it. I don’t want to be manipulated or sold as a product: That’s what made me start caring about protecting my data.
This will sound dumb, but I’m saying it sincerely.
I’ve had similar issues (without getting into details), but what worked for me was getting outside a couple times a week. By that I mean bringing a tent or hammock + tarp and sleeping outside a couple nights a week on workdays.
To be specific: I sleep outside Monday-Tuesday and Wednesday-Thursday. On those days I also make my dinner at my campsite. What I’ve found is that my brain goes into a much more “primal” state of “monke outside in cold, monke get shit done”, and that it propagates into my day and week.
The barrier to this is of course actually going outside, but I’ve been able to get to a place where I have a “deal with myself” about those two nights a week. I always have my pack ready, so it’s just about grabbing it and heading out- I think that’s key.
I’m not saying this is a solution for everyone, but it’s done wonders for me. As of now, I get restless and feel bad if I’m in a situation where I can’t get outside at least once a week. It brings me a peace of mind and will to get stuff done that nothing else can.
That’s what major versions are for - breaking changes. Regardless, you should probably be able to fix this with some regex hackery. Something along the lines of
new_file_content = re.sub(r'(?<=\bprint)(\s+)(?!\()', '(', old_file_content)
new_file_content = re.sub(r'(print\(.*?)(\n|$)', r'\1)', new_file_content)
should do the trick.
For someone starting out, I would say that a major advantage of Python over any compiled language is that you can just create a file and start writing/running code. With C++ (which I’m also a heavy user of) you need to get over the hurdle of setting up a build system, which is simple enough when you know it, but can quickly be a high bar for an absolute beginner. That’s before you start looking at things like including/linking other libraries, which in Python is done with a simple import, but where you have to set up your build system properly to get things working in C++.
Honestly, I’m still kind of confused that the beginner course at my old university still insists on giving out a pre-written makefile and vscode config files for everyone instead of spending the first week just showing people how to actually write and compile hello world using cmake. I remember my major hurdle when leaving that course was that I knew how to write basic C++, I just had no idea how to compile and link it when I could no longer use the makefile that we were explicitly told to never touch…
Yes, it’s a field. Specifically, a field containing human-readable information about what is going on in adjacent fields, much like a comment. I see no issue with putting such information in a json file.
As for “you don’t comment by putting information in variables”: In Python, your objects have the __doc__ attribute, which is specifically used for this purpose.
My test suite takes quite a bit of time, not because the code base is huge, but because it consists of a variety of mathematical models that should work under a range of conditions.
This makes it very quick to write a test that’s basically “check that every pair of models gives the same output for the same conditions” or “check that re-ordering the inputs in a certain way does not change the output”.
If you have 10 models, with three inputs that can be ordered 6 ways, you now suddenly have 60 tests that take maybe 2-3 sec each.
Scaling up: It becomes very easy to write automated testing for a lot of stuff, so even if each individual test is relatively quick, they suddenly take 10-15 min to run total.
The test suite now is ≈2000 unit/integration tests, and I have experienced uncovering an obscure bug because a single one of them failed.
This is a very “yes but still no” thing in my experience. Typically, I find that if I write “naive” C++ code, where I make no effort to optimise anything, I’ll outperform python code that I’ve spent time optimising by a factor of 10-30 (given that the code is reasonably complex, this obviously isn’t true for a simple matrix-multiplication where you can use numpy). If I spend some time on optimisation, I’ll typically be outperforming python by a factor of 50+.
In the end, I’ve found it’s mostly about what kind of data structures you’re working with, and how you’re passing them around. If you’re primarily working with arrays of some sort and doing simple math with them, using some numpy and scipy magic can get you speeds that will beat naive C++ code. On the other hand, when you have custom data structures that you want to avoid unnecessarily copying, just rewriting the exact same code in C++ and passing things by reference can give you massive speedups.
When I choose C++ over python, it’s not only because of speed. It’s also because I want a more explicitly typed language (which is easier to maintain), overloaded functions, and to actually know the memory layout of what I’m working with to some degree.
A protein is like a really long chain of simple monomers (amino acids), that you can think of as a long string of differently coloured beads. The ordering of the beads somewhat determines how the protein functions, but the major factor that determines it is how this long string is bundled up, i.e. “folded” (think of a ball of yarn).
A DNA sequence tells us the sequence of the amino acids in a protein, but tells us nothing about how it is folded. It is of great interest to compute how a protein will fold, given its sequence, because then we can determine how and why it works like it does, and use gene-editing techniques to design proteins to do the stuff we want. This requires huge amounts of computational power, so you get the fold@home project :)
Thanks for contributing!
Possibly a poor translation from my side: I’m referring to the “head office” of the university, i.e. the group of people under the direct leadership of the principal, who have the highest administrative authority at the university.
A professor at my university tried that, but the students quite quickly made a huge fuss, got the principals office involved, and the universities lawyers informed said professor that what she was doing was illegal, and that she should stop before she got any more trouble. She stopped.
To be fair, the result of this calculation only depends on the area/volume ratio of the human. I used the specific cylinder, because humans are roughly cylindrical, and have a volume of roughly 100 L. The surface area of a regular human is probably a bit larger than that of a cylindrical one though.
I’m actually a chemist, thankyouverymuch
#Chemistry Is When There’s Too Many Electrons For The Physicists
;)
The math actually says that we might quite possibly get nuclear stuff. I checked because at first I intuitively thought the same thing as you.
Assuming
Volume of displaced air: ≈ 100L = 0.1m^3 At atmospheric conditions: ≈ 4 mol
Surface area of cylindrical human: ≈ 1.58 m^2 Diameter of nitrogen molecule (which is roughly the same as for an oxygen molecule) : ≈ 3 Å Volume of monolayer: ≈ 4.7e-10 m^3
Treating the air as an ideal gas (terrible approximation for this process) gives us a post-compression pressure of ≈ 45 PPa (you read that right: Peta-pascal) or 450 Gbar, and a temperature of roughly 650 000 K.
These conditions are definitely in the range where fusion might be possible (see: solar conditions). So to the people saying you are only “trying to science”, I would say I agree with your initial assessment.
I’m on my phone now, but I can run the numbers using something more accurate than ideal gas when I get my computer. However, this is so extreme that I don’t really think it will change anything.
Edit: We’ll just look at how densely packed the monolayer is. Our cylindrical person has an area of 1.58 m^2, which, assuming an optimally packed monolayer gives us about 48 micro Å^2 per particle, or an average inter-particle distance of about 3.9 milli Å. For reference, that means the average distance between molecules is about 0.1 % of the diameter of the molecules (roughly 3 Å) I think we can safely say that fusion is a possible or even likely outcome of this procedure.
I am now sitting on the wing of a plane that is about to take off. Gonna try to Tom Cruise it. Will post updates soon.
To be fair: If you live in the south, it doesn’t make much sense, but if you live a bit further north it’s the difference between getting up when the sun is a a reasonable place, or getting up in the middle of the night (winter) or the middle of the day (summer). I want it to be light out when I’m awake, not when it’s sleeping time.
Turns out it’s easier to adjust the clock than to say “work starts at 9 in the winter and at 8 in the summer”
This put words to thoughts and feelings I have had for a long time, but have not been able to express accurately. Thank you, well written.
The whitespace doesn’t bother me at all, but holy hell! Any time I’m trying to understand a Python program/library that’s anything above a couple thousand lines of code, I instantly feel a burning hate for dynamic typing.
I love Python for scripting- in large part because of dynamic typing. IMO it’s just not a language made for building large infrastructures.