skysight-inc/HackerNews huggingface dataset:
When I was figuring out how DNS works back 10 years ago, I was told "Why don't you just use 8.8.8.8 everywhere? Why do you need your own DNS server for anyway?" every single time when I asked a very specific configuration question. Some years later 8.8.8.8 was just replaced with 1.1.1.1 with same critical counter questions instead of helping. So, it appears to me, instead of understanding DNS and routing, people and tech-bro businesses take shortcuts by using centralized infrastructure for their systems, creating dangerous configurations. Now, Cloudflare have made a mistake, and half the Internet crumbled down. See the irony?
> If anything, I'd say there is more transparency around unethical behavior by elected officials.

Yes, and it's because there are more watchdogs and reporting than ever before, and "the internet does not forget"
You’d still have hash collisions
Affordable Forward Geocoding API?
Cheaper forward geocoding api than Google's?

Does anyone know of any reliable forward geocoding apis that are affordable/free for a startup in its early stage? All I've been able to find is Google, FB, and Foursquare :(
Except that FLW homes tend to have serious deficiencies as houses. Their roofs leak. Their interiors often use natural light poorly and are cavernous and dark. Admire them as works of sculpture, but don't live in one.
Even that's just an effect that you can represent in your language. The evaluation of 2 + 2 is not exactly the same thing as the value 4, but you could track the overhead of evaluation (e.g. in the type) and have your language polymorphically propagate that information.
This is mostly it.

Before Stripe payment processing was abysmal. There was no thought at all given to the developer/implementer experience.

Stripe basically put a clean and straight forward API and product around the mess.

I know java is 'not cool' but it feels like javadocs in 2002 which are generally well organised by virtue of myriad of conventions, as opposed to docs in some other langs. which can be hit and miss, though getting better.

Stripe is a pretty good example of good product experience for those having to 'do the work', because they will likely have a lot of say in it, in the long run.
We can't take any video at face value anymore unfortunately - a video can be edited to make things look differently, or simply captured in a way to hide some elements out of the picture. It's been used by media before to push a specific narrative.
What I love about his stories is that they could be easily applied to modern Portuguese society, and would be for the most part still up to date.

That unfortunately leads us to other philosophical questions, though.
I'm pretty sure the delineation of the PM and TPM roles is not internal vs. external customer facing, but where your main skills lie in terms of what you're handling.

PMs are usually more upfront in understanding the customer and the business needs. Whereas a TPM, is more behind, understanding the customer but moreso managing the tech teams and solution architects to deliver the proposed solution.

However, the PM role is fickle, and seemingly no company does it the same as another.
Are they doing any notable research at all?
I never said this, what I said is that is that societal figures of power exist with a benevolent purpose and should not be perceived as evil.

The system of checks and balances on the power of the state can be seen in two lights: 1) as a way to prevent tyrannies from arising or 2) as a way to let the good actors freely act within well defined boundaries.

I simply believe the second point of view to be much more fruitful and stable.
Did something similar for a chat app and the first week we released it had an angry support call asking why we’d labeled one of their customers “bloated sloth” (I don’t recall the exact adjective-animal combo but it was similar).

This is what happens when engineers try to be playful.
I'll warn against getting way too focused on this as an early company.

Getting something up and running is often waaaaaay more valuable then achieving Stripe level UX from the outset, and then as time progresses you must make a conscious effort to improve. Remember, Stripe has been an app for about a decade. That's a decade's worth of learning what users care about and what details matter. And clearly that's a decade to polish a product to near perfection.

A trap I've fallen in myself, and I see /a lot/ is that people focus on delighting their users before they even know what delights their users or what their users care about. Often you'll only learn that by having a product that works and customers need from the outset.
How can I gain practical experience in these things? The jobs I've had mainly revolve around adding new features, not doing any of the things described in the article. Does working at bigger companies actually give you experience with this?
Quarkz: A Solution to Post Quantum Supremacy
https://link.medium.com/xnfvtsnei8
Top Data Science Mentors for This Month
> If you have an old fridge/dishwasher/etc take care of it, polish it up, treasure it.

