"documented" and "twitter" in the same sentence is so weird. There no worst format for keeping an history of things. It's ephemeral, hard to browse or search, and terrible to format.
It’s almost like we have different standards for different types of engineering.
The devs writing code for the next social media app operate under very different standards than the ones writing code for nuclear reactors. And that’s ok.
nuclear engineering is a direct combination of applied physics, civil engineering and mechanical engineering, all having a long history.
SE started out from mathematics, but the hardest problems are not related to it. We're only pretty good at nailing the things directly from mathematics like algorithmic complexity or distributed system guarantees.
Pretty sure this is because most of our public investing goes towards spying programs instead of more funding for places like NIST.
Not to mention funding for governments that actively sell exploits to other nations. Standards seem to be left up to the industry. I saw the Kubernetes hardening guildelines from NIST a while back that was cool.
My $2700 dell xps keyboard died less than 2 years after unboxing. Dell tech came to fix it after 2 months of cat and mouse with their support. He changed all the parts, and the machine stopped booting, then he left. One month of battle later, he comes back, and plays the same song, then live.
4 months after the initial blip, laptop is still dead, there is talk about a replacement but they will get back to me in 48h. It's been 2 weeks.
If dell does that, I guess we can forgive a noob player like ff.
I can write 10000 words on the spot on any random word picked out of the dictionary. Even a one I don't know at all.
Friends loved to test me on this, picking up some BS topic and see if I can come up with a scenario or a song. Then after a few minutes of my rambling they get bored of course. Having something to say doesn't mean it's interesting.
My problem is rather to learn to shut up about things and accept it's usually wiser to not have an opinion on most things.
The vast majority of words do not need to be spoken or written, but it's hard to do for me.
For me not really, it's just matter of spending more time on it.
If I spend 20 minutes, I will just produce BS. If I invest more time and energy, something good will come out.
When I was a kid I always assumed everybody was the same: you could always express what you had in mind. Took me years to realize not only it's not the case, but most people actually don't use words for their meaning at all.
Once I got that, my oral communication improved tremendously, but writing stayed mostly the same. Oral can be messy, sometimes it's even better than way. On paper, though, being clear is a virtue.
And if you can't be clear from the beginning, just babble until your brain gets in the flow, and you'll get to something eventually. Then strip the useless part, clean up the good one, and you got a winner.
I understand how others can suffer from writer's block even though it does not pertain to me. Have not happened and never will. Typically those who suffer writer's block go into writing on the false premise that all writing should be inspired. Like the first sentence you type on a blank page should be heavenly divine. There is this false notion in our society of a true, mythic writer that is a muse-inspired drunkard puking paragraphs reeking of genius. If that's how you think about writing then, of course, writer's block will be common.
When I write, the premise is I attempt to turn shit to gold, eventually.
Closer to the truth is as described in this article, writing is more like blind plumbing work. It's very revisional. Whole paragraphs and pages are reworked and outright deleted left and right. The final script is rarely in the order you started. Then your editor goes to work, butchering your baby. It's very painful, but you know this is the way to end up with something the reader finds readable.
Reading a published novel as a wannabe author, you must keep in mind that it's revised to perfection. Repeatedly hammered like a Japanese sword. Writing is definitely a forging process and not magic.
> Reading a published novel as a wannabe author, you must keep in mind that it's revised to perfection
Yes, in fact, I'm so used to that I sometimes edit my HN comments 10 to 15 times, and get frustrated when the "edit" link disappears.
But the initial one is always easy to write. I don't wonder "geez, what could I say?". It also often sucks, full of typo, things that could be badly interpreted, and so on.
Funny thing is, I'm currently learning to let it suck. Invest less energy. And as this thread proves, I'm failing miserably at it :)
It's the same, the only difference is filtering and shaping, and keeping up at it. It's a cycle. Babble, filter, shape. Then babble again. Sometimes you skip directly to write well shaped words because you are in the zone. Sometimes you just embarrass yourself because you are in public, and there is no opportunity to shape and filter.
But the process is the same, at least for me.
I assume other people do it differently, but the point is, writer's blocks seems alien to me. As long as you are not in a coma, I don't see how your mind cannot come up with something. And as long as it can, something worth committing too can be found.
It's not like sport when you have an actual physical limitation. You brain is literally a machine to produce ideas. It does that constantly, in mass.
Everybody has it, because everybody have weird dreams when they sleep.
Haha, this thread is amazing to read! People who reply to your post try to explain why the writer's block is a thing, and inadvertently demonstrate the reason it is a thing for them and not for you.
They talk about how easy it is to write random words and how hard it is to write well, and you keep explaining that you're supposed to remove the filters, start by writing random words, and then edit until it's good.
I think that's the difference between the people who have writer's block and the people who don't. People without the writer's block are able to relax their filters, people who suffer from writer's block are trying to write well right away, and it's hard and painful.
Ha said that, even understanding your advice consciously, I still find it incredibly difficult to apply. Logically, I see that there's no reason to be ashamed of writing a bad draft, I don't feel like I'm afraid of being judged by people, or like I judge myself, I think that I want to be able to just babble until I stumble upon something good I can refine. But for some reason, my brain just refuses to do that.
Maybe it's difficult because my brain feels like "babbling" is a waste of time and energy, and I always give up before it gets good. Maybe because it's difficult to motivate myself to do things when I don't have a plan, don't feel like I have control over what's going on, don't have the guarantee that my efforts will pay off. Maybe it has something to do with status or confidence or insecurities that apply these filters whether or not I choose to. I dunno. I know that these reservations are silly, but I see why people struggle with it, I do too.
I think that relaxing the filters, letting go of control, and trusting in your brain's ability to generate random words and make them good later on is also a skill, and some people find it easier than others.
But you're writing about a subject you know about - what about something new, something actually creative? Writing fiction? A subject you know nothing about and for which you can't look up anything?
The thing you are describing is not the opposite of writer's block. It's something orthogonal to it, at least in my experience. I'm also quite capable of stringing together endless seemingly coherent texts about anything when there are no true personal stakes involved.
However, when trying to tell a story or covering a subject that I really care about, that's a whole other ball game.
For me it's not. If the subject matters, the same process can be applied, and eventually something good emerges from it. You just filter the crap out, shape it, and you have the base for something great.
The good old advice of "just start writing" is easy to follow when words flow naturally.
Oh, but good writing can come out of it more easily than just trying to come up with something good from the start.
It's easier to filter than to shape. And easier to shape something already filtered than shaping from a blank page.
Also, not all writing have to be good. A lof of them already have value if they are not bad.
After all, writing for the purpose of writing is a beautiful endeavor, but writing for sharing information is a great in itself, and a perfect but non-existing reference will always worse than a dry but at hand paper.
Giants spent their energy speeding things strategically:
・ Google wanted Chrome to win, so they spend their effort on JS.
・ Facebook was a PHP shop, so they worked on make it fast.
・ MS had to promote .net, so they optimized c#.
Now you also have to remember that:
・ it's a hard problem
・ python is not a performance oriented language, so it was not a priority
・ when data science became popular, c-extensions were usually enough to get the perfs you wanted
・ once you have a working python code reaching perfs limit, you could start a rewrite in a fast compiled language (Google did it with go, dropbox with rust, etc). But this could take years before you need it. Youtube ran fine on PHP then Python for almost a decade. Python can take you very, very far. In fact, I'd say half the time somebody says python is too slow for them, it's because they are doing something wrong. Case in point, I have a half-million users/day streaming website running on Python. It's been running for 10 years, and needs only one dev to maintain it.
・ there are actually a lot of improvements on tooling for perfs on python. Multiprocessing have fantastic pools and shared memory. We have asyncio (not to mention uvloop). c-extensions release the GIL, so you can use threads for parallelism with numpy. Most people are just not aware of it.
・ Python is very old, 4 years older than java. It has been design way before multi-core laptop were a thing. And so the GIL is everywhere.
・ python is in a very unique position: it's the second best language for anything. Meaning it's been used by data scientist, web devs, geographers, sysadmin, pen testers, os maintainers and biologists alike. They all have very different tooling, dev envs and workloads. Speed doesn't mean the same things for all of them. E.G: a slow starting JIT that speeds up a web server would destroy the use case for cli tools. Mercurial has not computational speed problems, but import time is killing it. But lazy imports would make debugging and new comers learning curve harder. What if they speed up things for them, but slow them down for you?
・ 2->3 made the entire community change averse. And to get speed, you need to break the C api somehow. Hence the Handle Python project.
So the previous attempts to speed up Python were by either interns, or people doing it out of passion/curiosity. A lot failed (unladen swallow, pyston1, etc). Some were successful but only for some dimension of speed and/or doing some compromises (pypy, stackless...). Some are still WIP (Pydgin, pyston 2..). The solutions that succeeded the most are actually side stepping the problem (cython, numpy, numba, dask) but usually became popular although some very good projects still deserve more light (nuitka, mypyc...)
It's only now that Python is becoming such a huge deal that MS hired Guido to work on general computational speed for cPython. Now that there is attention, money and dedication on the problem, you can already things moving in the bug tracker (coroutine unwrapping, c stack skipping calls, HandlePython, etc). It's going to take time. Millions have already been invested in V8 to make the JS slug go steroid, so catch up is not for tomorrow.
> What I meant is inline. So inside of a py file, you can rewrite the one function which you identified as the bottleneck. In C or another language.
You can already do that with cython. And there are alternative for rust, nim, go...
That's also why python speed is usually not a priority: you can rewrite your hot spot in another language and keep most of your python code.
Now, I'm glad python speed is now something the right people work on. But there were very good reason it hasn't happen until now.
The way you say it, it feels like "wow, nobody has though of that before!".
> Facebook was a PHP shop, so they worked on make it fast.
Tangent: Facebook's work on PHP was largely a technical dead-end. Their work on HipHop and HHVM was never accepted upstream, and eventually resulted in their forking PHP into a separate and incompatible language called Hack, which basically nobody uses outside of Facebook.
In the meantime, the upstream PHP project hasn't been standing still. The core development team has made a number of significant improvements to PHP performance. By 2015 or so, PHP 7.0 matched the performance of HHVM, and newer versions have improved upon that. (PHP 8.0 added a JIT compiler, for example, which can dramatically boost performance for some applications.)
> MS hired Guido to work on general computational speed for cPython.
van Rossum applied at Microsoft, they took him and he chose that project.
van Rossum had never shown any interest in JITs before. While at Google, he maintained that Python was fast enough. While at Dropbox, he initiated Asyncio (fixed and improved by many people) and integrated typing (Jukka Lehtosolo).
If a fast JIT emerges, it will likely be by existing Microsoft JIT experts. They should familiarize themselves with the cliquish nature of Python, rampant credit taking by those who did not do the work, and sidelining and active defamation of those outside the clique once the work is done.
It could be a major career disaster to get involved with these people.
Youtube can do whatever it wants, but by taking this political stance, it creates a precedent that other actors will use to ask it to censor other political content.
I'm not anti-vax, I've had dozen of vaccines including covid, but I still think anti-vaxers should be able to express themself. Who knows, one day I may realize some doubts were justified.
See, I'd have thought that everybody tacitly understood that YouTube's scale has redefined presentation of videos over the Internet and as a consequence is the premier video archive for all of Humanity. This doesn't erase their fiduciary duties, but it does attenuate them -- archiving and presenting videos (to show ads) is actually how the money is made. But I'll bite -- I'm a credulous idiot who's confused YouTube for an NGO. You are a wise cynic who's come to correct me.
>Their mission is to make money, not to archive the internet.
I assume they remove "violent" videos to appease advertisers. In this case, they did not consider the value of the video being removed, instead prioritizing the safety of the content with respect to the advertisers.
In the large, YouTube's terms of service are structured around retaining an audience (both in terms of individual and institutional choice... Without a TOS that at least nominally says what constitutes offensive content, businesses and schools block access to YouTube and that decreases viewership which decreases revenue potential). They are also structured around being a hospitable place for advertising, and advertising (in particular brand advertising) gets real gun-shy on spending dollars on content that might be significantly off the bead from "wholesome."
Whether or not this video in particular violates the TOS is debatable (though having never heard of this before this link on Hacker News, my naive read on it is that it's simple violent aggression and a display of unadulterated physical violence, which generally doesn't pass the TOS for graphic violence... "Content featuring anything listed above where the viewer is not given enough context to understand that the footage is dramatized or fictional").
Actually in the US YouTube is legally allowed to delete or remove any videos they want to, regardless of whether they might contain evidence of crimes. They would generally only be required to preserve such evidence if given a court order, which doesn't appear to be the case here.
On my Berlin-Poznan trips, I sometimes had a 10s average ping, and an equally absurd packet loss rate. SSH worked great, but the regular internet was unusable.
ping is what the ping program reports, which, depending on the QoS settings the provider has, can be very different from the roundtrip time of packets you actually care about.
Your provider can for example filter out all ICMP packets giving you timeouts for "ping", but you can still reach the host just fine with other protocols. Similarly your provider probably prioritizes protocols that require low latency like VoIP over ICMP packets.