skysight-inc/HackerNews huggingface dataset:
> Also, developers can have a good approximation to what the customer wants, even without talking to the customer,

Yoep, sure, maybe we even don't need clients. Just developers creating products for themselves. Or just coding for the sake of coding. I've seen that too mamy times. That's why we need product people.
Zero parse wire formats definitely have benefits, but they also have downsides such as significantly larger payloads, more constrained APIs, and typically more constraints on how the schema can evolve. They also have a wire size proportional to the size of the schema (declared fields) rather than proportional to the size of the data (present fields), which makes them unsuitable for some of the cases where protobuf is used.

With the techniques described in this article, protobuf parsing speed is reasonably competitive, though if your yardstick is zero-parse, it will never match up.
Those engineers have the good fortune to be working in a fairly constrained space. New materials and building techniques become viable slowly over time.

Software developers are able to build abstractions out of thin air and put them out into the world incredibly quickly. The value proposition of some of these abstractions are big enough that it enables _other_ value propositions. The result of that is that our "materials" are often new, poorly documented, and poorly understood. Certainly my experience writing software is that I am asked to interact with large abstractions that are only a few years old.

Conversely, when I sit in a meeting with a bunch of very senior mechanical engineers every one of them has memorized all of the relevant properties of every building material they might want to use for some project: steel, concrete, etc. Because it's so static, knowing them is table stakes.

I'd say this difference in changing "materials" is a big source of this discrepancy.
Devil's Advocate: Interview questions are almost never related to the actual job. Why would the candidate assume otherwise in this case?
If I see a job I am qualified for, and/or interested in, and I don't see a salary range I tend ignore it - I don't have time to entertain companies unwilling to be open about their payscales.
There was no need for the second paragraph.
Every technology comes with good and bad. Better and more rewarding to be an optimist!
> With an informal diagram language, you could create a project-specific convention, for example a small clock icon in the corner would imply presence of "date_created" and "date_modified" fields -- and the icon itself would also be explained somewhere.

The UML spec actually has support for this. It defines a special kind of 'inheritance' between diagram elements and ways to represent it, including iconically.
I also evaluated it and implemented an ABAC system for our Node.js app with Casbin in a day. The tooling wasn’t perfect and I probably took a shortcut or two, but I didn’t see any red flags that’d actively make me recommend others not use it, so I’m interested in what you found.
One of the things that turned me off of using Amazon for fulfillment when I was trying to run a barely ramen profitable hardware startup was that I might get stuck filing property taxes in a whole bunch of states. That and I was so broke that I could only afford to ship one box of inventory to one destination, and they insisted on splitting into multiple different warehouses.
There are several "trains to nowhere" in China. High speed rail is already active between Lanzhou (Gansu) and Ürümqi (Xinjiang), which is 1500km of pretty empty countryside. They're talking about linking in Lhasa (Tibet) too. I can't imagine any of those routes will be profitable, but perhaps the income from the coastal provinces makes up the difference.

I suspect in China there is more political incentive to connect these far-flung provinces, though, to try to promote national unity. I'm not sure closing the gap between the PNW and "middle America" is considered quite as important by people in DC.
> effective oversight mechanism

Hard to do when the people who really understand broadband networking are working for ATT, Comcast, and Verizon and not for the government.
Every person has his own definition of what constitutes a late-stage company. For me, a company qualifies as late-stage if any of the following are true:

1. The company has filed their S-1 (including confidentially, but there are rumors).
2. The company needs funding to grow their marketshare; the fundamental product-market fit has been proven and the unit-economics may be favorable now or soon, so the capital is needed purely to grow the business.
3. The company is profitable already and simply wants to be a publicly traded company, and the discipline it brings.
Absolutely agreed. I'm of the opinion that anything under DRM, and any closed-source software, should not be eligible for copyright. When a work enters the public domain, society is allowed to build upon that work. If extant copies of the work are not in a form that allows others to build upon, then that right is infringed.
If you are expelled from a school, the school is currently unable to rescind access to previous education they've provided you, although the analogy starts to fall apart since education and digital media are not directly comparable.
Wrinkled snout/nose does not close the airways nor prevents pathogens from getting inside.

I have to admit that if it would, covid would be way funnier. But, it does not. J
That depends on the definition of

> psychological harm

Are they going to go into a codebase and figure this out? If I use AI to pull these levers vs using a series of if/else statements:

if person.has_bought_multiple_items

increase_base_price(person)

that's legal I guess?
I don't think DRM changes anything for the legal aspect of going public domain.

