skysight-inc/HackerNews huggingface dataset:
Rule #-2. A profitable business will require lots of smart schlepping. There is no reward for hard work unless it's produces value.

Rule #-1. Build a defensible business, not something that's trivial for competitors to copy.

Rule #0. Don't make a big, absolutist list of "dating rules". Be flexible and use good judgement.

Rule #5. Freemium can be good in many situations: when just out of beta, revenue is plateauing AND marginal user app infrastructure costs are low. You wouldn't do a cloud backup with unlimited storage like BackBlaze as freemium. You would with LucidChart because it costs almost nothing (so long as there aren't huge file attachments). It is smart in certain instances because of long-term economics, free word-of-mouth advertising, future sales and because it builds goodwill that enhances the brand. It's vital to steer enterprise users away from freemium because they have more needs that are better served with pricier support subscriptions (the "Enterprise" version).

Rule #22. If you're selling a physical product or b2b service through channels, then trade-shows are a must. It's incredibly foolish to shut the door on distribution when you don't have it. Then again, physical products are a PITA.

If it were me, early on, I would corral all the other founders for brainstorming on the Business Model Generation chart to consider what's needed right now and in the near future with some sticky notes. Then, revisit it regularly with periodic founder meetings to make adjustments.
> A piece of data categorized this way must come with a "Relative to what?"

This would be a good caveat to add to the original post. :)
Lots of fun.

Feature request: permalinks for results to make it easier to share them. My results showed "Created by TheseLyricsDoNotExist.com generation number #NNNNNN" at the bottom, and it would have been nice if that came with a URL to go back to them.
Hacking my arm prosthesis to output CV so it plugs into my synth
Pyramids are the perfect analogy to disprove your point.

The pyramids were useless tombs that wealthy kings wanted because of religious beliefs.

As an engineer, I have spent many months building features that were disabled/deleted because the measurements showed they were no good after release.

Now, for the 1% of product managers who make the right call every time on their own, having an engineer participate in the discussion may be a burden. But in my personal experience, every product discussion I'm in I bring great value to.
Everytime someone offeres top X things to as a startup, I immediately go on the guard. 9/10 times, this advice is useless; 5/10 times it is harmful. My mantra is do not follow any advice and prime your brain with it. It turns out, no one really knows what's going on. They're trying things out and see what sticks. From Harvard MBA folks to your mom and pop shop that sells craft supplies.

Please, I plead people on HN to stop listening to advice from people like Sam Altman, they're akin to "How to become a millionaire" books that you find at the side of the grocery store aisle. It is tabloid material that fills your brain with false knowledge. Next time a problem comes up, instead of thinking it through you immediately line up the dots and remember reading some solution to it.

On the other hand, read engineering, science and mathematics books. Master statistics and probability. These are universal constants that will always help you. Learn accounting. I see the irony of me providing advice in this rebutal, but there is a distinction - learn universally true things that have data, backed by math and science. Those will always be on your side because that's how nature really works. Otherwise, you'll get stuck in local optimum of following the crowd.

No offense to the author, I am glad things worked out for you the way it did. Remember, they won't work out for others and if I were you, I would not speak with such confidence and authority - it stands on stilts.
You might want to consider building a chrome extension. Users might have problems recalling your site.
Is it just me or does looking at write logs to determine read consistency just seem like a really bad way to do this vs a different load balancing strategy?
I think the main point was that /u/wesammikhail seemed to claim a position that either didn't exist or was illconceived.
Keto Diet Beginner's Guide: weight loss
Google cloud is eliminating few roles
I imagine if you took a look at total compensation (vacation, PTO, insurance, maternity leave), stronger labor laws and other societal benefits such as cheaper college, those workers earning €11/hr would probably be able to save a lot more of it compared to their counterpart in the US.

And bonus if they get sick, they don't have to worry as much about losing their job and spiraling down into crippling debt.
Thanks! Will do. No wonder the three.js repo takes so long to download :)

