skysight-inc/HackerNews huggingface dataset:
A very good lesson I learned from a previous company (medium size, 1-2K employees) where a C-Level exec was hired in and needed to make some large scale changes in the company with speed:

1. You can't "fake it" at this level. One of the most impressive things IMO about this exec was his ability to know, at a fairly low level, what every department and org in the company was doing, and to diagnose their strengths and weaknesses very quickly. We'd have quarterly day-long meetings where every department would present, and his ability to quickly hone in on critical low-level details was extremely impressive. I think he would have failed if he had just thought that his job was to "brush with broad strokes". (Aside, this did NOT mean he was a micromanager, it just meant that he had a very good understanding of the details across many departments).

2. It's important to put some structures in place where departments are forced to show some accountability for speed. For example, one metric that I actually hated at the time, but later learned to appreciate the purpose, was that individual departments were judged on the number of A/B tests they ran per month. I hated this metric at the time because I felt it was easily "gamed" - departments would run small little A/B tests like button color changes. However, after a while there were a couple of big cultural changes that had taken place: (1) the company built tools and processes that made it easier to deploy and run tests in the first place (better CI/CD pipelines, better analysis tools, etc.) which had the overall effect of letting us ship faster with higher quality, (2) while yes, there was a lot of "gaming" of count of A/B tests run in the beginning, it didn't take that long for teams to actually run out of tests to game, and people actually put in the hard work of thinking about better tests to run, and (3) it changed our culture to become much more data-driven - it wasn't perfect, and "data driven" can be a double-edged sword, but it was an improvement.
People say this and I have yet to find a company that doesn't do some kind of technical assessment. But I have seen multiple coworkers with 10-20 years of experience as software engineers with glowing recommendations get fired because they couldn't write software. So I'm a little happier to have some bar for myself and coworkers to clear.

> I'm never, ever doing a 4 hour assignment for you.

Boo hoo, you need to spend four hours of your life to take home multiples of the median American family's income. It blows my mind how conceited some people in this industry can be, and I'm glad I don't work with them. This is one reason why the take home is a great filter.
PivotalTracker, GitLab has pretty great project tracking and ticket management if you’re on them. These are the two I can think of off the top of my head. Personally I really like Pivotal.
Except for when you want to do diffs at the end of a sentence.
Netboot.xyz: your favorite operating systems in one place
The Inventor of iPhone’s Autocorrect Explains How It Works - WSJ [7m50s]

https://www.youtube.com/watch?v=Ncj3QAKvBBo
> As far as packet loss is concerned, TCP is more robust

Somehow I always felt using UDP as a basis for a file access protocol had more potential. You shouldn't care about packets arriving in the correct order, only that the (likely, concurrent) read/write operations are completed. If I request a 1MB read, I don't need it to come in 1500b sequential chunks, I can wait for the read call to return me a full 1MB buffer.

It could also enable better throughput on high-latency (but otherwise speedy) links, like moving files between datacenters across the pond.
Yes, not everyone can notice the important element of what they're witnessing, especially not a novice.

I've seen a lot of baseball and golf, and I still don't know how to even try to swing those things properly.
I don't think this adds any value to the interpretation of the parent's comment and seems overly pedantic. What does your hair-splitting provide when the central thesis of the parent is arguing that land value tax is a tax on productivity when you've even conceded the rebuttal?
For a fileshare? What exactly is the challenge here? Bandwidth might be, but most colleges probably have a pretty solid fiber connection.
Everything turning into an edit action when I just want to click a link or copy a bit of text is super annoying! Also is thinking you're in a text field, typing out something and realizing you've done a whole bunch of random actions because of all the hotkeys.
A completely rational guideline. My mistake, apologies.
I like shortcut and use it whenever I have a say in the matter.

https://shortcut.com/
I believe you.
Medium is the message is a term from media theory.
It refers to the idea that messages aren't in a vacuum, but are shaped by where they are transmitted.
Often that shape is a function of what the audience will find appealing.
You can tie this sort of thing to bellman equations to get a mathematical grip on the effect.

