skysight-inc/HackerNews huggingface dataset:
"Wehmut" literally: 'The courage in feeling pain'.

This is powerful. I feel like this courageous curiosity has been the primary virtue or trait that I've been exploring and aiming to cultivate more than any other during the past couple of years.

As a non-German speaker I'd be interested how this relates to melancholy (these to me feel like quite different emotional states).
Big fan of this library. It's much easier than writing these scripts by hand. You can also dump a command line version to use elsewhere with the .compile() function.

For those concerned about extensibility, you can always use .global_args() to pass arbitrary arguments to FFMPEG if necessary. However this library is well maintained.
Tencent open-sources Hippy, a cross-platform dev framework
qmail is an excellent example of isolation and least priviledge security design. But I'd really like to hear how production systems used by major ISPs or gmail work.
Old Reddit isn't slow. It seems to mostly be the new frontend.
HTTPS www skincareadvisor org/aleurier-skin-cream/
Aleurier Skin Cream
What's more, energetic skin has a lot of collagen in it. Along these lines, so as to reestablish your skin, diminish wrinkles, and look more youthful, you need to recover your collagen. Also, that is the thing that this recipe can help with. Aleurier Skin Cream Advanced Skin Care utilizes clinically demonstrated collagen boosting fixings to enable your skin to look and feel extraordinary! Besides, on the off chance that you persistently utilize this item, you should set yourself up for better, more youthful glancing skin later on, as well. Snap any picture to begin now!
https://www.skincareadvisor.org/aleurier-skin-cream/
Powershell and Azure DevOps (Fr)
What if all the employees who took the placebo pills were more productive? It’s still a sugar pills, but you can’t argue with the results.
Pester Infrastructure Testing (Fr)
I'm doing my PhD in HPC (part of my work is in situ stuff). One of the biggest problems is actually IO. But honestly, 250GB isn't that big. I haven't used dask, but I know people that do. I just avoid python for anything I need performance for, C++ is just always going to be faster.

Biased: you might want to look into DOE libraries. For IO I suggest ADIOS2 [0]. There's python bindings too.

One of the biggest things you can do is use a different storage type like BP (ADIOS) or hdf5. These are readable but binary. But to really determine how to speed up your problem you have to know where the bottleneck is. Is it IO or compute? With 100 workers (threads or nodes?) you aren't highly parallelized. I mean that could be a single node if it's threads.

[0] https://github.com/ornladios/ADIOS2
HTTPS www skincareadvisor org/aleurier-skin-cream/
Aleurier Skin Cream
Aleurier Skin Cream The best thing you can achieve for your skin is manage it. In addition, that is what the Aleurier Skin Cream Formula is planned to do. Since, the more you manage your skin now, the better it will look later on. That is the explanation placing assets into your skin right as of now is the best idea. Also, the fixings in this formula are here to help! Starting at now, this thing has fans the world over!
https://www.skincareadvisor.org/aleurier-skin-cream/
2019: The Best Year Ever
Pragmatism is priceless in large scale production systems. I just recently started a new job as a front-end engineer where we use Go for all our backend services. I have never used Go before, and likely won't much in the future either, but I absolutely love how absolutely dead simple it is. You've got conditionals, loops, structs, slices (arrays), and functions, and that is about it. Even though I don't write Go code I can still read, understand, and reason about all our systems. The same cannot be said about your average junior or front-end dev trying to understand Haskell or Lisp or other obscure high level languages.
Maybe Go. Python would suck because of whitespaces.
"Do your own stuff when you've finished your assigned tasks" is dicey for a couple of reasons:

1) You could be in a position where the work "never" ends. For sure, there are a reasonable number of tasks expected to be done at the end of the day, working some fraction of the day's butt-in-seat time; and when they're done, the business runs smoothly. However, recognizing this, businesses will add tasks that could be automated or designed away (e.g., answering the same inane help-desk tickets, which pile up constantly), because they "help" to secure an employee's "engagement" when they'd otherwise be free to study, optimize their performance, or simply socialize. If you're seen doing any of these, rather than the assigned tasks, you'll be docked.

2) It's difficult to bounce between tasks, including from your work-work to your personal work and back again. This is a sure-fire recipe for not being able to maintain, or even cultivate, focus. To add insult to injury, workers are often dealing with a scenario where "availability" is required of them to mask inefficiencies in the business' management or administration. This task could be done remotely, that one could be automated, a third could be grouped with a fourth if someone twisted arms to get the necessary data earlier (as has proven possible on days before a holiday). Allocating the 2 or 3 hours of the day not spent directly on work tasks would then be possible, but not when they're spread out over the course of an 8+ hour day in 10 minute chunks, or eaten up by busy work. "Hurry up and wait" is a productivity-killer.
> You can't really export the game outside of Steam, or use it with Steam disabled for any significant amount of time.