I imagine that copies that were illegal with copyright (with DRM stripped) become legal once it gets to public domain.
Haskell does it, because being lazy evaluated helps quite a lot in such algorithms.
What is it about the anti-progressive undertones, to use your language, that caused you to stop reading him?
I’m currently working through Leetcode now. I’m really taking the time to understand the various solutions with the goal of bettering myself as a software engineer. It’s honestly just fun working on the problems.

Anyways, did you get the FB job?
Long ago I was part of startup based in developed country which was hiring people from one of developing countries. Salary offered was lower than if it was somebody from startup's area, but it was very competitive on the market where developers was recruited from. Developers was very happy to be offered salary higher than their peers, in the same time startup was happy to get qualified engineers for less money than it would have to pay if sourced locally. This would not work today because salary expectations are now similar in both countries - this same startup is now bringing those jobs back to the local market.

I was observing similar situation 15 years ago in one of big corps who outsourced everything to India. For a price of one engineer from developed world they was getting many engineers in India, and those engineers could afford services like personal chauffeur. I could not believe when I heard it first time from friends I have there. Again - situation now is much less in favor of big corp, which is now trying to bring some of those jobs back to the local market.
>being thrown around a technology that is dodgy at best

I have yet to meet someone that says this who has foreseen the implications of defi. In my mind, as an early bitcoiner, that was the original promise of bitcoin.

A list of coins by market cap is full of absolute junk: https://www.coingecko.com/en

A list of tokens by locked in value is full of systems that are revolutionizing finance: https://defipulse.com/ Defi protocols are providing useful services and are making money. I doubt I could overstate their enormity.

There's a huge difference between the two worlds. Don't confuse dogecoin's "I like the stonk" hype with Maker's muscle. The "blockchain" isn't the point. The systems made possible on top were always the point, and that's what makes "blockchain" so valuable.
Lots of people in the Northeast don't live in downtowns either. One big difference if that, if you're taking a trip to one of the big cities, you often don't need or even want a car when you get there. On the other hand, if you can drive somewhere in 4-5 hours, taking a train and then having to rent a car when you arrive seems a lot less attractive.
> What if your car insurance was more expensive because your last name was associated with an ethnicity that happens to have more car accidents than others?

But why is it fair to charge men more than women? AFAIK car insurance is more expensive for men
Couldn't companies just put "Licence to watch..." in small print above the name of the movie/item and then still say "Buy now!" on the button, because you are buying the licence?
It will never happen, everyone knows it. Just a hand out disguised as a plan for the people.
Looks like https://datasette.io/ might work for you.

Datasette is a tool for exploring and publishing data. It helps people take data of any shape or size, analyze and explore it, and publish it as an interactive website and accompanying API.
Is taking the bus between St. Louis and Chicago really more convenient now than the train (Lincoln Service)? Google maps seems to show Greyhound taking over an hour longer, by a less direct route (through Champaign). I've taken the Lincoln Service several times, though only Chicago to/from Normal or Springfield, and it was very convenient. Wish it were faster (and IIRC long-delayed upgrades aren't going to shave much time), but I'm glad it exists.
The largest software companies in existence were born during a time when the role of product manager did not even exist.

Just like the largest corporations in existence became profitable and expansive before they hired MBAs.

Product managers and MBAs are the best examples of the Texas Sharpshooter cognitive fallacy. You shoot into a wall and then paint a target around it. Being successful at those roles is about painting targets around any successful initiative and claim it was your idea.

Powerpoint presentations are not reality, picking up the customer service phone, auditing the code, talking to internal and external users and keeping in touch with reality is.

https://youtu.be/4JVJdKnbZu8

https://youtu.be/P4VBqTViEx4

https://youtu.be/Y6P8qdanszw

"We hire smart people to tell us what to do". - Steve Jobs
Again, paradox of intolerance. This is the same as thinking we shouldn’t use violence against those who use violence to subdue others.
IMO diagrams work best in tandem with actual docs.

"IMO diagrams" are my favourite type of diagram
No problem.

A possible downside for a potential employee is they could be a very qualified candidate who passes on applying for a position because the high end of the range isn't high enough but they didn't sufficiently factor in the other benefits. Salary is only one part of the value of taking a particular job, there are other monetary (lower out-of-pocket heath coverage, profit participation) and non-monetary (better work-life balance, more interesting work, better workplace relationships, etc.) factors.
There's quite a lot of hate in the comments for UML is seems. And while a lot of it is quite valid, I have to say that sometimes I miss _some_ of what UML could do, especially in form of documentation. Sometimes a simple sequence diagram is able to communicate the behavior of a system much clearer than 10's of pages of disjointed prose... Just my opinion.
Bad coffee is just nice in its own way. Like ordering coffee at 3 AM in a diner.
Seems to be similar to the "bass face" of appreciation: https://i.imgur.com/uVSSTSD.png
Try these:

Tom Pemberton: https://www.youtube.com/c/TomPembertonFarmLife

Olly's Farm: https://www.youtube.com/c/Olly’sFarmLtd

The Hoof GP: https://www.youtube.com/c/TheHoofGP (good one)
Similar to “You have to keep a dozen of your favorite problems constantly present in your mind, although by and large, they will lay in a dormant state. Every time you hear read a new trick or a new result, test it against each of your 12 problems to see whether it helps. Every once in a while there will be a hit and people will say “How did he do it. He must be a genius.” - Richard Feynman
I have to admit I had little interest in tail calls myself until I saw what they could achieve performance-wise. Now that I have seen that, I am sold. :)
Foo x = new Foo() is not the culprit.

LinkedList<HashMap<MyFancyBusinessObject, String>>> is the culprit.

Also something I don't like with Java is that it is a lot of ceremony to actually start a new greenfield project or script in it. My favorite experience with this sort of thing is Racket where I just launch DrRacket (after ONE very easy install on any platform), start writing my program, and hit run. I don't even need to save my program if I don't want to (it does autosave though so you probably won't lose your program even if DrRacket crashes!).

To be fair to Java though, jshell is a very nice REPL which is surprising for a language like Java. It is actually my preferred way to do one off date calculations since most languages don't seem to have a nice way to do date arithmetic built into the language itself.

The situation with one off scripts is something that could really be improved in Java by having a dialect which just runs the file top to bottom like C# recently did with top level programs.
Yes, it's like that, but with the completely unregulated trading environment reminiscent of the Roaring 20s. That's why it's much, much worse. The dot-com bubble was driven by margin, enthusiasm and poor decision making. This one's got all those plus the hallmarks of the 20s: insane leverage (see: DeFi), bonkers leverage (see: BitMEX), and a fictional currency being printed at a rate of billions of dollars per week that's then used to prop up the prices of the assets themselves.

It's basically the dot-com bubble, the roaring 20s and 2008's CDO shell game rolled into one.
The smallest size at which English capital and lowercase letters are differentiable is 3x5, so 5x8 is pretty close to that minimum possible size. Any smaller and some letters become ambiguous or lose too much information to be unique (e.g., B vs 8). I haven’t checked to see if 3x5 can include symbols though, only the letters and numbers.
Decades of coding here.

Buildings neither are Turing complete, nor do the building blocks become obsolete every few years.

The closest analogue to software development is legislation.

Even the best written rules can have unintended consequences, and so we have tools to make the behavior ever more precise and less error-probe. But it’s
never fool proof.

Also and like legislation, it’s the edge cases that balloon a proof of concept into monstrous sizes.

In some respects, for software to advance some components need to be less powerful. But we have this fetish for inventing yet another Turing complete language in the pro space, just because, and bolting on a million features.

It’s unnecessarily tiresome.
I mean it's on you since you're making the assertion.
IBM used to push the adoption of their business process software for exactly the same reason. They imagined that "business process experts" use UML to construct the entire business process, and then the software (based on WebSphere Application Developer, an Eclipse-based IDE) will generate all the execution code, including deployment scripts. The irony is that the UML itself becomes more complex than code, and dozens of layers of exception trace were simply incomprehensible to engineers, let alone to "business process experts". To add insult to injury, IBM mandated generating tons of EJBs. Even thinking of that induces migraine.

P.S., It's surprising that those who advocate that UML is better than code didn't understand the essential complexity would not go away simply because we switched a language, as essential complexity lies in precisely specifying a system. Neither did they understand that that a programming language offers more powerful constructs and tools to manage complexity compared with UML.
Thanks for connecting the dots!

I'm familiar with the OpenFPGA stuff but hadn't connected it to the folks listed -- consider this an ask to have bios on the site as I evidently picked the wrong people to google. It's great to know there's more than meets the eye here beyond a vague press release I can't make heads or tails of.