It does exist.
It can be as harmful as you think it is.
Yet it isn't harmful everywhere - isn't the world at large without any variation.
It is intimately tied to the environment you are in, because that environment produces the rewards.
Different environment, different reward, different impact on your writing.
The effect is local, not global.

Which means you get to have a superpower.

When you have a bad transformation that degrades thinking that makes the term "medium is the message" feel dangerous.
So you get things like Neil Postman's Amusing Ourselves to Death.
I think your post is an example of the same type of fear.
This focus - on the examples of times where things are negative - it misses the opportunity.
Since messages are a function not of raw ideas, but of their audiences you have an incredible power.
Choose the right audience.
Set the expectation for evaluation in advance.
Pick the medium that helps you to think clearly and makes it easy to be judged.
Now, instead of being destroyed by your incentive environment, you get empowered by it.

Take a look at Amazon's writing culture for an example of that.
Or more broadly, the many companies which chose to ban powerpoint for reasons which are fundamentally related to what I'm talking about.
We're not worse at understanding writing than ever before.
We're more advanced than ever before, because we stand atop the giants that came before us.
Yet at the same time - we're not, because that too is local and not global.
The future is often already here, but isn't evenly distributed.
G'MAMA
Yeah, you're right. Just saw on Youtube that a Biden aid, Brian Deese, said they are not blocking expanded oil and gas production but killed refinery expansion, preventing 1M+ acres of oil/gas leasing. Per him, "I guarantee you, we're going to end fossil fuel & I am not going to cooperate them". It looks they are taking a long term view, and I hope the execution will be smooth: we can manage short-term increased cost while figuring out a way to keep the planet for our children".
Older programmers are mostly white males.

Lots of people don't like to hire those anymore.

I hired in at one place, was informed afterwards that it was only because they were so desperate that they hired me despite my demographics.
Was reminded repeatedly on my sins of being a white male.
Let employees vote to fire their managers, possibly up to the c-suite (though there may be contention with the board having this control). Keeps management aligned to the employees interests.
Ripe for disruption.
> Apple dictates the browser engine for security and battery life considerations which I regard as a feature.

> Anything else can be viewed on the web.

You've reconstructed your statement to be conditional on your preferences.

It's now "You can... Except for the major situations when you can't... But I don't count those because of my personal preferences."
I think he is entertaining, but I don't find his reviews critical enough. He typically reads off a spec sheet and shares subjective opinions of just a few days of use. I need deeper, more critical reviews
>Private from your current ISP, sure, but not from Mullvad

being private from your local ISP is what 99% of people care about because they use VPNs to send copyright infringement claims to /dev/null and watch netflix, not to smuggle nuclear secrets to Iran. It's privacy in a practical sense that's useful to people. If I go from an untrustworthy ISP to a trustworthy one I've gained privacy, there's no need to be overly academic about the term.
> Many seniors (actual seniors, not 3-years-of-experience seniors) have a network and can say "hey I'm looking" and instantly have multiple options that won't have them do more than talk to the team and manager for an hour or two. If that.

Just wanted to back this up a little bit. This is exactly what happened to me on my last job search. I'm currently in between jobs, starting the new gig after the 4th of July holiday. The company that I went with: I had a 30 minute call with an engineering VP and the hiring manager that was followed by an hour long panel with a few members of the team that I'm joining. I also learned after I had accepted the offer that the person who referred me internally spent about 45 minutes chatting with the same engineering VP about me specifically before they reached out. This was for a staff/lead position and I've got over 15 years in the industry.

I specifically sought out referrals from former colleagues and friends where the interview process put a lot of emphasis and weight on the internal referral and it worked out really well for me. I really hope that this is a sign of things to come, not just for myself and my future employment but for others, at least at the ("actual") senior level.