That isn't true for all games. There is this [0] list, but I have no idea about its quality. Essentially there are games that don't use the steamworks DRM parts, so while you do not get a steam-independent installer, those games still work after uninstalling steam (and you could probably watch the installer to make your own for a completely steam free PC).

[0]: https://steam.fandom.com/wiki/List_of_DRM-free_games
Up And Then Down: The lives of elevators (2008)
"Note:" comments are perfectly fine. On the other hand, I've seen at least three distinct definitions for TODO in this HN thread:

- TODO should be a note about behavior.

- TODO should prescribe a small fix.

and yours: TODO should mean "don't worry about deleting this".

These different interpretations and potential confusion they would create make even a stronger argument against TODOs.
This is another example of group-think in scientific research. The same thing happened for decades where low fat diets were supposed to help for heart disease but that has only recently been reversed after decades of indoctrination. This happens all throughout scientific research, where science is supposed to be immune to this, but it's obviously not. So many things we take as gospel, only to be reversed decades later, and it has to do with how things get funded which is unfortunately leading society the wrong way.
Pretty sure he was a celebrity before though, that kinda makes things easier than for the avg joe blow.
No, but the google fossil wear (no idea re: name) watch is great.
This does not add to the discussion. It would be better to post a substantial response or just leave the discussion as is.
Loschmidt's Paradox
You're not wrong, but the opening statement "Zip is now effectively obsolete." is sort of true but not really in a lot of contexts. It isn't something I'd say with conviction.

From your point of view was the implied statement something akin to: "In the context of a high-throughput network transfer program choosing DEFLATE over an algorithm more well optimized for computational weight wouldn't be a good idea." ?
Normally I'd agree, but ffmpeg is a bit of a special case: thanks to its extremely large set of options it has a rather high number of pitfalls: flags that do subtly to wildly different things depending on where they are placed relative to other arguments, for example. Complex filter graphs are pretty gnarly on their own, being a string-based sublanguage all crammed into one argument... it's not totally unreasonable to reach for something just to tame that particular beast.

If this gets you halfway-workable tab completion for the various options of things it's worth it for that alone, vs. diving through the big long page that otherwise contains all the names and orders of arguments to filters.
think that scarce research funding should flow their way because giving any to other possibly-wrong approaches would be wasteful

I heard someone recently tell me how using science to form views on topics (social/psychology/etc) is dangerous, because science is really about funding. AND large donors/entities who can fund science often pick science research projects that sound cool and sexy. They may not be pushing any agenda but do lean toward funding trendy ideas.

So really, science is often biased because of who hold the checkbooks. That really made me think.
Unfortunately true for most scientific communities and the reason why the current academic system is badly broken and talented young minds decide to quit academia before even submitting a dissertation.
Thanks itronitron. I look at both the applicant and the job advertiser as my customers. I want to take the frustration out of the job application process by making it very easy for an applicant to apply and for an advertiser to scan that application in a second.

Thanks for the suggestion regarding minimising the information in a job advert. I had thought of standardising the CV with minimal info but didn't realise that same applies to the job adverts as well.
I'm afraid "don't worry about deleting this" was poorly phrased...but your point still stands
Awesome! HN is a wonderful place to find like-minded individuals :)

sorry if I'm slow to reply, my sleep schedule is all over the place but dad is being discharged soon so I promise I'll get back to you soon, added my email to bio.
I think it's less of a company culture thing and more of a local team preference thing. If the ICs on a team are united, managers are often willing to change things a bit from how they're used to it. It could be just as simple as prefixing a "[Trust]" tag to items that are important and have some priority within developer minds, but product management has no opinion / ability to form an opinion apart from earlier they've agreed on a general "[Trust]" bucket to account for such things. This lets them be filtered out as needed. Worst case, a united team can have a private issue tracker and beef up their estimates to management to account for work management doesn't want to hear about but needs doing nonetheless.

If you don't have either a united team or managers willing to move at all, or even work with ICs collaboratively, you have bigger problems than what you do with TODO et al. If I were in such a situation I'd still use an 'issue tracker' (maybe a local text file) 9 times out of 10, while also looking for a better job.

Issue trackers are slow and I have to work with one of the slowest (it was built in-house on top of a core product never meant for such a thing...) but some are much faster than others. Command line ones can be pretty slick. Still, it comes down to team (and individual) preference and experience (your "very hard"s are never even "hard" in my experience). Even on a personal project that's going to span a decent length of time, I'll take the slowness of adding even a minor issue and the rare risk of grooming/popping the backlog (and all this might just be in a single local text file, very low overhead) only to discover an item no longer applies and taking the second to Never it. It's not only faster for me in the long run but maximizes the incentives for the things I want in a system that I'm tasked with maintaining and improving.
I second this. I'm in the final stage of developing an app for a client, and it's using SwiftUI. The speed with which you can develop the interface is astonishing. Within Xcode itself, you can preview how it looks (i.e. compiles automatically and shows the result), and there's even a simulator integrated into the UI. Next to the preview is a play button so you can click a button, see an animation, et cetera.

