skysight-inc/HackerNews huggingface dataset:
Like here, just to make the point, here is a quote I saved from a Scott Alexander Substack discussion of Georgism. I liked this so much I saved it in Notion, sorry I don't have the commenter's name. If you read a lot of Georgism stuff, you'll notice that they call literally everything 'speculation'- if you want to, you know, live in your home, that's greedy 'speculation' that an LVT will stamp out:

"A greedy land speculator (middle class home owner) refuses to develop a vacant parking lot (refuses to sell to a McMansion developer) because he can let land appreciation pay for his refusal to develop (let him stay in his home).

Since the villainous speculator and the heroic homeowner are economically the same, any consistent LVT has to essentially force the home sale. That is the entire point of the LVT"
I just wrote the search query to our PM, since I was unable to find anything myself... I don't understand why just couldn't use, IDK, a shared spreadsheet, even that would be more productive (from my perspective)
You're misquoting me. I never said they were extremely fortunate for choosing one model over the other, I said they were extremely fortunate for "being able to choose form over function." When wildfire season rolls around and air becomes very hazardous where I lived, local air purifiers of all kinds were completely sold out, and the box fan solution is all a lot of us had[0]. It's not just inexpensive, it's about availability of materials.

>just to try to dunk on someone

You're attributing negative intentions to my posts, which isn't appreciated.

0. https://twitter.com/seattlefire/status/1425260701568970752
Back in 2008-ish a lot of projects I came across tried to use Redmine because their company had a sucky JIRA or sometimes even Mantis implementation. Redmine turned out to be highly unsuitable in a matter of a few months and after trying out a few options that are mostly just tickets+kanban boards, it turned out that the simplest 'fix' was just setting up an individual JIRA just for the team so it could be used properly instead of some heavy handed top-down "use this tool in this specific way" approach. Once more teams started to do it, the 'company-wide' JIRA essentially just contained managers and a few product owners and it got deleted in a year or so.

Afterwards, all the 'team JIRAs' got merged into a normal JIRA again, but this time everyone had full control over their own projects and boards, problem, solved.
The thing with 4hr technical assignments is that you're saying no to anyone with kids, which I'm going to venture applies to more senior people than juniors.

I used to do these assignment. Now I simply don't sorry.

My schedule is

6:30 AM wake up with youngest daughter, to let wife sleep in (she takes care of her all night)

9:00 AM hand off youngest daughter to wife, who takes both girls the rest of the day. I go to my home office

12:00 PM lunch with family / kids

1:00 PM back to work

5:00 PM off work... Cook dinner / watch kids while wife cooks dinner. Set up table. Eat with family.

6:30 PM Play with kids for an hour

7:30 PM Bathtime + off to bed

9:30 - 10:30 PM Infant child actually goes to sleep

10:30 - 11:00 PM Wife and I chat about our day and spend 30 minutes of time actually being together

11:00 PM sleep until 6:30 the next day

Exactly where in that schedule am I supposed to fit a FOUR HOUR coding assignment. That's ridiculous. Unless you're providing child care, this is simply too much.

A one hour interview... I can handle.

Perhaps you'd get better leads by allowing for a choice. For my last job search. I had several different companies all in the upcoming AI accelerator space. Two of them had assignments. I said no thanks. The others did interviews. I got a good raise (base + stock options)anyway. I don't think I lost anything saying no to the ones with assignments.

Alternatively, perhaps pay people to complete the assignments.
This short film comes to mind: (Uncanny Valley)
https://www.youtube.com/watch?v=1AvyUWUKCw8
Your process seems reasonable. How detailed is the job spec? Is there something you could add to it? Is the screening process by recruiter consistent?
I did not write an argument against property taxes. I wrote one against abusing the properties of taxes to achieve goals beyond the primary purpose of taxation.

I will read your link this evening.
It's replacing any previous web text editor UX components that we had in the past (likely DraftJS). We're also building Lexical for iOS which is slowly rolling out across iOS devices too.
So you require 90 minutes of interviewing followed by a 4+ hour long unpaid homework assignment complete with a presumable additional hour of presenting the homework assignment to a team without them knowing what the pay could be.

I think you'd have to not have many other opportunities to be worth putting up with that much for the potential for a job. Imagine if they interviewed at even one other place that required this much from them, they wouldn't have the time.
This isn't suggesting that the things that you publish be one sentence per line. It's suggesting that you write one sentence per line, polish the individual sentences (and question their right to exist at all) then edit them into paragraphs. You might have assumed this assume this by noticing the fact that the article has more than one sentence per line.

> Who is the judge of 'it improved my writing more than anything else'?

Who do you think? Who wrote the article? The word 'my' might be a hint.

> What was the 'anything else' for that matter.

