skysight-inc/HackerNews huggingface dataset:
A lot of insight in the parent comment here. Most importantly this: "...there seems to be two camps of people: those who want constant positive reinforcement and those who it completely has the opposite effect ..."

If you are leading and or managing a team, one of the most important things you need to know are how do people want their feedback. My experience is that it varies from person to person (I suspect that there are many more than two camps :-)) and as such it is unlikely that you can meet that need in group feedback.

Because of that, my choice these days is to split feedback into two fora, the group status meeting and 1:1s. In the group, feedback is modulated by progress against plan. So "we need to work harder" for behind plan, "neutral" for on plan, and "this team is killing it" for ahead of plan. In 1:1s the feedback is based on the expectations that have been set for that team member, do they know what is expected of them? Do they know how it is being measured? And where are they with respect to measurement vs expectation.

1:1 feedback often times (for me) takes on more of a mentor/mentee tone rather than a how are we doing on the schedule tone. Doing that well also requires a certain amount of trust which, as a manager, you have to earn by being honest with your team members.
10 parallel calls already in progress that have not received a response from server. Why start 11th request?
I think this comment is a prime example of why this problem is so difficult. Misinformation often caters to people's cynicism, creating a sort of positive feedback loop. How do you reach the chronically cynical person who's essentially trained to look for the most sinister explanation to all phenomena?
We just launched a dedicated technical due diligence / tech M&A risk consulting company. The goal is to help investors make more informed investment decisions.

https://www.apioneers.com

We are currently building a streamlined process for investigating risk inherent in a technology company (be it a start-up investment or a critical piece of infrastructure for enterprise systems), and finding out just how much can be solved for with such a standardized approach vs. the consultants' years-long experience applied in a creative, inquisitive way.

Next to this, we are also putting a lot of hours of R&D in a financial product that's going to help make housing more affordable for good tenants AND just as or more profitable for landlords at the same time. Good progress here, already talking with banks for contractual details.
It's certainly not a good idea to identify anything that deviates from the public expert consensus as "misinformation", but that doesn't mean there isn't a problem of verifiably wrong claims spreading. For example, Chicago and San Francisco have not fully opened their economy. I'm skeptical that the resolution to this problem looks anything like "information control", but it seems terribly naive to expect the problem will resolve itself when it's so easy to be ensnared by it.
sounds similar to Wix
The difference between a circuit breaker and a kill switch is that a circuit breaker, like a real electrical one, automatically trips and stops requests going through for some time after a certain error threshold to the remote server has passes.
I had considered asking this from a web developer/node perspective. But I increasingly do other things like run different databases, golang, etc so I left it open-ended for that reason.
The funded ones with the 2 year timelines generally are. But most startups are more bootstrap/angel investor with a bright owner who has a fatal flaw.
Currently using Authy. Any way to migrate my keys in bulk?
Thanks for sharing!! I've never seen this before.
That is roughly how I use it, except is ssh'd into an Emacs session. Even though I am not a fan of MacOS, I love the M1 air. Great keyboard, always cool, battery runs for days.
About Warren Buffet:
First he invested in insurance companies. So you buy an insurance company for $1B - you another few billions to invest on their behalf, which greatly increases your return rate.

Secondly, he has a strategy to often invest in private companies, leaving old management in place, and hold for a long time, and benefit from profits, not from stock changes(means he can hold the company for the long time).

So for private companies, one major reason owners prefer him - his that this business is their "baby" so even after cashing out, they still get to manage it.

This is unlike what most private equity investors do.

So when he goes to make a deal with those companies, there's little competition from other investors, so he can buy at a lower price.

So he just seems like genius stock picker, but he really isn't.

As for predicting who in tech will become profitable ? i doubt that someone will share that information freely.
There have been several posts in recent weeks on this topic, and every time I have the same reaction: how can they all just ignore TiddlyWiki [0], that has been out there since 2004 and has evolved nicely over the years to deliver most of the same outcomes? Is it that folks just ignore prior art? or they just gravitate to the latest more sexy software? (honest question).