I think it's more a question of what you buy. The crappy ones from the '90's that weren't going to last have all died. The ones that left were the quality ones. You can still buy good quality, straightforward appliances. You just are going to pay accordingly.
I think this is true, but only part of the equation. I think you certainly could build a house at average-suburban-prices without cutting corners, but your profit margins would be lower or you'd have to compromise somewhere else. For example, the market has optimized around square footage, $/sqft is the most important metric for many consumers, ergo a smaller but better built house won't sell (or, at least, won't sell for a price that justifies the extra expense). Nobody ever got rich by leaving money on the table.

The disadvantage of living in a seller's market is that it's also a builder's market; when homes sell as fast as they're being built regardless of quality, there's little pressure on builders to improve quality.
The reason UDP is less leaky is not because it meets any guarantee better, but because it guarantees less
The grates that protect prison windows are often made of pipes with a bunch of loose rods inside. Cutting through the pipe itself is relatively easy, but the rods inside are unfastened, so they tend to roll under the cutting tools.

Edit: The principle is actually somewhat similar to the anti-drill protection on door locks - a small disc in front of the lock with a slit that the key goes through. The disc makes it hard to drill through the lock, because it spins together with the drill.
There is a transcript here: https://github.com/matthiasn/talk-transcripts/blob/master/Hi...
Humberto Costantini.
People impersonate officers all the time - you read about weirdos pulling people over and then getting busted when the drivers calls 911.

It's illegal.
Also not, Electron apps are Windows HTA revisited, not willing to do the right stuff.

And yes even Microsoft does it, but what to expect when younger teams have the cool ideas to rewrite VS installer with node or use it to drive VS plugins.

Still not every graphical application is Electron based, whereas in what concerns the UNIX terminal hardly anything has changed in 50 years.
I think about 'Why it is Important that Software Projects Fail' a lot.

https://www.berglas.org/Articles/ImportantThatSoftwareFails/...

It's been posted a few times over the years: https://news.ycombinator.com/from?site=berglas.org
I'm curious as to know what your PM's roadmaps look like, because really they shouldn't be listing features/implementation, but objectives and goals.

I agree though with what you're saying, regardless of the technical capacity of the PM, it's not really up for him to decide the capability of the teams, or the proposed technical solution. He should be managing those with the engineering teams, and their thoughts should be reflected on the roadmap.
> The specific implementation of that form really depends on your circumstances, I am not trying to sell you Google Forms specifically.

And that's followed by a footnote:

> Still, a Google Form going to a Gmail mailbox enrolled in the Advanced Protection Program is probably the most secure reporting channel against real-world threats. PGP will get misused and anything else phished before anyone gets into an APP’d Google Account.

... so it's back and forth on it. Since this is security we're talking about, I don't think it's a good idea to communicate in a style like that. People's brains will condense it down and then you're stuck with "use Google Forms", and that's what I'm arguing against.

> So it seems like you're combining the argument for PGP when the argument against centralized solutions, but your footnote walks back the argument against PGP as long as the solution is not centralized.

The decentralization is very high on the priorities for me on this, and the argument I really want to make is that you should be using something decentralized. PGP seems to be the established practice, and that gives it a huge edge just because people still need to deal with it anyway (and hopefully spend a bit of time learning how to use it correctly.) I also think that a message-level encryption system will beat account-level access control; I really don't want my phone to have access to security exchanges.

> Do you agree with the author of the post that an HTTPS form is more effective than PGP, but only as long as it's not centrally hosted?

Honestly, no, because I agree with you that I can't host a HTTPS form and get better security out of it than I do with PGP. And I think a huge part of people is in the same boat with me there. But that may not be the case for all people, hence my "If you're more comfortable with that than PGP, anyway."

(…especially since that form is only half the way, you still need to somehow read the submissions…)

But this is something that could change with the introduction of a pre-made FOSS kit to run a page like that.
How to Re-Run Last Executed Commands in Linux
Tried from Australia, the imagery of my neighbourhood is from 2018
If this is a result of poor execution then I'd stay and change it. If instead it's a result of a cultural or company vision that does not embrace focusing on the customer, their problem (not just your opinion of it), and working constantly towards solving the problem then you should bail.

I spent a lot of years in several companies thinking I could correct a bad vision or culture, and unless you're the CEO you can't. Poor execution of a good vision/culture is always correctable, although you should consider what is the root cause of that poor execution... often it's personnel.
it is the Emacs of finance.
In my experience, "strong opinions weakly held" is a style of workforce management, not a thinking style. In brief:

- Project total confidence to your employees. At any given moment, your course of action is the best one available.

- Announce changes instead of proposing them. Announce them at the last possible moment, or even retroactively.

- Never mention past iterations you have discarded. Now is now.
I would say that as the PM role is one without actual power, you need to convince those who will be working on a problem to be convinced that what you're doing makes sense. With data backing them up, this makes your assumptions more trusted, and the team easier to convince.
I'm someone who does that I believe. I don't see it as a bad thing. I'm not going to go and pretend it was my idea, it's just that I take a while to make up my idea of what's right, and I'll discuss edge cases and all kind of issues with others really thoroughly and strongly, I'll do that with many people, about the same thing. And then I'll kind of form my own opinion from that, which could be 90% of person's X, and 10% of person's Y, or any other combo, sometimes mixed in with some of mine as well, but not always, it's very possible I was the most wrong of all initially.

In practice, it means that when I commit behind an idea, I'm often right. But the ideas are not necessarily mine. And I don't care.

I wouldn't say it's narcissistic, for me, I feel it's actually the opposite. I don't care that I came up with it or you or who did, or even if multiple people contributed to it, I just care that it's the right idea, and once I'm confident that it is, I will strongly upheld it and hold it as my opinion. That's because I've already put it to the test by arguing against it in all possible ways, talking to many others about it, getting their opinions, their alternative ideas, etc.
Work at a startup as the systems person, because they don't already have one
Everything a UNIX cli does can be done better in a REPL.

Modern UNIX has the necessary IPC tooling for REPL workflows like on Xerox Workstations REPL, Amiga REXX, Oberon, Powershell/COM/.NET, Inferno, yet the large majority uses it hardly any different from V6.
Our free press didn't do much to help prevent the spread of the virus here either... It looks like it's also going to turn out much worse.
I can't see the improvement of this vs. walls of high end personal safes. They have used mixed material walls for ages, made from some hard small component (e.g. ceramic) embedded in a more flexible mass (hard rubber).

Being accepted in SciRep this material has to have some merit but I am unable to see it.

Is the structure even scalable to smaller objects? The other comments talking about bike looks did not read the paper it seems.
Have you seen Workspaces? Have you tried to use it?

It’s one of the most horrible things I’ve ever been forced to touch. I avoid it even more than I avoid Windows and other Microsoft products, which is saying a lot.
have you considered offering it as a cloud platform? we're doing something along these lines, niche scientific software (biological modeling, bioinformatics) as a paid hosted service. still at the prototype stage! so I can't comment on how well the business model actually works yet lol

but the idea is our mathematician will be able to publish whatever novel math she develops, and we may eventually open source the math core as a reference impl, but we'll keep all the cluster management and other supporting infrastructure code proprietary. sort of a "if you want to run it on your desktop, go ahead! if you want to actually scale this up for big jobs, we've done all the legwork already so it's really in your best interests to just pay us." I think open source ideals are good and worthy but from a business perspective, you capture value by providing value that can't be got without you. relying on customer goodwill is particularly difficult because any large org, the people who will feel goodwill toward you and the people who can authorize purchases are in two different departments

also fwiw I think if you wanted to do the model you described in the paper unchanged, gpl is a much better choice than mit. copyleft actually serves as a wonderful poison pill: you can try us out for free, but if you want to ship us, you need to pay for a proprietary license or legal will nail you to the wall. whereas mit, there's no stick. I've seen affero used by several projects for this express purpose: you have to buy a proprietary license because agpl is so onerous you just can't use the code for commercial purposes at all

interesting project btw, I love seeing stuff like this!
Forget locks... just make my tires out of this.
indeed, that's how you'd embed a balanced binary search tree in an array.
I recently built a Stripe integration, and can't say I'm especially impressed.

Unless I completely missed some aspects, it mostly just seems like an interface to their database. While this is great for some advanced workflows, the vast majority of use cases are all very similar: "create subscription and customer", "change subscription", etc. Common workflows require quite some coding, and there's no support for transactions! IMO a good API design should be more thoughtful than providing an interface to your database.

I don't think the documentation is especially well written, although it's not bad either. What's worse is that the stripe API docs hijacks my CTRL+F key so using my browser search is a massive PITA. This is such a fucking annoying fucking thing that I'll break my "don't say fuck on discussion forums"-rule for this. I fucking hate it. I tried disabling JS but that results in every navigation doing a full page refresh which easily takes over 5 seconds.

Also, browsing the docs isn't super slow or anything, but it's also not quite fast enough to feel "natural".

The checkout docs actually are pretty meh. Much of it is written in "tutorial" form and unclear on details.

As for the site design ... it often takes >5 seconds to load anything after clicking and it easily uses more than 100M of memory per tab. I recently wanted to load a bunch of customers so I opened them in about 10 different and my entire laptop just ground to a halt. I've actually been procrastinating on some Stripe stuff I need to do for the last week because I dislike using the UI so much.

Is it all absolutely terrible? No; it's passable, I guess. But do I share any of the enthusiasm in this article? Not even close.
I'm unable to dig out the link now. But from what I understand, it was not coded in the script. Instead, if you were someone from a developing country, you could email them about a discount and the site owner would then send you a unique URL with a cheaper price point. Not scalable at all, but I guess it works for the first several paying customers.
I perhaps haven't been using the phrase as originally intended, but I've always used the phrase "strong opinions, loosely held" when it comes to hiring and building a team, and I've found it incredibly useful.

The "strong opinions" part for me means hiring someone who not just has a lot of experience on some topic or technology, but they understand it at a very deep level. The strong opinions come from a place of perhaps having been burned hard by a particular technology or process (or, contrarily, loving a technology or tool for some reason), and being able to point out the 10 little details that turn out to be big issues in real-world usage.

The "loosely held" part to me means being able to trust that (a) you don't know everything in all situations and (b) most importantly you're willing to really listen to other people on the team and are open to the idea that you may be wrong.
> "We are winding [the promotion] down early. There is the impression we don't like among our consumers that there is a problem with the promotion."

Do they teach this in marketing school or do you pick up this kind of passive, responsibility-avoidance on the job?
The Venus of Laussel – La Femme à La Corne
acid to disolve the aluminium in the structure
It is not about then terminal, rather using it as if the world hasn't changed since V6 came out.

Ignoring REPL based workflows, structured IPC with GUIs apps for automation, ability to use any library directly, cramping text into a little window in a high definition screen.
Yes and no, depends. It gives such experience to a software architect, otherwise not really. Tho, software architects do a lot more than just systems design (tho, that is pretty much their main task). But yes, you get a job as a software architect or something like an "in-training" one, helping one, etc. at a big corporation to get such experience (I'd argue that small companies only need some code design, you want a lot of systems/software design you should go for a big corporation)
It's a bit weird but the point was that it was striking rather than a dull flat design with a lot of dark colors
It might imply that whatever path you take, you should also prepare a strong hedge in the other direction...?
>industrious tweakers with better tools

They're probably breaking in hoping to steal tools to sell. If they had decent tools they would have already sold them. It's not impossible but well-equipped tweakers are far less likely than other kinds of thief.

On the other hand they're batshit crazy enough to try other means, why bother trying to break into a storage unit when you can chain the door handle to your (also stolen) car and rip the whole unit door off.
They don’t mention what kind of blade was used in the experiment? Interested if it was a diamond blade or a conventional blade.

When pausing the video it looks like a conventional cut off wheel.
Their nuclear arsenal is built with Chinese and Russian brains, not NK's native technology.
U.S. Marines with E Company
A "cult" is an entity with blind followers who would go over the edge like lemmings.

Stripe is not that. They just built a good API, have made it more functional and easier to use over time, and have great developer support (go on IRC any time to chat with them). They accept criticism and fix problems. Cults don't do that.
Arthur C. Clarke's Hazards of Prophecy: The Failure of Imagination: https://fabiusmaximus.com/2017/12/27/arthur-c-clarke-hazards...
I think you're seeing what the benefit is, though: it feels like you're just using an API to some company's DB.

Payment processing is one area is that just a complete nonstarter to homebrew on your own. It's fucking awful. There's no choice. Bank's still require you to transfer them files via ftp to make transactions.

And god forbid the legal, and technical mess when you want to accept foreign currency, or even multiple CC providers.
I’ve watched a bunch of lockpickinglawyer videos and there are locks he cannot pick at all, and locks which take a hell of a lot of punishment from a Ramset gun. It’s not out of the realm of possibility that you could build a bike lock which would effectively deter thieves. After all, it doesn’t have to be indestructible, it just has to convince the thief that your bike is not worth the time and risk of attracting attention.
That's fair and valid, but shifting your culture from one that's laser-focused on shipping features that work to one that cares about shipping polished features that delights users definitely gets exponentially harder as your company scales in size.

The sweet-spot for making that transition is essentially as soon as you've found product-market fit, no later and no sooner, and missing that sweet spot even a little bit can make the transition very difficult and very costly. But the dilemma is, as most successful founders will likely tell you, we're only good at identifying product-market fit in hindsight, long after it happens (and it may never actually happen).

I've worked at plenty of companies that pay lip service to wanting to ship polished features that delight users while still overwhelmingly shipping features in a very utilitarian, timeline dominated fashion, long past the point where they've demonstrated product market fit.

As with anything in product/engineering/design, it's all about tradeoffs and striking the right balance, and where the right balance stands will always keep shifting under your feet as you make progress...
by everything you mean outside of programming also? Or just in programming? I guess I find DRY pretty important for me, as a tool to force me to abstract and to help me understand the system I'm working on.
Renaming the Default Branch from Master
> How do they store their data?

SQL.

> How do their different applications talk to each other?

Proprietary APIs.

> How do they scale their systems to work for millions of users?

T H E C L O U D

> How do they keep them secure?

They just... don't.

> How do they make sure nothing goes wrong?

They just... don't.

> What are APIs, webhooks and client libraries, when you really get down to it?

Easily outsourced to India.
Nothing in there on its electrical properties. Can it be cut using a plasma cutter?
While researching a reply, I uncovered USDA Technical Bulletin No. 1413: "Thermal Properties and Heat Transfer Characteristics of Marsh Grapefruit". Please enjoy:

https://hortscans.ces.ncsu.edu/uploads/t/h/thermal__51bf44b0...