You probably aren't seeing the AST optimizations because they are actually in the parser. Search for "mangleSyntax" to find the optimization code.

This would normally be done in a separate pass but I'm trying to minimize the number of passes done over the full AST for speed. I figured it'd be faster to optimize the AST as it's parsed because the newly-created AST nodes are likely to still be in the CPU cache. That said, I haven't tested the performance impact of doing this. I just did this based on intuitions from performance work on previous compiler projects.
SeaTrain is not a new idea, but certainly viable. We actually built one last decade for another agency and it works well. There are other great ideas floating around (no pun intended) that DARPA simply takes a long time to act on, but I suppose there's only so many hours in the day and money in the coffers.

If you're interested in this, I recommend you also check out the NOMARS opportunity (1), the solicitations for which are only offset by approximately 1-month.

It's an interesting time for ocean going vessels. In my opinion, ship autonomy is ushering the biggest advancement in marine engineering since the advent of cargo containerization (and before that the switch from sail to propellers). Not the autonomy itself, per se, rather it's what autonomy allows in terms of new flexibility of hull form, power and propulsion design.

1. https://beta.sam.gov/opp/dc4233cf116e4852ba4c7b436db95ae2/vi...
I thought this too, but that then creates a likely unreasonable burden on the client. Not all user agents expect cookies either, think of all the varieties REST clients. Sounds like they would also need to internally reference the lsn too, so being able to look it up internally would be valuable.

Feels like there is something there tho in terms of approach, esp since they are keying it on user id.
This is a very strange comment IMO. There are already perhaps too many XML and JSON handling libraries for Object Pascal, as well as libraries for pretty much anything else I can think of.
It sounds nice, but it doesn't work very well.

Users lie. Not even maliciously.

Clients will say they'd pay for it, then when you deliver it they'll say they realized that your competitor provides that and everything else that is really important to them in the standard fee. The competitor is actually no better, and would require the same amount of development to get to parity in other areas, but they win by claiming that everything will be rainbows.

Clients will say they'd pay for X, but once you deliver it they'll suddenly realize that it won't actually work for them until you also implement Y, but they won't pay any more for X+Y than they would for X alone.

Clients will say they'd pay for X, but once you deliver it they'll have shifted direction or something has changed and they don't need it anymore.

Clients will say they'd pay for X, but once you deliver it and they start using it they'll discover that it's not at all what they actually needed.
YourHomeworkPlanner: The Future of Online Schooling
Typically we've left the implementation details to the developer working on the tickets.

* One dev does front-end for both and the other back-end for both, potentially by pairing together on an initial PR which adds a skeleton of the API so they agree on it. *

Isn't this essentially just a horizontal slice? So you would subtask this horizontally but the story itself would be vertical?
That oven loader robot looks like an ABB IRB 2600. I don't know the exact cost, but it has to be around $50K new, minimum.

Has anyone explained to Zume that the restaurant business is low-margin?
> I attempted to see a specialist for a condition that I had maybe two or three times, I ended up giving up every single time after I was told the wait time is between 3-4 months. I keep my American employer sponsored private insurance and employer determined time off policy.

I am in the US and go to good dentists and doctors, who are out of my insurance network incidentally, and they and the specialists they refer me to can easily have three month waiting times.

Also Sweden has been following the US lead of cuts and privatization since the 1990s, often led by the Social Democrats. It's a great strategy for the idle class - push through public health spending cuts due to costs, then bemoan the inevitable wait times as reason to privatize.
> To which I have to ask, why is that a problem? Because its a hotbed for hate speech?

Because the moment a troll shooter posts his manifucksto to a site, that site becomes "linked to terrorism" and it becomes our social responsibility to shut that site down and ensure that sites like it never rise again. Based on which comments get modded up and which get modded down, this is Accepted Truth on Hackernews.

If these principles were applied consistently, what should we do about the newspapers, magazines, and web sites that ran the Unabomber's manifesto in the 90s?