Would you give him permission to describe one practice he adopted while writing without describing every single step he's made in learning how to write since he was a child?
The only point was to confirm that Wirecutter doesn't always actually test all of the products they review, regardless of whether it's (arguably) justified in each individual case.
We added a team-managed project a while back, and built a really good workflow around it that satisfied the needs of everyone who works in that project.

We can’t easily replicate that workflow anywhere else. This isn’t the end of the world, but I should be able to create a new team-managed project based on another team-managed project and then modify its workflow separately. So far, I can’t figure out how to do that.

I’d love to take the team-managed workflow and promote it to a company-managed workflow now that we’ve experimented with it. So far, I can’t figure out how to do that.

Don’t get me wrong, I really hate JIRA. I’ve written my own bug tracking system. I’ve tried lots of other tracking systems. JIRA is wrong on so many levels, but eventually you hit something in one of the other tools that you cannot address with those tools, but is possible (but painful to configure, and it might cost you extra money) in JIRA.

The only other tracking system I really like is GitHub issues, but it also has problems and limitations. And then you have things on GitHub that actively make things much worse (the autoclose bots; forms like the ones that Vue puts up, etc.).

I’ve never seen any organization need the level of complexity that they end up using in JIRA (especially the access permissions, which consistently get borked sideways), but most organizations eventually need something better than Bugzilla, Trac, or Github Issues.

The other difficulty is that switching bug tracking systems is tough. I want to really try Tara, or ClickUp, or Monday or a few different ones, but adding another tool is literally adding another tool. This is the same reason we’re using Confluence, even though it’s objectively the worst wiki in existence.

I hate Atlassian products with a passion. There’s nothing better, and the cost of switching is too high.
Getting to a 'very high LVT' is not something proposed to happen overnight. Mortgage debt also has to be considered since this is simply 'capitalized future rents'. Additionally, the process would include a tax shift, that is the reduction of other taxes as the tax on land is raised. Only after a revenue-neutral tax shift was concluded would further increases in land value taxation occur.

Given the fact that renters (who generally have less income than homeowners) can manage to pay the annual land rent every year, homeowners will manage just fine.

"Furthermore, as we discuss in more detail in our paper, the number of net winners from this reform would far exceed the number of net losers, who, if necessary, could be exempted or compensated at little budgetary cost." https://voxeu.org/article/post-corona-balanced-budget-fiscal...
I absolutely don't use my valve index as much because of the mess of cables and now my desk is in a weird spot colliding with my tracking stations.

I also don't use my quest 2 because the fidelity just isn't good enough.
I guess these are some of the issues that the committee examining the possibility of an open category are considering. I would think it makes most sense to require people to choose, and not compete in both the open and one of the sex categories. Whether people get excited about the “open” competition is up to them. I think it’s pretty easy to predict that it will be populated by men like Lia Thomas who don’t want to compete in the men’s competition, and there won’t be many people who care about it.
Ironically, most of the stuff seems to be about Confluence. And almost all of the commentary is about bad company workflows and bad company processes and not really about the product itself at all.
Totally food for thought, but here are my 2.7349 cents:

The hiring process doesn't seem to, and of course this is totally an completely assumptive-- based only on the list of items in your post, reflect any reason why a senior engineer would want to apply there. Most people want one of two things: more money or more growth. Right now, I'd guess, that potential candidates aren't feeling either from the ad. Is the salary actually good? Reading the job details I can say I'd expect at least ~$200k/yr cash, some sort of yearly cash bonus, and equity in the company.

Additionally, there may be language in the job ad; which, turns off more experienced candidates, e.g. "ninja," "rockstar," "10x". Very subtle changes to the language you use can completely change your applicant pool for both good and bad, it's worth experimenting via services that help with this (by reviewing the job ad) or consultants (though I'd try a service first, gonna be a lot cheaper).

Finally, seeing your stack being ops related, I'd guess a lot of qualified people are assuming you don't pay enough or will have awful work life balance. Are folks on-call 24/7? Salary might be alright unless your on-call 20% of your life-- in which case maybe it ain't. Speaking to that in the ad might really help pique some folks interests (if the work-life balance is good).

Good luck!
> Surely people aren't specialized in... Jira-ing or whatever.

There are people who build their careers on this. Their are consultants who do this, and only this. And the unfortunate reality is, Jira is so complicated, there actually is a reason for these people to exist.
>There's no VR content that is held back by the graphical fidelity atm.

As mentioned by the other comment, the ability to read text clearly is important and missing. That holds back a lot of productivity use cases.
In defense of complex permissions, this often ends up being necessary to avoid single points of failure. For example, if someone can turn off the setting preventing force push to the master/main branch, that person should not be able to commit code thereby requiring more than one person for a commit to be force pushed in practice. Even better would be to require a config change like that to be approved by more than one person, but that can be difficult to implement compared to adding in narrow permissions. Even if you just prevent force pushing in general, another common bypass would be disabling CI for certain commits (such as in cases where the CI infrastructure is down and the commit is necessary to fix some ongoing incident). Yes trusting developers is always going to be necessary to some degree, but that doesn't mean absolute trust is required all the time.

