skysight-inc/HackerNews huggingface dataset:
If you read between the lines, the article sounds a lot like "I know better", implicitly "because I worked at Google" (as per the "ex-Googler" qualifier in the title).

Consider this:

> Introducing code search and monitoring doesn't require asking anyone on the team to change existing workflows. Changing the code review tool, however, does.

It basically sounds like the author wants to take over and tell everyone how to do things.

After time at Google, comparing them to other organizations all the way from 8-person start-ups to other FAANG+Microsoft, there are a LOT of downsides to their tools and their isolated ecosystem. A lot of things are more difficult and take longer to just get done than elsewhere at the same quality.

> Google is well-known for its internal tools. It would help to educate yourself a bit.

This may also be exactly the attitude OP was talking about.
When I wanted to learn about Indian classical music, I was pointed to the youtube channel of Anuja Kamat [1]. Disclaimer: I haven't watched enough to present an informed opinion as of yet.

https://www.youtube.com/channel/UCs6OTIFV53Z-EGT84lxTvqQ
In Russian-speaking world, the function of UVB-76 is known and scans of expired codebooks have been posted online. Long story short: it's a military communications system that uses one-time pads. Military units monitor transmissions and use unique decoding sheets to translate random numbers and keywords into messages such as "readiness level 1" or "execute action 5". It's mainly a backup system intended for use when everything else fails, because even off-the-shelf hand-cranked consumer radios would enough to receive messages, given the right decoding sheets. The amount of radio traffic on the station has usually seen an uptick during major military exercises.
I wrote a specification-test framework that does this:

https://github.com/hitchdev/hitchstory

Project with README that is partially generated from the code samples in the tests:

https://github.com/crdoconnor/strictyaml

with the README template:

https://github.com/crdoconnor/strictyaml/blob/master/docs/in...

that grabs code snippets and their expected outputs from the story:

https://github.com/crdoconnor/strictyaml/blob/master/hitch/s...
Interesting read, thanks.

I mostly agree with the article's premise, but I would add an exception for when you automate the solution yourself.

You personally no longer need to solve the problem, but in the process of automation you'll have to learn more about the problem then you are likely to learn just through solving it manually.
The problem is they delayed to develop process twice(14nm and 10nm), who believes next 7nm would come on schedule?
Terminal emulators, as their name describes, emulate old school terminals.

Terminal support in linux is built directly into the kernel. So bar minimum you need to be familiar with these syscalls, which are a little obscures, but luckily only a hand full are necessary.

Next, youll need to understand process management in the kernel, standard pipes, and job control.

The actual emulator code has to keep a mapping of terminal control characters to terminal features, and keep this working across OS's if portability is a goal. Here in lies the devil in the details. This emulation layer is tribal knowledge.

Finally you have to also be a good UI dev, who knows how to inter-op ASCII and UTF8 shell escaping.

This isnt touching on colors, GPU acceleration, and other pluses.
Congrats, it looks like you effectively monetised your network. I have met some people who wanted to do this, did have something to offer yet failed quite spectacularly to the point of becoming homeless and destitute. I guess it all depends on who you know. A lot of people (like me) are simply unwilling to pay more than something is worth in terms of time invested. But it proves that if you are popular amongst the right kind of crowd that is able and willing to spend, it is possible to do it.
No. Don't make candidates practice an otherwise nearly useless skill they will most likely never use on the job, when they can just look this algorithm up on the internet if they need it.
There's a more sinister yet subtle implication to this, which is that Amazon can de-platform people from their own homes.

If the doorbell stops accidentally when Amazon goes down, it can also stop intentionally at Amazon's discretion.
Warning: this link may be unsafe

https://defendingtherepublic.org/wp-content/uploads/2020/11/...

The link you are trying to access has been identified by Twitter or our partners as being potentially spammy or unsafe, in accordance with Twitter’s URL Policy. This link could fall into any of the below categories:

malicious links that could steal personal information or harm electronic devices
spammy links that mislead people or disrupt their experience
violent or misleading content that could lead to real-world harm
certain categories of content that, if posted directly on Twitter, are a violation of the Twitter Rules