Oh, right. Marcuse's principle of repressive tolerance kicks in. That tells us we have a social duty to legally protect expressing a leftist perspective and to criminalize expressing a rightist one.
I haven’t used The Lounge; it looks well-designed, but I try to avoid web-based clients as they have a lot of overhead. It also doesn’t seem like The Lounge has any solution for push notifications on iOS.

(Alas, most ‘native’ IRC clients for macOS have web views inside anyway, so avoiding web-based stuff may be a lost cause. But then I’m in no position to complain about Slack or Discord using Electron…)
I would not expect return to RTL/DTL but iwould not be surprised by use of NMOS-style pull-up transistors/resistors in combination with traditional CMOS logic. You can make NMOS gate in CMOS process quite easily and it comes out significantly smaller. Doing DTL in CMOS process seems somewhat pointless given the fact that simplest way to make diode-like thing in CMOS is transistor. And then there is the issue of small fanout of RTL/DTL.
>why the hell can I not know how much stuff costs up front

Prices should be publicized, I agree, but you can ask to get something pre-authorized. It just takes longer.

>why can I not tell them no I dont an unnecessary x-ray

You can ask your doctor why you need an x-ray, why they deem it necessary, and refuse if you like

>and why am I not told cost owed by me until after the procedure only to find out it's just an absurd amount of money

Again, you can ask for pre-auth.
> I've worked at little startups and a medium-sized tech company as well as FAANG. In each case, we spent most of our time working on projects with 2-3 month time horizons. The small and medium companies called their development strategy "agile". In FAANG we mostly just did our work and didn't spend any time on the Kafkaesque exercise of "sprint retrospectives" and "grooming sessions". Our product manager didn't tell us what to build, but acted more as an advisor for the engineering team leads.

Wtf? I've worked mainly for startups, with a couple of large companies in-between, and I've had the exact opposite experience. The engineering in every startup has been fairly lean and efficient with a few mistakes here or there, and every large business has been an 'agile' hell where everything feels ludicrously slow and nothing gets done.

I've always avoided interviewing with FAANG etc because I just assumed they'd be in the latter category with the sheer number of employees they have. It's interesting to hear that Facebook actually runs smoothly.
Show HN: SocialPlanner – Find, plan and publish engaging content
The real story is that for Google, Microsoft, and Yahoo, among others, there are infrastructural reasons they can't easily support DNSSEC; it’s a problem these guys have because of how they’ve architected their global email infrastructure, etc.

However, MTA-STS has its own issues: [1]

* Still can and should prefer DANE outbound
* Authenticates domain control via CA leap of faith
* Vulnerable to MiTM at cert bootstrap
* Vulnerable to weakest root CA, and unauthorized certs
* Open to downgrade on first (or irregular) contact
* Complex mix of HTTPS, unsigned DNS and SMTP

Given these caveats, I'd say to Google, Microsoft and the rest: good luck with that.

All standards are about tradeoffs; even though MTA-STS isn’t as good or as battle-tested as DANE’s TLSA, it’s something they can implement fairly quickly versus what it would take to rearchitect so they could do DNSSEC/DANE properly. I suspect if they were able to start over, they’d do something differently, but it is what it is.

We shouldn’t be too surprised; DNSSEC implements a distributed chain of trust and that doesn’t work with the increasingly centralized systems the largest email providers run.

It has nothing to do with a lack of confidence in DNSSEC and DANE since we already know about the nearly 2 million domains with signed MX and DANE records and the over 5000 domains hosting DANE mail servers: [2]

[1]: https://youtu.be/A8SgW9y__io?t=5875

[2]: https://stats.dnssec-tools.org/#graphs
Are they worried about the AI or the robots? Because there are lots of rape fantasy hentai/manga games out there already that allow people to engage in that pattern of thinking.