I've been using TiddlyWiki on and off for many years, but 2-3 years ago I moved heavily into it (the Drift [1] distribution), and I haven't looked back. To me, it has become less about the tool and more about the information, and ensuring I have complete access to it, even 20 years from now. That includes data, metadata and even the software itself, regardless of the platform or OS.

[0] https://tiddlywiki.com/

[1] https://akhater.github.io/drift/
Scala slowed down, largely due to spiked popularity of Kotlin.

https://snyk.io/blog/kotlin-overtakes-scala-and-clojure-to-b...
Resilience4J has improved quite a lot. I have been using for over two years now, never missed out on anything.
Macports? I don't brew
Ask HN: If you take lot of Vitamin D what else do you supplement with and why?
I have read things that indicate that vitamin D alone is not ideal. So wondering what are other people doing.
Comes up more often lately. I do have an issue with organizing myself. Scheduling more than a week ahead is close to impossible. Not due to my job but due to my messy mind. Same with note taking.
Has gotten worse and I even tried learning Emacs to get the famous Org Mode. I have to admit: This is so loose it seems I can get real benefit from it. No rules to follow but I manage to stay on top of a lot of things for the first rime. Still don't get Emacs though. Zettelkasten seems to require a diligent setup and well... no.
I wonder how well the NiMH battery in it holds a charge after all these years. It would be a fun project to customize a new modern battery pack to replace the original. I hope someone takes that up.
Mind sharing the app name?
My perspective: Going from a 2019 15" MacBook Pro with 16GB of memory to an 8GB M1 13" MacBook Pro

You don't start to feel the 8GB until you:

* have a lot of tabs open in Safari (like ~30+)

* have heavy web apps (GMail & Outlook, I'm looking at you)

* run a virtual machine (Only so much you can give a Parallels instance w/ 8GB)

* run some known performance & memory hogs (Slack, Teams, etc.)

* vpn seems to slow things down a bit

I generally will close down apps when I don't need them (but that's _always_ been my habit). I do find the M1 to be fully sufficient (and still faster than my previous MBP) when doing my day-to-day (including VS Code, JIRA, Slack, Xcode, Node, etc.). I also use my M1 for music performance and composition, and that's worked just fine for my purposes (but so did the previous MBP). I will (as I did before) switch contexts by closing apps I don't need, so it's hard to say if apps from development impact the apps for music or not; they rarely run side-by-side.

Things that have greatly improved my productivity:

* This thing is as cool as a cucumber, and absolutely sips its battery. This means I can be more comfortable taking my MBP to the couch, or to the patio (when it was warm) and not worry about watching the battery %.

* This thing _in general_ is much snappier. Native apps load quickly, and performance in the apps I use is about twice that of the previous MBP.

* I can type on this keyboard!

* Using a single external monitor is fine; I work from a couple of locations, and both my Dell P2415Q and my LG 24MD4KL-B 24" Ultrafine 4K work fine.

There are edge cases here where the M1 falls short:

* I can slow the poor thing to a crawl for a few seconds if I attach a 4K monitor and then try to AirPlay to another 4K display. It catches back up and is generally fine after, but you see the beachball for a while.

* Lots of tabs in Safari will cause slow tab switching, and some web sites just chew through CPU. Battery life is still _way_ better than the previous MBP, but it definitely impacts the feel of the device.

* Bluetooth mice -- ugh. I bought a Logitech MX ergo and had to switch to using the receiver instead because the MBP bluetooth felt so laggy.

* Most iOS apps just aren't well suited for the device. Apollo (for Reddit) works pretty well, but even that has its quirks where sometimes keyboard shortcuts will just stop working.