For your specific example of not being able to see tickets as admin, I imagine that feature was added for teams where sensitive information is stored in the ticketing system for things like user reported issues. User reported issues often has PII or other personal data and while developers need to see that information, admins often don't. When I worked at a bank, any remotely sensitive columns in the database were either inaccessible to developers by configuration or by encrypting them to and from client code when the DB didn't support column level permissions (while Sybase could manage column level permissions, Mongo and Elasticsearch didn't at the time).
I can't take credit for this, but I also don't recall where I heard/read it from:

"Most teams would be better off using a shared spreadsheet for task management than they would using Jira"

Rings true to me to this day.
Nowadays the need for Facebook arises after you finish school and want to reconnect with lost friends
"My opinion is that Jira reflects the organisation that manages it."

Came here to say EXACTLY this. I've used Jira across 3 companies, and in the first 2, I always felt like folks complaining about Jira were just being picky developers wanting the sun, moon and the stars, because Jira worked perfectly fine for me and my team (in fact, it was the backbone of our process).

Then in the third org, I felt like I was hit with a brick wall of every single issue folks complaining about jira point out. Needless workflows, Middle Managers wanting to "control" how stories/epics get closed, multiple levels of convoluted manual configurations, automated processes creating Jiras that for trivial non-issues which clogged notifications and team backlogs and brought jira to a crawl etc. Heck, at one point, the mess got so bad, that the company considered hiring a third party to "fix" our Jira workflows. And note that this was a <100 person startup!

On introspecting, I completely felt that in the first 2 companies, the organization was structured around "getting stuff done" and "keeping stuff as simple as possible, but no simpler" and that naturally flowed into how Jira was set up as well, while in the latter, the focus was entirely on top-down "process", and that showed in the Jira setup as well.

Honestly, I now think I can say a lot about a company's engineering/product culture just by spending 15 minutes on their Jira ;-)
If you happen to speak German, Stiftung Warentest is great and reviews a wide range of stuff.

https://en.wikipedia.org/wiki/Stiftung_Warentest
Can I please just have a 3d window manager?
No, not mapping my 2d desktop onto a single surface in 3d.

A true 3d native window manager. where I can arrange each individual window anywhere in the 360 degree space?

Until that is solid, VR is not the productivity tool I was hoping it can be.

Just like Mobile(ios, android), Microsoft could not possibly drop the ball any harder here.
part of the hatred has to come from the fact that it's a tool used for hidden micromanagement. Whenever I experienced Jira being introduced into the workflow, human connection vanished, work became laboring and many times the better devs left the team due to lack of autonomy. Who remained were the people who didn't mind to just work and never question, like factory workers of the 1900's.

I don't mind using Jira as a verbose platform which aims to map project state and helps communication BETWEEN all participants, but this is rarely the case, especially with all those pseudo-agile practices that are part of mainstream software development.

Another part of the hatred may come from the fact that it's an overcomplicated tool for a moderately simple task. This complexity is standing in the way most of the time. I just want a simple board for a simple project with simple issues/user stories/whatevers and update their state which gets reflected on the board. For additional features i want to install/write a plugin and that's it. If I need a manual for software in 2022 it's either trash or something far from mainstream (in which case complexity and/or lack of ux might be acceptable).
For Meta, or in general? For Meta, there are plenty of teams that require some infra knowledge around these common concepts. It's been fairly straightforward to find a team as a front-end engineer that allows you to excel in these areas at Meta (once you're successful in the interview loops).
Air travel itself is essential, it's one of the defining abilities of the modern world and can't just be shut off. It would be corrosive to try and separate the essential from the frivolous, I agree with that.

I favor carbon taxes that dig an industries grave for it: such as taxing coal to build nuclear, wind, solar. That's not feasible with air travel yet, which leaves a consumption tax, those are regressive.
> It's incredible that these shitty ML hueristic systems are the best these "genius" FAANG developers, who get paid $150-300k a year, can come up with up.

I think it gets personalized / fingerprinted fairly quickly TBH. For example, I have 2 identical (Linux + Firefox + uBlock Origin) VMs that I use over the same VPN connection. One of them gets almost no captcha challenges and the other gets them continuously. My subjective experience is that it's based on what you're searching for on Google or maybe due to hitting sites that Google might have flagged as malicious (guilt by association). It's tough to tell, but it sure feels like there's some type of cumulative score based on activity.
Steps 1-4 plus probation period is sufficient. The rest is bs.
It’s absolutely not pointless. We learned, but learning is not a destination, it’s a journey that sometimes has backtracks and delays.