^

This is the prompt I see. I see a "back to previous page" button but also an "ignore this warning and continue" button. In addition to providing the ignore button, they also put the URL up front and center, so it's not like it's impossible to figure out how to get to it yourself.

I doubt they are flagging the lawsuit specifically. They are most likely flagging the URL https://defendingtherepublic.org, which is not filing lawsuits on behalf of voters, but rather on behalf of Sidney Powell (it literally says "Sidney Powell's Legal Defense Fund") who is Michael Flynn's attorney and a former member of President Trump's legal team [1]. This website is not an unbiased source of information and a lawyer has no incentive to present any information that would weaken their client's case.

Considering Twitter has decided that flagging the President's own tweets is acceptable policy, it is not surprising at all that the same thing is happening to his surrogates.

[1] https://www.politico.com/news/2020/11/22/trump-campaign-sidn...
I think that the full context of the sentence you quoted will help:

> In this case, if you base your number of threads off grepping lscpu you take another dependency (on the util-linux package), which isn’t needed. You also get the wrong answer, as you do by grepping /proc/cpuinfo. So, what this will end up doing is just increase the number of context switches, possibly also adding a performance degradation.

The idea is that a common way to size an application that exploits concurrency is to base the number of application threads on the hardware threads available. This portion of the article is saying that if you do so on the basis of `lscpu` or grepping `/proc/cpuinfo` you could mis-size relative to the actual number of cores available to schedule the threads of your application on. Doing so will lead to excessive context switching for your application, and that can hurt.
I appreciate that someone took the time to closed caption the audio recording of the woodpecker. But it's in Polish, so I can't understand it.
Sometimes people just draw different conclusions because they have different values and priorities or willingness to accept incremental progress.

I’m not dismissing Klein, I referred to her “oeuvre” out of my respect for her as an artist.
I interviewed ~30 people total between 2018 and 2019, and I have to agree with you. There is no shortage of applicants. Just the shortage of qualified people.

Side note - I do NOT use whiteboard technique in my interviews. I ask the candidates questions about the stuff they mention in their resumes and go deep in the technical discussion based on their responses (or I told them to walk me through one of their recent projects be it a work project or their side project). Using that 'simple' technique, you can easily filter out so many pretenders (as I'd like to call them, who have splendid resumes but little to back things up when grilled the details about their resumes).
And on top of that, your TV manufacturer gets to spy on you. It’s win-win-win.
Use the upvotes and downvotes as a guide

Its worked accurately enough for decades to share a regional context
I think that's the entire point of this article: the existing system software APIs that we use aren't a good abstraction for the capabilities of the underlying hardware, leading to poor performance.
Perhaps next we will connect our toilets to the IoTs, so that the waste can be disposed of by smart routing of what's in the toilet. But then, oh shit, what if the network goes down? Have to hold it 'till Amazon servers come back up. :-)
> Google prioritizes code quality over development speed.

That's putting it nicely. Based on experience, I'd say it's arguing about preferences while demanding that code be coupled because "that's how we do things here".

> culture is far more like academia anyway

Academia is actually based on research and correctness to a much higher degree. The lack of focus on correctness in code worked on at Google is, honestly, appalling. Until, of course, you realize that all other FAANG employees still write loads of concurrency bugs and pronounce themselves gods for doing so.
> No product wants to be on the same chip for 5 years.

There are many chips stick to old process except latest performance chips like smartphone SoC, GPU, TPU.
Now I'm curious to what degree the graphics rendering is responsible for IntelliJ's sluggish, battery-hogging experience on macOS. I wouldn't think it's the main cause, but who knows
As a PHP dev this is a really fair comment.

I think the other reason non PHP devs think we are in the dark ages is because when they google it, our documentation looks like it's from 2010. It's a bit of a joke really.
"People Can't Read About Amazon's Servers Being Down Because Eminetra's Servers Are Down"
> But you already have a security vulnerability regardless, if you dereference p before checking if it's null.