edit/ Added some more context...
What does age have to do with anything here, other than older folks probably needing to pack a prescription med or two?
Thanks for putting the salary range in the webdev role! (I asked you to do so on Twitter :) ).

My question for you: do you think there are any other big, generic points of segmentation for SaaS consumers like SSO is? A few jump to mind:

* uptime SLAs (you mentioned this)

* data export/retention

* ???

I'm on record as saying that I think SSO will migrate down the value chain just like HTTPS did: https://twitter.com/mooreds/status/1481300034448760842 but am curious what will replace it.
I find it funny that you said "learn AWS properly" — have you loaded AWS services page recently? I've seen even very experienced DevOps engineers struggle to remember what was the service name to get into "parameter value store" (and I already forgot, and that was two weeks ago).

AWS is a mess. You learn just enough to get by and long for the days of simplicity where you could manage a bunch of servers yourself.

Oh, sorry, we are using Azure or GPC or OpenStack, that's an entirely new set of names for you to even know what you are looking for.

K8S is just the same. Every company decides on an "easier to use tool" like k9s that you have to learn from scratch if you don't want to jump through hoops to just use kubectl directly.

If anything is a definition of boring work, it's this: work to assemble a bunch of existing pieces without creating anything really new. I like being tasked with creating things, not being an assembly line worker who's got to learn terminology de jour.
In addition to what others have said, I personally would love to see people using the format, so please go ahead!

I'd be interested to see what you're working on!
Okay? I never said it was legal.
If a tool needs this level of support it's not a good tool and not even a tool - it's the no-code equivalent of a framework.

I'd rather pick any other ticketing system which has things done in one way than waste my life configuring jira
This is actually the standard principle in german dental practices. Every practice i visited for the last 15 years recommended to remove all wisdom teeth asap because they will soon develop a cavity. Nothing happened in all those 15 years. I only get angry every time i visit a dentist and hear the same bullshit again and again.
I've seen absolutely ridiculous workflows on Jira. Things like - "i'm gonna make the most ridiculous workflow out of spite and boredom just to troll you."

From that perspective it's easy to hate it, but you hate the actual use of the tool not the tool itself.

Currently i enjoy more sane use of it. Simple workflow. You get in, read the ticket, clicky a button, get out. Slowness in that regard is very tolerable.
If it's set up properly, it's easy for developers to browse the tickets, log work on them, and update their status - and that's all they will need to do. So, from their perspective, it's fine. However, getting to that point is unnecessarily difficult, and if you fail, that difficulty spills over into the developer experience.
>Who pays $260 per filling? That is a crazy price. $1,040 for an hours work?

The rate may be a tad high, but I don't think a dentist is cranking out 4 fillings in an hour.

Here in Canada we have a semi-regulated system, and $200-$300 CAD per filling looks pretty normal at my insurance provider.
I've worked for university sized companies. I'm not sure why setting up a fileshare would be difficult. What's to sign off on? Space and a couple VMs? Red tape aside, I don't see the challenge.
I'll toss in a mention of yggdrasil [0], which would put every computer on the network at a unique address.

[0] https://yggdrasil-network.github.io/
> - Take-home technical assignment (~4h) or similar at candidate's choosing

That's probably your problem. You've gotta respect people's time. It'd be ok if that were the final step in the process, but it looks like it's followed by Yet Another Interview Round (TM).
Try to slim that down, or remove the "presentation" aspect, and have it be the team's burden to audit the assignment. Ask for a small writeup explaining their technical decisions from the candidate instead.
Not quite true; sometimes, if an infection develops (even without a cavity, just because food got caught in the gums) it can be significantly more painful to deal with than getting it taken care of when they're healthy.
Single letter hotkeys are pretty bad. If it's not an input field you've focused but the page itself, you might assign the ticket to yourself and set it to some crazy state before you realize the focus is all wrong. Ask me how I know...
> They're on the market 2 weeks, tops.