You'll bump into a couple of things which require workarounds. For instance, you can only stylize the navigationbar if it's in normal mode, not if it's in the nice large title mode, and you'll have to use the UIAppearance API for that.

I'm also seeing lots of people calling things "bugs" but they actually just misunderstood the new layout system. I haven't seen showstopper bugs. Frustration is, however, unavoidable because it's a learning process.
Why would you grep in a scenario where a note is written because "[the]... code is functional, but if you are going to do another iteration you may want to consider the following improvement or optimization.". It's exactly meant for when you encounter it, it's not meant to be found externally.
That's fantastic!

I have a one man software business but in creating and selling my own product, which has some strong pros and cons comparatively! I've been toying with the idea of taking on some consulting as well. The pivot to get into consulting seems much harder, however.
Restarting the server because the tarot deck said to is certainly a way better reason than the ones I occasionally see in practice - e.g., "because the uptime was unusually high and that seemed suspicious," well did you suspect that it was manually configured and nobody was rebooting it for a reason? That one is an actively bad reason to reboot a server during an outage, at least the tarot deck isn't making decisions contrary to evidence.

Also, if you read the article closely, it's not advising you to trust the deck blindly, it's advising you to use it as a way to think about the problem from a new angle. If you're restarting it blindly based on a tarot deck, you're the sort of sysadmin who's ready to restart it blindly based on finding a five-year-old wiki page with a vaguely similar error message on a totally different platform. Should that be a fireable offense? (Maybe! Or at least maybe the company should find you a different role that recognizes that making decisions about production servers is not actually one of your skills.)
My wife and I do have a weekly one on one. It’s on our shared calendar for 8:45PM every Sunday. We call it a ‘check-in’ because 1:1 feels like unnecessary corporate speak in the context of our marriage.

It’s a chance for us to talk through what went well and what went poorly over the last week. Having it on the calendar as a regular activity means that it never feels like we’re calling the other person out on something, and it means that we never just let it slide because we’re busy with something else.

We’ve been doing it for over a year and a half and have only missed it once when she was at a conference.
And what if I told those employees that the water in the building has been shown to invert the effect of the placebo pills and make them less productive? Now their productivity goes down. See how this can go wrong?

Buying into the bullshit and tying your abilities to something as flimsy as a placebo pill is not a great idea.
This deep simulation of space economics is surprisingly compelling
I'm not really sure what this is, because it just shows a list of files bigger than my phone's screen, which can only scroll a few pixels up and down.
Science is funded:

1. by desire for profit

2. by desire for political gain

3. by charitable impulses by people with money to spare

Each has its problems and advantages. Best if we allow all three.
I think a big part of the reason why people don't care about accessibility anymore is because you can't make a website without someone pulling out a Bible-length list of asinine complaints, and that is for a site "in the top 60% of pages".

I know that I have stopped caring for "accessibility" almost entirely beyond the most obvious things. Most of these complaints are either totally inane and unnoticeable, or will affect so few people over the site's lifetime that I can count them on one hand. I think it's good for people to try and make your website as accessible as possible, but there's a limit to how hard you can indignantly demand people bend over backwards for you.
Many small towns used to have drop-in centers, which acted like community centers where people could spend their day. Public Houses used to fulfill this need as well, but evolved into commercial "pubs" for drinking. Of course the various churches often still fill in parts of the role of community centers in many areas.

As everything gets commercialized and privatized, community can become a lower priority and thus taking care of people who don't pay for anything is no longer something those centers do. Eventually many towns ended up with nothing public at all, and it sounds like McDonalds is filling the need that these places used to do.

An interesting microcosm of this issue is public outdoor seating out the front of businesses being introduced in some city squares. The seats are public, provided by the city, yet because of their positioning it's easy to mistake that they are for the business. When people think the seats are for businesses, they don't feel comfortable utilizing the space unless they're paying the business.

Would you go to a pub without buying a beer? Probably not, so they're no longer Public Houses for the public, and not everywhere has a place that's filled in the need.

Frankly, I think communities are scared of who would show up, and that's precisely the problem. We have cordoned off and alienated our communities into The Paying and The Poor. You don't get to be part of the community unless you're the former.
Yep. Tracker is for stuff that definitely will get planned in. TODO's are just little reminders for when returning to a piece of code some time in the future.