Firstly, that's not (in general) true, unless you count denial of service[0] as a vulnerability; reading from address zero and then panicking has the same security implications as segfaulting while trying to read, namely the software immediately halting.

More importantly, the above code does not dereference p (at all, though do_stuff presumably does). `&p->baz` adds a constant offset to the (register storing the) pointer, without touching memory at all. There is no vulnerability (assuming the obvious assumptions about how foo and do_stuff work and are used) until the compiler introduces one.

0: For example, you count the fact that someone can DDOS the machine it's running on as a vulnerability in any network software. Which is somewhat resonable in some contexts, but not the context of compiler bugs.
Our Government (in Eastern Europe) has used the virus (COVID-19) to get loads amount of money from the EU and its citizens. Set price controls to push out private businesses, made health care workers lie[1] about cause of death because those hospitals have received financial aid from the EU (if the patients died from COVID-19), and so forth. You know the deal. The Government is benefiting a lot from this.

[1] Facebook is full of nurses coming forward with this, and I know some people working at the hospital.
Maybe I'm a jerk for saying this, but "dozens of sales" and "hundreds of followers" doesn't seem particularly impressive.
Well, fair enough then!
I wasn't talking about the reading of the number of CPUs you could use, but rather how many threads you'd spawn based on that information.

There may be 10 CPUs in the machine, but if your in your container which is restricted to using only 1 of them, it's no use launching 10 threads in that container over just having one.
Walking Has Changed My Life
How to Live to the Full While Dying: The Diary of Alice James (2017)
Hey landlords! Try the new Amazon Deadbeat-B-Gone™ service! $19.99/month!

Never have to worry about being a lead in Pacific Heights again!
Have maker badges worked (or not) for anyone else reading that's tried it?