Seems to me that a person won't buy a rape 'bot unless they already are turned on by it.
I emailed pkg-ruby-extras-maintainers@lists.alioth.debian.org FWIW
>She definitely didn't shop around

Why not? So she wanted to go to a specific doctor, and that doctor had a waiting list. How does any other system solve for that? A single doctor can only see so many patients.
Sadly this is the case in our company. I worked as a dev team manager for the last 9 months and I was constantly wondering why do we work on these features...

The more time I spent with our CEO though, it turned out that he wanted to decide everything feature-wise. When I proposed that we should maybe do some market research or user interviews instead, he boldly declared that he knows the market the best. So go figure. No wonder that the whole company is a shit-show and we're losing a ton of money each year. Also when new features are prioritized I dared to propose to other managers that maybe we should tie the priorities to our business plan. Again our genius CEO told us that the business plan numbers should not be taken very strictly.

The more I thought about this why would anyone give money to such a moron, I figured that he is basically a very effective sales person. He can easily convince you how great he is and his vision, but he lacks all kind of strategic or operational skills. And as someone commented here in HN before, he also has management myopia: "If I can't understand it, it must not be hard" he probably thinks.

There was even a case when we looked for a product manager. This is not exactly the CEO's fault, but even 8 months were not enough to find one, even though that we interviewed perfectly capable and matching candidates. But there was always at least one person in management who found some excuses to ditch the candidate. Now in hindsight I think these people were afraid that the current status quo of the feature factory would change, so they sabotaged the whole PM candidate screening.

So now everything in our company is as it is written in this post. Success theater (this might be the same BTW that is called vanity metrics by Eric Ries), no connection to metrics, no connection to user values, hand-offs, etc.
Is this an HMO? I signed up for one once and the delays were pretty stupid (even to get a referral to a specialist you needed to come back to see a different doctor first). I've never signed up for the HMO plan again since. With a PPO you can always pick another specialist that is available.

Meanwhile there are companies in Canada that help Canadians get their MRI's in the US because it's so slow there. And clinics near the border advertise in Canada.
i stopped answering my phone a long time ago, if someone really needs to contact me they can text, email (no guarantee on that though), or hit me up on discord, no spam there
> Together with Chrisi from KOMA Elektronik and my husband Daniel, I am in the process of building a device (the "SynLimb") that attaches to my arm prosthesis instead of the prosthetic hand. The SynLimb converts the electrode signals that my prosthesis picks up from my residual limb into control voltages (CV) for controlling my modular synthesizer. The SynLimb thus allows me to plug my prosthesis directly into my snythesizer so that I can control its parameters with the signals from my body that normally control the hand. For me, this feels like controlling the synth with my thoughts. I show the prototype(s), explain how we put it together and how it works, and do a little demo.
Is this for companies that are 100% remote or for companies that include distributed roles?
LOL. so is brainfuck, but why don't people use it for everything and anything? Just because something is turing complete doesn't mean its well designed.
I have worked at a variety of companies and on a variety of projects. What kind of cadence works varies widely. And the factors that go into it are everything from what kind of software it is to the codebase to the organization it is embedded in.

There was one reporting app where I was the sole developer and it was only for internal use. My regular cadence was that I would field a series of questions every day. Better than 90% of the questions already had a documented way to solve it. But many days a new feature would be needed. Most features were delivered on the same day. That was a fun project, and my reporting system wound up adopted in every department of that company.

I have worked on a legacy codebase with a Kanban style ticket system. Most features were delivered in less than a week. However a significant fraction of "features" were actually bugfixes. Such is life with legacy code.