My last search lasted 9 days from when I put out the signal to having interviewed (for 3 companies) and negotiated an offer and submitted my resignation and 2 weeks notice.
Linear.app
I tend to use reviews as a "try this door" kind of thing, and do my own research. Probably the most awesome review site that I used to rely on was DPReview[0]. I haven't really looked at that site, in the last five years, but they used to be absolutely top-shelf, and full of geek value.

I tend to be heavily Apple-biased, myself (I write native Swift software for Apple devices). Other sites tend to be heavily biased towards Intel/AMD (usually gaming review sites).

[0] https://dpreview.com
This pretty much only works in the US. In the rest of the world companies expect to get a fair price. Hence the term, American prizes.
It sounded like unionisation was an attempt at pushing back the ills of VC funding, especially taking back some control of the company’s direction, rather than concentrating on fairer pay and working conditions. I support unions but I’m not sure I support them controlling the direction of the company: most of the time the business people, frankly, know best about profitability.

The whole story reinforced the idea that if you build a company with value but no profits eventually you either abandon it as a business or give control to VCs, and if you had any emotional or political investment in the company you will be disappointed.
So much this. Find someone who does a lot of residential repairs of X. Ask a few of them for recommendations, specifically on what not to buy.

As the Farmer's Insurance jingle goes, "They know a thing, because they've seen a thing."

Every service tech I've ever asked has immediately had a "Never buy {popular brand}, because they all {have shoddy part | catastrophic design error}."

And it's night and day between what service techs all know vs what even the most detailed internet sleuthing would give you, because they actually see a representative sample size.
Depending on what you use it for, Gitlab springs to mind
https://toolguyd.com/top-tool-deals-11122020/ has some comments on what the site owner can see, things like which links work better than others, etc. Surprisingly large amounts of info could leak without anyone really realizing it, even if everything is entirely "anonymized" there's still the total dollar amount paid out, etc.
You're not responding in good faith with your "boo hoo" comment. No one is crying here. The point here is there are many, many companies that don't require a 4 hour take home technical assessment, and thus people can decide to do them or not.

The post is about this topic, so the responses are about the topic. You think that 4 hour take home technical assessments are a reasonable filter. Awesome, you are a person who can apply for the position op is focused on.
> Then the interviews were basically friendly meet&greets but super informal, not a single coding test or take home assignment

I have 20 years experience and this is completely alien to my experience. I've gotten lots of job referrals over the years, but all it did was get my foot in the door. From there, it was the standard interview process with whiteboarding and take home tests. What am I missing here?
I bought the costco black backpack with swiss logo, like 15 years ago. It was under $40, and probably some of the best money I spent. Took it on numerous trips, hiking, got it wet and filled it to the brim with stuff. It still functions perfectly. No rips or tears. The zippers have a haze on them now, but considering the years of use it's kind of great. It has a laptop compartment. They still sell it. So might be a great option for someone.
Struts was an industrial standard for longer than most things, and everyone hated using it for most of that time.

A quarter pounder with cheese is an industry standard too, but that doesn’t mean you should give it preferential treatment. Industry standards are often more like consolation prizes than a special experience.
I came from Apple (and their excellent Radar issue tracking tool) to a company that uses Jira.

Jira is the worst. I routinely lose data in jira, like saving errors. Dragging and dropping attachments sometimes causes the page to crash and reload. Everything in the UI moves around or obscured behind some tabs. I want to be able to file a network of issues all at once, something Radar did great. Jira workflows are much to complicated, and their flexibility just increases your administrative hell. I can go on and on.
School’s Out for Summer and Many Teachers Are Calling It Quits
According to Merriam-Webster, "customer" is defined as "one that purchases a commodity or service" so it isn't really a trope.
Yeah at startups we called those people "pushons". Basically, the CTO would say hey, "this is eric, s/he starts tomorrow". Mercenaries. Pros. No interviews, no questions, no linked ins. Usually "pushons" turn into top performers. With a 6 month runway and cash being burned - we didn't have much time for fizzbuzz.
The hate is not for JIRA the tool, but JIRA the way of managing things.
>But the dress shirts I only dry clean