* VMs. If you run Windows in Parallels, you _will feel it_. I do not run VMs all the time for this reason, but spin them up and down as needed.
Ideal “project management” tool for a solo developer
Summary:
#1 Short task id
#2 Able multiple task with a terminal
#3 Fully integrated with github
#4 Pomodoro timer integrated
#5 Multi view, kanban and table
#6 Simple, no strange labels to fill
It’s often a facade too! I’ve heard privately at one employer the statement “We all outwardly sing Kum-ba-ya and hold each other’s hands but everyone has razor blades in their palms and they hold hands pretty hard...”
Historians are typically people with an utter lack of technical skills or any understanding of what actually goes into making anything work. A dry surface level analysis of literary accounts and archaeological finds doesn't mean much if you lack the mental context for it.
- I had some trouble building the Rust lang toolchain (wanted to work on a PR), haven't tried again (used my other machine instead).

- The battery life is great.

- Something I wouldn't have thought is how much I enjoy that the machine is not heating up under stress. Difficult to describe, but that is really really nice

- I have the MBP and the only time I heard the fan was when I compiled the Rust toolchain.

- Tried to run Linux in Parallels but that didn't work (some sort of weird error, didn't investigate further)

- Within Xcode/Swift everything works as expected, just much faster ;)

- My M1 has problems when I'm connecting my external 5K display. It works great, but when I put the M1 to sleep and wake it up again it can't find the display anymore. Even plugging it in / out doesn't help. I read somewhere that that'll soon be fixed with a software update.

- I had higher hopes for the ability to run iOS apps. I really wanted Netflix and Amazon Alexa to work. I hope they'll reverse their stance to not support M1s at some point.