I have worked on systems where features realistically took a month or three, but we pretended to biweekly sprints. The sprint cycle seemed silly there.
Facebook GDPR data processing consent
If you hire people in a country, follow that countries laws. Not doing so makes you a shit employer and I hope you get caught.
Yea, that's always the issue. An extension would be ideal for desktop users and was considering that as a feature, however, for this initial release, I didn't want to alienate any mobile users that may not have the ability to install an extension. Appreciate your feedback and glad someone has the same idea, definitely makes it easier to prioritise features going forward.
Maybe we'll have to disagree because I'm still pretty sure nodejs is somehow slow.
The problem with that assumption is that while those solvers are based on a mathematical foundation (though I'd argue that some NN based simulations are too some papers out of Weinan E's lab at Princeton having some decent math to an untrained eye), the parameters that are fed into those are often just fit to some experimental data. And are often only verified in a heuristic manner. So while a neural net based simulator may not be transferable in the same way as a more general simulation engine (though depending on how you write them even they generally have limits), it may be fine in a certain domain which you can show by just checking how well it fits to certain experimental data you already have in existence.
The serial numbers of NSA reports
I just use s3_website. It works well if you have Java installed.

https://github.com/laurilehmijoki/s3_website
> No computers that project images on eyeballs...

Actually, we have something close to that now:

https://www.kickstarter.com/projects/tiltfive/holographic-ta...

It doesn't use lasers though.

The tech is basically working, and they're ramping up to production this year.

And no, you can't just walk around arbitrarily, but you couldn't do that in the book either (you could walk out of range). Also, Stephenson didn't worry about just turning your back to the laser projector...
But it’s a career. Work defines a career.

If a crappy PM wastes an engineer’s time by having them churn out useless product features, the PM is ruining their own career and the career of the engineers.

It’s important to work on meaningful work in order to have a meaningful career. That doesn’t mean everyone needs to heal the sick, but it can mean a PM doesn’t waste my time making me do stupid shit like build a feature no one uses.

It’s very difficult to level up if you never build anything worthwhile. PM’s should focus on getting it right the first time or not doing it all, because in the world of software development, adding technical debt for something not worth anything anyway is worth less than doing nothing at all
Oops, I typoed. I said 'new *printf functions'; the example was supposed to be 'printf2("int64: %d64", x)'
Leptin Resistance for the Woman and Men Who Want to Lose Weight
>> When engineers and other ICs read this article, they tend to assume that these ... mechanisms aren't happening because they don't personally see them

I think you're missing the second point of the article here. Per the article point 1 "Or, if measurement happens, it is done in isolation by the product management team and selectively shared. You have no idea if your work worked"

So the article is also highlighting failure to share as a failure mode. Every good company I worked at, I [the lead engineer] had equal ownership as my product owner. The respected my opinion, learned not to doubt my warnings, trusted my intuitions, and made adjustments based on my recommendations.

That balance of shared ownership is a defining indicator that it's not a feature-factory, whereas a "I call the shots as product" mentality is more feature-factory.

Is it possible you [rightly] worry about this article because you are what it's talking about?
"Comparative advantage [1] in X means you suffer a lower opportunity cost"

Yes, however I don't see a relevant difference between that and my phrasing.

It still looks to me as though you were clearly describing a lack of competitive advantage, while using the word comparative. Sure, you can discuss comparative advantage if you want.
I take notes in class or in a meeting with pen and paper mainly because tablets still suck at this and typing on a phone isn't much better. The downside to this is organizing them after the fact. Especially if you don't have a lot of free time. So oftentimes my paper notes are a mess.
TL;DR: the couriers tend to eat them.
Ask HN: Starting my first real email campaign to cold and warm leads, any tips?
Yes, the basic business model of a coffee shop worked. What Starbucks did was codify best practices, and worked on efficiency to scale-out.
So not at the beginning of the trial then.
I use node.js in AWS Lambda because I run Clojurescript on top of it.

My application (https://operatr.io/) is Clojure (JVM / Back-end), Clojurescript (Browser / Front-end), Clojurescript (AWS Lambda) - there's enormous leverage is using one language in all cases.

I have at least one function that exists in all three environments, but more than that I have one common language for delivery.
It is common knowledge. Here's a video that goes into more detail: https://youtu.be/P_UVPTdjxC0