For actual immediate tasks, a TODO_123 with the active ticket number is more practical when stubbing some partially written code.
Actually the signature was almost free, because it was also the nonce for the header, which was the nonce for the rest of the packet. IIRC.
China’s Baidu dethrones Google to take AI language crown
This should be marked as FIXME, not some management savy ###
One can be wary of big money projects while trusting the larger trends, critical reasoning and method itself.
California is thankfully neutering that sort of backdoor access.
Big data is about I/O not CPU

I’m a C++ veteran btw and understand the point but big data is about how to process petabytes of I/O not how to consume CPU.
Learn Go – Beginners | Intermediate | Advanced
It should just follow a retention policy. If no action on it in the last 12 months just automatically close it.

Otherwise issue tracker has thousands of items that the team will never realistically work on.
> That's a terrible advice. When I worked at Google, many code reviews added more TODOs because the reviewer identified a potential source of problem but also correctly decided that fixing it right there was not the best use of developers' time.

I'm sure Google is able to adopt a working ticketing system. If you already have an issue tracker then it makes absolutely no sense to keep a separate out-of-band ticketing repository such as source code sprinkled with TODO entries.

> When code has potential issues, I want it to be marked with TODO which basically says "The original developer was not an idiot, but was working with limited resource and the best way to fix the issue wasn't clear then."

That makes absolutely no sense at all, unless your goal is to simultaneously avoid accountability, poopoo other people's work, and actually do nothing to fix the problem.
In short it is a consequence of everyone became a seller and every conversation became a salespitch. There is never nuance in a salespitch. Everything projected needs to be flawless and beyond reproach, every competition vilified and without merit.

If everyone is competition, there is no more 'us' outside the context of 'them', and you can never show weakness in front of the 'enemy'.

Ultimately it is this projection of everything being a zero sum game that fuels our decend into tribalism.
I agree but I also think that value is pretty marginal.
Obviously less severe but #2 echoes why gym classes always seemed questionable to me.
Consoles also control the hw which means it is possible to make the drm stronger.
> “ The same thing happened for decades where low fat diets were supposed to help for heart disease but that has only recently been reversed”

Oh did not know that. Do you have reference material?
Those things are configurable, though, so new markers are rarely problematic from a tooling perspective. Getting your teammates to agree on using the same markers is perhaps the bigger problem.
It's critical for me too, for exactly the reasons you listed.

RE point 2., it also applies to issue trackers and other "proper" way of encoding TODOs - if I tried to branch out to file a ticket in such situation, or even make a TODO entry in the Org Mode files that always accompany my projects, I'd very quickly lose the flow. Context switch is deadly here.

RE point 5., I try to work through them as I go. I consider this to be a part of cleanup after a main task - I go over all the TODOs in the area I worked in, and implement the simple ones, delete the stale ones, move the serious ones into issue tracker, and leave the rest for future reference.

All of this applies also to FIXME, HACK and NOTE comments - three other types I use. Out of these, NOTE are informative, "seriously please pay attention" comments.

I date them all. I have a Yasnippet for all the above, which expands "todo" into "TODO: $ -- My Name, 2019-12-30", $ being where the caret stops after expansion. Same for "fixme", "hack" and "note".
> Better books have followed in this zeitgeist

Any suggestions?
America has decided only one party needs to be a signatory of a contract and it will apply to both. No consciousness needed because there is nothing to agree to. Everything has already been pre-agreed to. This is the same in our other industries. Good luck if you cable provider, retailer, hotel, airline, landlord, or other service fucks you over. You agreed to some insane bullshit in the thousand page 2pt font popup that probably didn't even load correctly so now you are fucked. At least it's not a matter of life or death there, though, but it sure is a matter of our entire society being structured this way to take advantage of people and fuck them over for money. Police? Oh yes, they are some of the biggest thieves and are allowed not only legal violence, but legal theft. Corporations are often worse than the government. They will gladly kill thousands for minor profits. Hundreds of thousands or millions if they are not Americans. Minor crimes are just part of doing business. In our society, everything is a calculation, and lives have a dollar value. It's not very high, although admittedly, higher than most of the rest of the world. This mindset permeates the entire culture and society to the point that it's virtually indistinguishable from them. It's no wonder we as Americans cannot and do not trust each other. You simply never know who is out to fuck you over. You just know that there are many and that you will be fucked over. The more money you have, the more you can insulate yourself from it to the point where enough money gives you the privilege to fuck over other people in previously described manner. This also explains why people love their guns so much. Some people just get fucked over for money. Others, especially minorities, often get fucked over for their lives.
It's small, simple, unobtrusive, free and portable-
It is also old and unmaintained, but I love it.
Just unzip and run. No installation required.
http://theguide.sourceforge.net/
I still associate my NES with the smell of ozone.