Looking at other hardware-related foundations (like the RISC-V foundation) there are explicit callouts for "individuals not representing a legal entity," which is where someone like myself would fit, but the bucketing on OSFPGA makes it seem like people in this group who are not students (for example, me, not that I'm particularly special) don't have a place here. (As an aside, I dislike how many orgs collapse members and sponsors into one thing, but that's neither here nor there).

Finally, I didn't mean to imply that the work I mentioned came whole cloth from the respective author's heads. Sorry if what I wrote conveyed that.

PS: When is Zero ASIC coming out of stealth? :)
My AP CS class covered UML, I haven't seen it anywhere else. Diagrams, yes, quite frequently. UML, never once.

I put the bare minimum of time into studying UML, and I'm glad I did.
I think it depends on the company. Some companies (GitLab) seem to (or used to) build location into their salary calculations. Others (Automattic, where I work) don’t, or at least try not to. But even expanding that to situations where you move, both companies I mentioned state that they don’t reduce salary in general.

At Automattic, that means you would get paid the same if you started in HCOL and then moved to LCOL. But at the same time, you might theoretically start out making a bit more than average in LCOL or a bit less than average in HCOL, depending on your situation and experience.

Some more info: https://techcrunch.com/2020/05/26/how-automattic-pays-its-re...

Disclaimer: I don’t know the exact specifics of these programs, just sharing some basic info :)
Protobuf is also used as a format to write data to disk.
Got it, I thought you were referring to the demise of Java applets.
This is a nonsensical question and of course there is no answer.

Any time you are asking about universals in regards to the lived experiences of human beings you need to take a step back. This principle applies to issues many orders of magnitude less complicated than employee pay which i think goes to show how absurdly far off track this question is.

To illustrate the point,say you conclude some "universal pay" (good luck even defining what that means, who it applies to and when it applies) . Why do I care? I'm still going to go live my life and maximize my pay for my particular situation. So your universal pay is already not universal after the thought experiment of trying to apply it to the first person who you cannot directly control .

You'd be just as good debating how many angels can dance on the head of a pin.
Hah! The funny part is, you think they don’t mess this up all the time, but they do! We all have experiences with buildings that are impossible to navigate, have weird maintenance issues (toilets always backing up, A/C a nightmare, rooms too small, rooms too big, not enough useful space, etc). Buildings get redrawn constantly during construction, and they rarely match the plans. Cost overruns are endemic, as are scheduling issues.

They’re also using literally thousands of years of deeply ingrained cultural rules and expectations focusing on making living in and building structures effective (it’s one of the core tenets of civilization afterall), supported by an army of inspectors, design specialists, contractors (themselves leveraging thousands of years of passed down and deeply baked in expertise in everything from bricklaying, to concrete work, to framing).

All that for what, functionally, is a box we put things in, including ourselves, that we prefer provides some basic services to a decent standard and isn’t too ugly.
Delays can have cascading effects. And if a freight train is delayed, or breaks down on a crossing track at 5:00pm, it's not like it can get out of the way just because Amtrak is scheduled to go through at 5:15.
I think there's a quality-of-life factor worth considering too.

There's value in stability for many people. Maybe they've be happy with being a dishwasher or whatever for the rest of their career, so long as they can pay the bills.

Living on a cycle of "oh, your job has been DISRUPTED(tm), go learn how to be a (trendy new job)" every few years is going to be frustrating and stressful at best. A lot of opportunities to choose wrong or be stuck having to upend your non-work life to serve this change.

We can improve conditions for low-skilled workers by cranking up regulation. It's not just about a $15 or $25 minimum wage, it would be things like replacing "right to work" with "you can only fire with cause and ample notice" and perhaps regulating the "shift from three full time employees with four who are each booked 29 hours a week to avoid getting benefits" strategy. Maybe we outright restrict automation-- if you're going to displace a worker for a machine, you'd have a social and legal obligation to support that worker until he gets back on his feet.

Of course, people will turn on the water works and claim this will ruin small businesses. I believe they will adapt. If anything, removing the worst actors from the market might reduce pressure in the market overall-- you can charge the extra dime for a burger knowing the guy buying it is making a living wage, and you don't have to try to compete with someone who's managed to unload part of his cost structure on the food-stamps/medicaid/social welfare systems.

There's also the claim that this will accelerate automation, but I'm wondering how long that Faustian bargain is relevant. Even if we said "okay, you can pay your burger flippers $1.50 an hour to discourage you from replacing them with robots", eventually the robot TCO hits $1.49 per hour, and the deal's off. We're going to have more workers chasing fewer jobs, and it's unrealistically optimistic to assume "we'll keep retraining and inventing new jobs to take their place."

The other option is to extract low-skilled workers from the market economy: create state guaranteed-employment programmes to absorb their labour. They don't have to make a business case for paying people a living wage, or not replacing them with robots, since the purpose of the programme would be to stabilize society as much as it would be the "label on the box" purpose (environmental cleanup/infrastructure maintenance/educational support/whatever trendy thing we think up next) It always bothered me that you can get a guaranteed government job if you want to shoot holes in brown people, but there's no similar opportunity without the violent intent.
Heroku-style deployments with Docker and Git tags