The fact that you think it’s pointless shows that you yourself have some learning to do.
I don't respect any HR Team/Company that demands tests, assessments or homework as part of the interview/onboarding process. If you don't have a competent enough team, that can identify I know what you need me to know just by talking to me, I don't respect your company philosophy, I will assume your team is incompetent or not fully formed, and I will choose not to work for you. Its a cheap cop-out for HR to not have to do their job and not have to involve working members of the team in the hiring process. If you need to "Test" me to hire me, I find it disrespectful. It means you already don't trust me, so I will never trust you.

Also there's lots of incredible talent out there, who are horrible test takers or do poorly under the context of the stress of performing for an interview... these people actually tend to be more talented than the people that are good test takers and good under that kind of pressure. You're shooting yourself in the foot by not considering them.

Hiring "the best candidate for the job" is a nebulous term that HR has misinterpreted to mean "most technically skilled during an unrealistic interview test". The best candidate is really the person who interfaces with a team the best on an interpersonal level, and they will grow in to their position over time, and fill in any gaps in technical experience they don't have if they are truly passionate about their field. Either a lead person has leadership traits or they don't. Some technical homework assignment and presentation will prove nothing.
>... but I think beyond that, deep down, he's just a nerd who wants to live in a VR dreamland to shut out the millions of people who call him a weird lizard.

I mean, in his defense he might be pretty normal by lizard standards, I don't know. Calling him weird just seems unnecessary in that context.

>He of course wants every human interaction to be monetizable by Facebook, total control of our dopamine channels, ...

I agree. It'd be a much better future for everyone if he'd just throw his advertising biz in the garbage. Apple is going to kick Meta's ass in the long run just by virtue of their privacy stance—which isn't all that great to begin with, but it sure does beat "our intent is to sell every iota of information we collect on you."
The worst thing about jira is it leaves the door open for confluence which is the actual worst thing.
re PIA, have you seen this? https://restoreprivacy.com/kape-technologies-owns-expressvpn...
Maybe it’s the soon after part but Apple has been doing it since 2003: https://support.apple.com/en-us/HT201222
Here's a better answer to that question:

Crowns don't come from inherent value. They come from monarchy.

Jira holds the crown because so many are convinced the "industry" in which it leads is worthy or valuable.

What value does a monarch provide? Order. Structure. Authority. Corporate environments value these because - art its core - that is what "Corporation" is: a new system of governance.

Most of the complaints about Jira can be turned to Corporatism itself.
Even if your site is set up well to support it there is objectively less data you get back. Like it's hard to figure out where are the trigger points that increase or decrease conversion all that stuff. Or if people leave and come back. And it's a lot harder to run your own analytics (coming from somebody who does) even if you are just hosting somebody else's solution.
I personally advocate things like urban density, mixed use zoning, walkable cities, human sized homes, urban forestry, but I don't think LVT's are the right tool. I live in a city with "market value assessment" for property taxes, and it profoundly lacks transparency, and is a very dodgy regime altogether. The main thing a LVT creates is constant churn as (retired) people cease to be able to afford to live in their homes, incentivizes being a landlord, and punishes family wealth creation via home ownership (which is a barrier to class mobility), as if you own property, you now need to generate revenue from the land to pay the taxes on it. The LVT isn't for services either, it's punitive by definition.

Sure, it would get rid of some vacant buildings, and we do need a way to discourage land and property banking that turns hot money into high prices for home buyers, but taxes are what you impose when you have a policy that nobody would win re-election on voting for. It's literally what nobody wants. Nudging taxes are inferior back door policymaking by regulators (in their own interest) who can't get the political traction for an actual policy. Who is nimby'ism a problem for? Arguably, people who want to impose unwanted experimental policy, and in-effect loot the wealth that cohesive local communities and their cultures invested in and built. Nimby'ism as concept is a slur that makes a villain of anyone with a home and investment in their local community, and who may be skeptical of centralized policymaking. I'd question the underlying values behind advocating an LVT, as they tend to be within a degree of some other very technocratic impositions that mainly benefit their administrators.
If self hosted is your thing I like taiga for kanban integrated with gogs for the issue tracking/VCS integration side of things. Didn't take me more than a day to get working and everyone signed up on it, isn't a lot of maintenance, just works, costs nothing.
This is quite interesting actually, because this sort of directly lays out "Here are 3 difficult technical problems we need to solve for a VR headset" - Resoution, Focal depth, high dynamic range.

I'm not an expert in the area, but resolution and HDR seem like basically solved problems - in that they're just logical progressions of where we are today. The focal depth one I didn't understand. He says normal monitors are a fixed distance, whereas in VR and AR you need to focus on different distances. But these VR headsets are just a fixed distance away, so how is that really a problem?

Fundamentally these problems are clearly necessary buticie not sufficient for VR.
I did not know that! Thanks a lot. I'll definitely give it another try.