Depends on what you're working on and on if you're defining "getting stuff done" on a macro or micro scale. For large flagship missions, 2 years is nothing. The scale of work and level of verification required by these projects is massive and takes time. You've only got one shot to get things right with billions of dollars on the line, don't rush it.
High-assurance isn't really the culprit. It's more of a funding issue. If long NASA programs could save part of the first year's budget to use the second year, things would go a lot faster.
You might get hired into an overstaffed team and not do that much for a year until it's crunch time and then you're underfunded so it takes an extra year. Arguably you spent three years to achieve one year's worth of accomplishments.
Curious as to how you would define this as doxxing? The information contained in this "hack" is just an archival of all publicly-posted information on Parler, it is comparable to someone archiving my LinkedIn page and calling it doxxing.
I have not seen any indication that private messages are included in this. As the person indicates, phone numbers are only included if they were posted on Parler by the users themselves, but yes from what I can tell the IDs are the most "private" part of the leak. Although one could argue that they are still "public" given that Parler publicly exposed the information.
The article itself never defines "messages" and, from context, it seems like they referred to users' [public] posts as "users' messages" -- not DMs/PMs.
EDIT: A clarification on Twitter from ~9h ago:
"since a lot of people seem confused about this detail and there is a bullshit reddit post going around:
only things that were available publicly via the web were archived. i don't have you e-mail address, phone or credit card number. unless you posted it yourself on parler."
>I am now crawling URLs of all videos uploaded to Parler. Sequentially from latest to oldest. VIDXXX.txt files coming up, 50k chunks, there will be 1.1M URLs total: https://donk.sh/06d639b2-0252-4b1e-883b-f275eff7e792/
>This may include things from deleted/private posts.
"Private" posts are posts shared to specific circles AFAIK, not the classic definition of 1:1 DMs. They're still semi-public, a bit like Google+ Circles.
By "messages" they mean public posts directed at other people, like I'm 'messaging' you right now. It's a misleading title that was meant to sensationalize the 'hack'. It seems like all this amounted to was a simpler way to scrape public posts.
To be fair, I believe the controversy began with disagreements over the previous maintainer's use of unsafe and spiraled from there. So not entirely non-technical.
In addition to what AnimalMuppet said (fixed bounds on loops), you also have to be careful to avoid blowing the stack with limited memory + lots of running processes
Thank you Salvatore! You have been an inspiration to me as a young programmer and have opened my eyes to the wonders of OSS. Excited to see whatever you do next!