Overall, I'm very happy with the M1, but I still have a 2018 Mac mini that continues to be my main machine. I bought the M1 because I have an upcoming Mac app that I've worked on for ~2 years and I wanted to make sure it works on M1 (https://hyperdeck.io).
But you can smother the damage; startups can't.
I vastly prefer honest negativity over dishonest positivity. An example of this is the behavior of service personnel in the US compared to my native country, every time I go there I almost want to tell them to tone down the niceness, but of course there's no point because I realize I'm the odd one out.

Of course I appreciate the effort of being "nice" but when you're not doing it out of genuine care for someone I'd much rather just be treated in a neutral way, like you'd treat any human being you encountered that you knew nothing about. I don't much enjoy being treated as an old friend by someone who wouldn't lend me five bucks, and I don't enjoy being asked polite questions that require elaborate answers when you really don't want to listen to the answer and your eyes glaze over within the first seconds.

Adults have left their insecurities behind them and should understand they're not, at least initially, the friend of every human being and shouldn't have a problem with being treated in a professionally reserved way.
They seem to be unable to answer this question since Google provided no URL. Without knowing what is considered malicious, how could they check if there was anything? What if it is a false positive?
This is why you need some form of network analytics to figure out if the new version you are rolling out is breaking anything or even seeing of something _is_ breaking. I get the "we don't want to compromise security even an inch", but how secure is a messaging app that cannot send messages?

Even more critical since anyone can write clients that function with the server and thus a malicious actor could attach them without them knowing how to identify it or stop it.
yeah, having actually worked with plcs in industrial control systems... the security is, ahem, lacking for the most part. not that my work was with high security process control but I'd say it's fundamentally lacking for the most part as the state of the art is not that great.
Sometimes I've wondered if this keeps down ambition -- the only workplace I've been in where this is common, people seem to have a pretty low bar for success. I wonder if part of that is that folks think that they've achieved a lot when they get so much praise, even when they are not achieving a whole lot.
Again, the issue is not the citation... it's what the citation is used to do. If an historian cites Mein Kampf it's not because they're agreeing with it, is it?
The hippos probably bring in tourism dollars, so that wouldn't be the most profitable solution.
There's a limited number of IPs so most homes CANT use static... we already don't have enough IPs for the mountains of devices.

But the other part is money... why give something away for free when you can make it a "feature" to pay for?

Tons of other reasons in various articles...

https://www.online-tech-tips.com/computer-tips/ott-explains-...

https://superuser.com/questions/590391/why-do-isps-change-yo...
Yes. That's what the Twitter thread shows.
The contrast between Gauss-Jordan[0] and the Bareiss algorithm[1] is a good example of explicitly handling the length of the numbers in bits as part of the runtime.

Gauss-Jordan is O(n^3) if you consider addition and multiplication to be constant-time, but if it operates on arbitrary-precision integers, it can get exponentially slow[2].

The Bareiss algorithm avoids this worst-case behavior by choosing the pivots in a slightly more involved manner, which avoids building up large intermediate values.

[0]: https://en.wikipedia.org/wiki/Gaussian_elimination#Computati...
[1]: https://en.wikipedia.org/wiki/Bareiss_algorithm
[2]: https://staff.itee.uq.edu.au/havas/fh97.pdf, Section 3.1's "Construction A" is a specific matrix that exhibits the worst-case behavior.
Inside Twitter’s Decision to Cut Off Trump
Somewhat related; I've always been very curious why a lot of developers I've worked with seem to think testing isn't worth the effort, and I've been keeping a mental checklist of all the reasons/excuses I hear so that I can reflect on them as well against my own experiences - sort of a way to challenge myself and ensure I'm not just cargo-culting methodologies.

Recently I decided to go through `Growing Object-Oriented Software - Freeman, Pryce` (and actually finish working through it this time) with the goal of understanding what "proper TDD" is supposed to look like. Something interesting I noticed is almost all the complaints I've seen as reasons against TDD/certain testing methods all seem to be examples the authors use as how not to use TDD/testing. It seems to me that a lot of developers have just learned _of_ these techniques by name, and haven't really put a lot of time/effort into practicing their application and instead just seem to write them off on face value or by the literal interpretation of their names.

One example, a lot of people I speak with seem to think TDD is very literal "write a _unit-test_* for everything before you write the implementation OR ELSE...", but of course there's a lot more nuance than that depending on the situation. The book actually puts a huge emphasis on having your initial test(s) be end-to-end tests that slice through the system as a whole, with the idea being to create nested feedback loops of varying granularity/abstraction to allow you to iterate without fear. This was something I never heard emphasized at all when I started learning about TDD, or hell even in a paid course my employer put us through by a "TDD expert".

I should also clarify, I only consider these claims from developers that have a proven track record of working on large/complex systems since, well, those who don't probably haven't cultivated their ideal workflows/approaches yet (or just haven't been given the opportunity to showcase them, as is common in large companies).

* I emphasize unit-test because a lot of code bases I've worked in rarely have anything other than just unit-tests...
I have a an old network protocol analyzer from an HP-Aglient subsidiary that's supposedly scriptable in Forth. Actually out of all my old protocol analyzers this one is probably the coolest from a technical perspective. It has six 68k's in it, and is heavy as hell. Unfortunately I never get to use it unlike all my other one's because it only has ISDN BRI interfaces, and most of my hacking involves PRI (T1/E1) or V series interfaces.
'Emotional Dishonesty'.

In a positive direction it's at least more palatable than otherwise, but it's still bad.

Orgs. that focus on emotional support and politics more than outcomes will feature this prominently.

Oddly - it may not matter. Sometimes pushing the cogs of ABC corp forward is mundane, and everything else that happens is just fluff talk, like the sign on the bathroom door, it doesn't change how many widgest were bought and sold, or like the language on the 'stop sign' in Canada: French or English it doesn't matter, it's just something irrelevant argue about instead of having an actual war about it.
It depends on what you want. The first option will tend towards longer waits, and the second towards shorter waits.

I would tend towards increasing the minimum wait at each iteration (until you get to some maximim wait), because it it failed 10 times in the last minute, it's likely going to fail many times in the next minute, so we don't need to try more than once or twice.

Also: in case the client random is broken, you don't want to accidentaly end up with everyone retrying after zero seconds forever.
"You guys are {killing,crushing,owning} it"

I say this to my team a lot, even though they're operating as "expected" levels for my company.

The reality is there are a lot of teams and a lot of companies that simply do not expect much from their teams. We do. I want to remind the team that they are doing good work.

When people have confidence they're doing a good job, they're more likely to continue to do a good job.
Different Airbyte engineer here!

Wanted to help answer your question as to what "optional normalized schemas" means. When writing data into your data warehouse we provide 2 options: 1. write each record as a json blob. 2. infer the schema of the data and write each value in a record to its own column with an appropriate type.

We are betting on EL(T), meaning we think that Transform should be considered separately from EL. To give a more a concrete example, if you are already using DBT in your data warehouse to normalize your data, you likely prefer operating on the "raw" (json blob) data than an arbitrarily normalized form of your data that your EL pipeline has decided on for you. I am seeing this trend pretty pervasively where a lot of, nominally, ELT pipelines are outsourcing the Transform to best in breed tools like DBT.

Thanks for asking this question btw, we'll do our best to clarify in our docs!
Sony CSL Kyoto Laboratory
There's the notorious productivity swamp that is caused by the obsession with optimizing productivity without thinking about the actual purpose behind it. This is multiplied by the ease and incentive of creating and publicizing productivity software and articles that are consumed by people in a perpetual state of insatisfaction. The result is a psychologically advanced form of procrastination and a futile attempt at control that stems from fetishizing technology.

To-do lists are for things that aren't a real priority, otherwise you would be giving them your full attention and the tracking would be unnecessary. At most, it's helpful to track administrative minutiae. If you give something your full attention, tracking will seem like a non-sequitur.

Despite all of this, I have been finding the card system outlined here to be quite useful. The key for me however was to keep to a physical pen and paper version. Keeping notes exclusively online used to prevent me from being able to address them regularly with a clear mind. Forcing myself to synthesize ideas and refer to them again has helped me move forward in projects important to me. It's not the act of writing the note that is important, but the mindset towards having ideas that you want to develop.

Ultimately, most important aspects of life are beyond any productivity hack. You can't hack meaningful relationships other than by growing as a person, nor can you hack the strength to work on things that matter every day.

In a sense, the ultimate hack is to come to terms with your mortality and use this as an impulsion to focus on what really matters to you.
I don't like this. Companies going public means that they have investors to answer to. Investors who will pressurize them to close up their source.
Knowledge on how to make things is ephemeral, is constantly lost and has to be rediscovered even in the modern world. People whose day job is playing meaningless language games don't have any appreciation of how much idiosyncracy goes into doing even simple technical tasks.
By "metal" I meant the browser, so avoiding heavy libs.
I'm actually in my second year of university but I started learning physics "properly" at 14 so I had a head start.
Don’t worry. I already gave up on the sign-up flow when I entered my preferred username and password, then tapped register in the top right corner, only to be confronted with a prompt to —- again enter a username and password of my choice.

I would have to spend hours getting my family signed up for this thing.
Global warming kind of made it inevitable
If you have root access, yes.[1] Otherwise no, sadly. One of the reasons I moved off Authy before it got worse.

There is a workaround using the Authy Desktop app but I have no idea if it works.[2]

[1] https://github.com/beemdevelopment/Aegis/pull/107

[2] https://gist.github.com/gboudreau/94bb0c11a6209c82418d01a59d...
At the end of the day, its just the shell executing the commands :) sure, you can always distil it down to a script (or a set of scripts) and nothing wrong with it either - as always, depends on the context.
Needful H1B's are always positive.
And I'm positive they're destroying our IT infrastructure, one project at a time.
They do the minimum to make it appear it works so they get it off their desk. Just like their home country. What a fucking mess.
> AFAIK most of the co2 is from the chemical reaction itself, not the heat source used.

About half, I think (depending on the fuel used).

Cement manufacture is a major destination for supposedly "recycled" plastic, btw. Cement kilns are very flexible on fuel quality.
I just don't think the problem of misinformation has much to do with trusting the government. Even people who distrust the government can, should, and often do avoid falling victim to misinformation.
It isn’t the same imo. Many men take offence with woman in command. But I like how you think.