Similar, but floating newsletter sign-up buttons/widgets in the corner of pages have worked for me (they don't have to be in-your-face pop-ups!), making a big difference compared to a sign-up form inlined into the middle or end of posts.
You’d think Apple would just hire someone to do this for them, in Java. There are maybe 10,000 concerns they could pay for to resolve, with clear no nonsense objectives like “Does Java2D run on Metal?” And the crazy thing is they have the money to do it.
I would have thought plagues were the greatest risk but I'm not some dipshit political ideologue.
Yeah, I do the same too. Like if I find a loose sock I can throw it in during the first cycles. I don't think top loading washers make enough of a splash to even warrant a lock, I may be wrong though.
Have you tried Thunderbird?
Communication through the cloud doesn't make it any more secure. To the contrary, it makes massive leaks/hacks possible.
Sluggishness is caused by the fact that it's Java.
Or you could just load the font from your own site and avoid a pass through Google.

Here's a site of mine which loads some fonts.[1] See any loading delays?

It's junk-free. No trackers, no ads, no "Google Tag Manager".

[1] http://aetherltd.com/
I would certainly hope that a type "checker" returns a more detailed representation of a program than a parse tree - one in which all expressions are typed and ill-typed expressions cannot be represented. So the premise is fundamentally wrong.

Are there non-type ways to improve program safety? Maybe. But since we all understand types and types can cover all the cases we've managed to find so far, I'd stick to types unless and until we can demonstrate a need for something else. Yes, handing out fundamentally unsafe APIs like array-access-by-index is a bad idea - but trying to put types on those APIs is the easiest way to see that they're the wrong abstraction. If you insist that your APIs be type-safe, you'll naturally be guided away from APIs like get-at-index and towards APIs like map / fold / find.
Not really. And it's a tab on my terminal/tmux session or on a browser.
It should be noted that the reason this is wrong under Docker is that /proc/cpuinfo is not cgroup-aware. LXC works around this by creating a fake /proc/cpuinfo (and /proc/meminfo)[1] which matches the values set by cgroup limits.

[1]: https://github.com/lxc/lxcfs
It's always disconcerting to see academic inquiry censored.
$THANKS – a cryptocurrency you earn by being thankful
It hasn't helped that iOS and Android haven't always made it easy to connect to other local devices that aren't bluetooth. Cloud services are handy, cheap intermediaries for lots of device/user interaction. LAN connectivity is a lot more complicated than it seems on the surface, with devices constantly going offline depending on power consumption and what chipsets are in the device (which is a function of what price point the makers were targeting).

And yes, there are technical solutions to this (just add an IoT hub, just add this chipset, etc), but don't forget how cost-driven IoT still is. People want the features of smart devices, but won't pay 5x the cost for it...unless you're Apple making headphones.

IoT is still very much a hack-driven industry. I do 100% agree that the software side is substandard, but until some of these chips get cheaper it's surviving on small margins.
That's the sort of thing that sounds smart if you don't stop to think about it for 10 seconds.
كلمات اغنية مشكلة دموع تحسين
Evolution is a process of obtaining solutions to problems, not obtaining "the only possible solution" to a problem.
Apple has vested interest in users not running Java on their platform.
Sharks are larger and have larger teeth though. Plus, they have an advantage b/c they live in water and we don't. Bring them to land and we can debate a cage-less shark fight. The tiger situation seems more possible but I wouldn't try it.
Not just Macs, plenty of Linux systems have a big.LITTLE design.

with a big.LITTLE system it'll really depend what you're doing. Just compiling something? It's probably fine (if all cores can be active at once). If you're wanting more consistent performance for some calculations? You might need to think a bit more.
The Oldest Evidence of Animals Might Be from a Different Organism
The key is to use reference-counters. If you think about it, no lisp is really going to fit the single-ownership model. Many of them are implemented on GC'd languages for this reason. Rc<> is the standard Rust answer for GC, and in practice means you don't really have to deal with ownership issues for those values.

I implemented my own Rust lisp if you want an example: https://github.com/brundonsmith/rust_lisp

And here's a more general resource (not written by me) on this class of problems and the surrounding subject matter: https://rust-unofficial.github.io/too-many-lists/
I have a mechanical doorbell. The only way it can be down is due to an external service is if it breaks in a way that I can't fix.

For many cases of reliability, mechanical > wired > wireless > cloud.
Typophiles like Google's CDN because it can have way more nuanced conditions about what exact font to load

But you don't have to use it, and yes for some reason that seems to be a lost art.
Reminds me Philip K. Dick’s short story “The Day Mr. Computer Fell out of Its Tree” (written in 1977).

"It had been a bad idea from the start, back in 1982, to operate every mechanism from a central source. Of course, the basic idea had sounded good: with the ozone layer burned off, too many people were behaving irrationally, and it had become necessary to solve the problem by some electronic means immune from the mind-slushing ultra violet radiation now flooding earth. Mr. Computer had, at the time, seemed to be the answer. But, sad to say, Mr. Computer had absorbed too much freaked-out input from its human builders and therefore, like them, Mr. Computer had its own psychotic episodes."
Something like that. If we have a frontend engineering role and a candidate is not able to explain what Promises are, then we know their resume is BS.
I'm just saying that there's a limit to the amount of bite protection provided by chain mail.
From the man page:
> If the -j option is given without an argument, make will not limit the number of jobs that can run simultaneously.
> *There is a reason so many other people accept the concept of an interconnected network
https://injuryprevention.bmj.com/content/9/4/357
Typescript is just a much improved javascript, to the point of these two just being two dialects of the same language. I wouldn't make a distinction between the two. Performance-wise, as a servrr-side language, they both have the same strengths and weaknesses.
The meaning of "classical" with a lowercase 'c' refers to elite music with theory built around it from any culture; most people are not referring to the "Classical" with a capital 'C' period of European culture.
For the technically-literate home automator, I think the sweet spot is something like Hubitat. It's not home-brew, has decent commercial support, integrated Z-Wave and ZigBee etc. and is designed to be completely self-contained on your LAN.

I dumped my Wink Hub for one after they did their bait-and-switch for subscription fees. Never been happier with home automation.
Might be some lawsuit.
Is it not the first open phone out there, ever? Regardless, it is too expensive, and I need a phone, so I compromise. I have a shitty Android phone, and I do not store secrets on it.
it depends on your perspective. It may not be intended to be impressive, but merely representative. It may not be intended to be representative, but merely informative.
> According to a recent EU survey, 77% of EU citizens would rather repair their devices than replace them; 79% think that manufacturers should be legally obliged to facilitate the repair of digital devices or the replacement of their individual parts.

I hope this will shut up some of the Apple fanboys who argue that this generation doesn't like to repair things or elctronics have become "too complicated" to be easily repaired without sophisticated tools. I am really curious to see what changes Apple will make in EU to adhere to this law.
Intel has a storage layer running Optane for meta and logs called DAOS. ^0

Intel DAOS was news to me only last week, a oversight I'm profoundly embarrassed by given I'm responsible for a meaningful amount of storage iron due to be replaced with orders to spend to estimate eliminating dependencies if performance comes plenty with sufficient reduction of vendor lock in. Lock in is a relative thing in enterprise storage. Apple could have been forgiven a eternity of nannying for a good ZFS port but I have always believed that Steve knew Larry coveted SUN for ZFS alone, years before that forced wedding. I ran my business on VMS. RDB the management system Palmer gifted to Oracle was the upgrade option above licensing RMS Record Management System and RMS is plenty capable being foundational to the hallowed for good reason cluster capabilities VMS is remembered for in the same ways sclerotic drunks on their death beds remember their Sunday school teacher's good words on moderation.
ZFS exposed to a new and enthusiastic development community unfettered with nuisance concepts precisely those which were cast off with exhilarating energy by the NO-SQL movement. would be a genuine threat provided with functional basic data integrity underpinning their efforts during the pertinent time.
Every top loader I've seen solves this with an interlock: opening the lid stops the motor and brakes the drum. Closing the lid resumes from where it stopped.
I have to say that is least threatening characterization of Raag Bhairav I’ve heard in a while
Also see meson's[0] built in package management called wrap-db[1]

[0] https://mesonbuild.com/
[1] https://wrapdb.mesonbuild.com/
Yes I grew up around there. Intercourse is close to Paradise.
Spurdo’s influence is universal
> C will also prevent you from mixing up disparate pointer types

No it won't. In C++ it's a compile error [0]. In C it's just a warning [1].

> c++ has no protection against void pointers

You're somewhat correct but the answer is a lot more nuanced (because void* is very nuanced). Again, C++ will complain unless you do it "right" [2] while C is ... willing to let you blow your leg off [3]. However the definition of "right" is still just as dangerous as C's because all type information was lost in the void and it's up to the programmer to get it right -- and programmers are notoriously buggy.

[0] https://gcc.godbolt.org/z/166ns8

[1] https://gcc.godbolt.org/z/vEnajj

[2] https://gcc.godbolt.org/z/cGe39z

[3] https://gcc.godbolt.org/z/orb1s8
I have gone through something similar recently (implementing nanovg on top of Metal). It’s a really good experience and can be achieved with relatively little code.
> I believe that actually adjusting the programming language grammar (and thus the actual parser) is clearly a parser approach to solving the problem.

How do you get the properties of type safety (progress and preservation) in this case?
It's a safety mechanism mainly intended for children. I think it's been around for a while. The washer Mom bought 10 or 15 years ago had it. I think there's an unlock button on hers, but I can't remember. I do know it's incredibly annoying.
Great point and I totally agree. I was reffering to the other commenters' here generalizing sentiment of "IoT is a mess".

Just realized I wasn't clear what comments I was referring to when I wrote I don't understand their issue.
a good book which discusses species with over a dozen sexes read Matt Ridley
The Red Queen
From the author's blog:

>>> But I’ve also no interest in participating in the “startup game”. I don’t want to write applications for accelerators and rely on the opinions of gatekeepers.

>>> My goal is not to become a billionaire.
> "I was wrong, but..."

Just leaving this here. It needs no further explanation.