Yeah, I bought one and it didn't really hold up very well. Having to dry clean sort of defeats the purpose of having a travel shirt.

In general, I really like merino wool but it's expensive and fairly fragile even if I avoid putting it in a dryer.
> Anything else: if you don't have a site you trust, then the only recourse is to look at LOTS of sites and read between the lines. By "sites" I also include "user forums."

That's why Wirecutter is useful: convenience. They might not have the best product recommendations, but for items they "review", they provide an easy to click button to buy the product.

No offense, but reading random review sites, reddit, yelp, forums, misc google SEO landing pages with affiliate links, etc to try to find the best product is a huge pain. If I can go to 1 review site that is good enough and just buy the thing, the convenience often wins out.
Could you start small? Just a minor LVT to begin with, which could potentially be raised over time. Possibly implemented by a single city instead of nationwide.
Just about every enterprise tool requires a proper implementation and system admins and business process analysis and change management to get setup.

A lot of enterprise tools are "crap, why would the company ever use this", and 90% of that is in the implementation (or lack thereof)
Just speculating, but if you create a new account and then spam some positive reviews people will notice and downvote / get you banned from the sub-reddit. If you have some built up history it looks more legit to the other community members.
This shouldn’t have been necessary, but it at least represents a little progress back to sanity in this area. Without a ruling like this, eventually there would be no more Olympic medals going to women swimmers. Let’s hope the other sporting bodies follow suit.
In theory, yes, and ideally any of this would be implemented as a standard, for instance as a segment of a TLS ClientHello added by a forwarding proxy (such as Private Relay) that includes a UUID connection identifier, a risk category for the user, the identity of the proxy, and the proxy's signature for the whole of the ClientHello packet.

There would then also be presumably a way to interrogate a proxy for reporting back bad actions of a user by a service provider, with those attestations also signed by the service provider. (FLAGGED_AS_BOT, CHILD_PORN_TAKEDOWN, FINANCIAL_FRAUD, SPAMMING, OTHER_TOS_VIOLATION, etc) The service provider would pass in the UUID connection identifier which the proxy could then map back to the known user, weighted by the degree to which the proxy trusts the service provider's reports.
I would fight you about how Bamboo is the worst tool I’ve had to use, but since they’re both from Atlassian that feels a bit like splitting hairs.
Yeah, this is basically The Frogs in the Walls.
This guy is responsible for a relatively significant proportion of the entire planets carbon footprint!

His air travel is the least of our worries.

https://digiconomist.net/ethereum-energy-consumption
I'm curious what other people's thoughts are when comparing CA Agile Central (formerly known as Rally) to Jira. Which do you like more and why?
- For a while, we had tickets in done states that just roll over to the next epic, like they were still open. Nobody knew why, and it went away with nobody making any fixes to anything.

- For a while, the side pane when you open an issue would just be blank.

- Setting a ticket's epic makes me want to tear my eyeballs out. The button has the tiniest hitbox, the suggestion list is always wrong.

- Bulk operations are just a PITA

- the search box is always description. I'm almost always filtering on other criteria, and so, have to suffer a page load.

- and every page load is long and slow. Loading my backlog page is 186 requests, 4.4 MiB on the wire, and takes 9.4s. For one page.

- UIs that have drag & drop, but don't support simultaneous scroll are annoying. I have to wait for the view to move at JIRA's speed, which is ofc., slow.

- it encourages "sprints" and "agile", which in turn encourage "process" over just getting shit done.
Other than in your body where do you suppose you exist?
It's a tool for the boring part of software engineering- I don't expect it to spark joy. I wish it were faster, scaled the full width of my monitor, allowed external editors, etc. Overall it gets the job done well. Everything else that I've used is horrible which makes it the best in my experience but that's still not saying much.
Yep. Jira is far from perfect, but I've not had any better luck with anything else.