skysight-inc/HackerNews huggingface dataset:
This feedback does not sound particularly constructive.

If they wanted something done faster or better: Well isn't that special? Look at the special boy who wants work to magically go faster with 0 additional work coming from higher ups or senior engineers. That's really nice, but that isn't how things work in the real world. Stuff takes as long as it takes.

If you aren't having regular, as in daily, meetings with your team to make sure you are working on the right things: That is literally your manager's only job. Do not let them brush you off.

Meetings are for YOU to make sure YOU are doing the correct work. It isn't you turning in your homework, it isn't an accountability check-in where you get a letter grade and a lecture. It is the time you communicate about progress and goals. They are YOUR meetings, to help YOU, NOT theirs!

Helping you with these meetings and other forms of communications IS YOUR MANAGERS JOB.

And if your team isn't considering changing requirements when planning work, then that isn't on you either. Requirements changes should go through your project manager and it should affect project scope.

However, at a certain point, you have to manage UP to get what you need from your team. Set a cadence of accountability with your manager and team. If they don't make that reasonable accommodation, at least you can say you tried.

===

As an aside:

Here is a fact you probably have not had to deal with too much yet: Some people are cruel assholes, and they don't even know why. They just say and do cruel things because that is who they are. Don't deal with assholes.

The other thing about assholes: They manipulate you. They make YOU feel bad for THEM. They make YOU feel like YOU are doing a bad job instead of taking on the responsibility themselves.

If I had a Jr engineer who was struggling, I would tell them and I would help them. If I had a Jr engineer who I forgot to manage and then they failed to meet expectations... well, i wouldn't behave like your boss. But shifting that blame downwards is a tactic you could use.

We have too much mobility in this industry to deal with assholes. If you are writing and shipping computer vision projects, cash the checks, keep your head down, get the experience you need, and once you are done with this place: Leave without looking back. You don't owe them anything.
The sole caveat to this is the Milwaukee Protocol, which leaves most patients dead anyway, and the survivors mentally disabled, and is seldom done - see below

I was curious, and thought that would be something gruesome involving power tools, so I looked it up and it's apparently an induced coma with heavy doses of antiviral drugs, which has a very low success rate.
The notion that one has to take care of one's "needs" before pursuing anything "higher" is a lie and an excuse. The number of great intellectuals and writers who lived at least a portion of their lives - and often more - in absolute penury is testament to this. Einstein for example nearly died of starvation, yet he kept working.

One could make an argument that it is because of real world difficulties that one is able to do great work. What did Jesus say about the rich man and the kingdom of heaven? The times in my life when I've lived on the edges are the ones that have laid the groundwork for everything worthwhile I've done in my life. Success and comfort too often bring stupor and cowardice, and not worthy ambition.
Not starting a holy war (and endless discussions about the nature of pizza and whether the Truth is in Rome, Naples, or New York), but it is quite common to put some oil in the dough. It makes it easier to work with, more homogeneous, lighter (but thicker), and it cooks a bit different.
Are there species of bats this [0] doesn't apply to?

If not, it's an irrelevant level of detail for this context.

[0] https://get21stnight.com/2020/03/30/why-do-we-keep-getting-d...
Though this is one reason why we can do better than RSS: the implementer (or HN commenter) isn’t the one that should get to decide what I primarily or secondarily use my “feed reader” for.
In this case, my local post-RSS feed reader is absolutely a way for me to store content for consumption on my own time, not just a notification service.

You’re right about RSS. I just see a better solution for this idea of a content-delivery system being one implemented as a smart client that can handle all websites rather than a dumb client that hopes every website in 2022 implements RSS. That way there’s no “you’re just using it wrong.” ;)
Indeed, the rampant consumerism of our current day is powered by government, not capitalism. The US government actively promotes consumption through tax policy, monetary polity, and spending policy.
When I was a kid, I was pretty sure that rabies, quicksand and poisonous snakes were the big things to look out for.
I wonder if ROATE is even in the list of words. I'd never heard it and I'd like to think I have a decent vocabulary.

The article says they whittled it down from 12,000 words to around 2,500 words, aiming for words that most(?) people would be familiar with.
If it provides no more advantage than an existing non-standard controller, than this news piece is a complete non-story. Or at least, that bit of the piece is a non-story.
I wish folks were intelligent enough to graduate from "LOL microchips?? Idiot" to actually acknowledging mRNA technologies, the fact that ipv6 adresses can be printed on blood platelettes, and the reality of innovations in microrobotics and nanoparticle fluid tagging.

As long as people like the author have their head in the sand about some stuff they dont like thinking about , actual scientific papers will continue to fuel conspiracy theories...

EG- nano bots in blood used as cameras
https://www.nature.com/articles/srep09744#Sec9

Not sure why they put "geoengineering" in quotes either. Author should peruse the IEEE chapter for it.
https://spectrum.ieee.org/tag/geoengineering
When that technology becomes a non-trivial part of the global CO2 emission without bringing any value for anyone except select few "investors", it becomes an issue.

Completely shutting down all cryptos would have the following effects:

- Immediately reducing electricity consumption worldwide

- Making money transfer for illegal activities (drug, human trafficking, prostitution, gambling, ...) harder

- Making money laundering of said activities harder

- Reducing the electronic chip shortage

- Forcing a bunch of young, adventurous, often quite clever people to find another source of revenues. Hopefully by providing some tangible value to society

It sound like a good plan. The only real I see are for people using cryptos in authoritative regimes, so overall a net benefit for the world.
> though not unusually notable as an assistant professor at a mainstream state school.

We really, really need to get away from this academic obsession with prestige. If she does solid analysis and communicates it effectively, with a record that looks increasingly good as time passes, she's already ahead of the curve. Meanwhile many other highly-credentialed, prestigious experts have been wrong over and over and over again in this pandemic.

Academic/scientific institutions are polluted by the credentialisim/prestige focus. It's the ugliest aspect of the whole space.
> Data now suggest that many changes to school routines are of questionable value in controlling the virus’s spread. Some researchers are skeptical that school closures reduce Covid cases in most instances.

https://www.nytimes.com/2022/01/04/briefing/american-childre...
Titles are incredibly malleable and don't always line up to comp. And situations are almost always complicated by external factors. Not all employers are enormous Microsofts/Googles either, where there's a line out the door of candidates.

E.g. Imagine you have a software business with < 20 total staff. What would you do in this situation:

Candidate is interviewed and we think they would be a good fit for the role, say it's a mid level role. We're desperate to fill it as we have xyz project to complete. The candidate has an offer somewhere else that is 15k higher than the usual mid-level title compensation. They say "I'd love to work with you, but money is important to me right now as I'm saving to buy a house".

Do you...

1. Offer the standard, lower mid-level amount, lose them to the other offer and allow the business to suffer a larger impact.

OR

2. Match the other offer and undermine your "standard compensation based on titles" rule.

Either option is problematic and compounded by pay band/published salaries rules.

If you overpay them and then can't give them a raise for a while because they were hired above their pay band, then they will be annoyed/offended and may leave. "Sorry we overpaid you when you were hired so no raises for a while until you can progress to the next title"

If you overpay them and everyone's salaries are published internally, then their peers will be annoyed and demand the same salary, which your business can't afford.

If you don't hire them you are letting a hiring rule affect your broader business strategy and risk missing out on opportunities that would benefit the whole team.

This has been my experience. Yes this is quite one dimensional, and money isn't always the driver. But sometimes it is, and I think "standard compensation based on titles" is a one dimensional solution.

Open to ideas
There is some strange allure for spending time crafting Dockerfiles. IMO it's over glorified - for most situations the juice is not worth the squeeze.

As a process for getting stuff done, a standard buildpack will get you a better result than a manual Dockerfile for all but the most extreme end of advanced users. Even for those users, they are typically advanced in a single domain (e.g. image layering, but not security). While buildpacks are not available for all use cases, when available I can't see a reason to use a manual Dockerfile for prod packaging

For our team of 20+ people, we actively discourage Dockerfiles for production usage. There are just too many things to be an expert on; packers get us a pretty decent (not perfect) result. Once we add the packer to the build toolchain it becomes a single command to get an image that has most security considerations factored in, layer and cache optimization done far better than a human, etc. No need for 20+ people to be trained to be a packaging expert, no need to hire additional build engineers that become a global bottleneck, etc. I also love that our ops team could, if they needed, write their own buildpack to participate in the packaging process and we could slot it in without a huge amount of pain
> Both sides now work hard to silence opposing or even moderate viewpoints.

Who has the Right deplatformed?
It's not our responsibility, and it's not the responsibility of the previous generations. If it's anyone's responsibility, it's the responsibility of the government officials who looted the country, socked away their modest winnings in banks in Uruguay, and left us to pay the bill, and of the creditors who lent them the money, knowing that was what they were doing. This collective punishment bullshit is a "let's you and him fight" swindle.
The easiest way to experience this is to remove 3 key caps from your keyboard eg. from T K and C. It will destroy your flow.
It's your first job out of college. To be honest you aren't a good developer yet. That might sound harsh but it's actually totally okay. I don't care how great your grades in college were, new grads don't understand how to build maintainable enterprise projects. They don't have ample experience to draw on when it comes to how best to solve a problem, because most of it time it's the first they've seen of that problem. Thrashing and failing is just part of the career. Having a nice long think over a post mortem is how you learn and grow. What really matters is whether you have a good attitude, if you can reflect and build on your mistakes, if you're pleasant to work with, and if you can gracefully give and receive feedback. You're not a great dev yet... and that's fine, because you're working on it.

The problem seems to be with your boss's expectations. So if I understand this right they gave a junior developer soul dominion over a CV project with evolving requirements and a tight deadline? That your manager isn't really reviewing your code and offering feedback on a daily basis? That you don't have a dedicated mentor? Of course you're thrashing. To give you a project and expect otherwise is stupid.

Look, I'm a firm believer in giving good people the support and tools they need to succeed, because I've never really seen it fail. People who want to do good will. I've mentored lots of junior devs and they all have their own strengths and weaknesses. The one weakness I can't abide is if they're too full of themselves to accept feedback or hard to work with. If that's not you then you'll keep getting better. Look, you might think you like that job and maybe today was an exception, but you don't really have a basis of comparison and what you described sounds kinda wack. I can tell you with 100% certainty if your colleagues don't have realistic expectations you're going to have a bad time. The blame fest is coming. There are a ton of chill teams out there that would appreciate your time. Might not be as flashy as CV, but at the end of the day building Rube Goldberg machine business software is pretty dang similar. What matters is if you enjoy coming to work.
I hear the phrase "high-functioning" more than "aspies". I think the distinction is useful in social contexts: just knowing Bob's son has autism is not enough info when writing party invitations or considering transferring Bob overseas.
You need to develop a personality and lifestyle that includes interests in something else. Art, sports, music, theater, gaming, martial arts, auto racing, millions of different "outdoors" activities, stamp collecting, volunteering, sewing, trivia, building furniture, rock climbing, travel, dancing, bird watching, gardening, cooking, philosophy, history, economics.

It's a very big world out there. Get out there, look for what draws your interest, then do that thing with other people that like to do that thing. That will probably lead to new friends, unless your drinking friends have the same non-drinking interests that you develop.

I also highly recommend some therapy. Find out why you were drinking instead of doing all those other fun things.

Oh, and if you continue to drink, drink better alcohol. It costs more money and it's harder to find, and it tastes better, so you savor it and don't look to get drunk. A lot of the time now I just drink water if I can't find a drink I like. Not gonna waste my money on shitty booze that's bad for me anyway.
> This post is filled with bad and naive advice.

it's also got a very silly title. the way a boss quits is they sell the company.
The curve doesn't look legit. Percentages for each star level. I have the impression Amazon could predict potentially manipulated reviews with reasonable accuracy by analyzing the curve.

Edit: not claiming or implying anything about the author, book or the reviews. Just pointing the curve doesn't look legit to me.
I wonder if they keep their server times in sync with ntp.
It tells people to not bother inventing anything, everything “legally” has already been invented by people with more money and lawyers than you.
Why are they obviously minuscule compared to crypto mining? I'm unpersuaded that the ecological problems caused by crypto mining net above zero, but in any case they are obviously minuscule.
> the suppression of voting rights

Which countries allow voting by mail and/or without ID?
Except no company is going to give you the equivalent of 4 years of salary upfront. That’s the part you’re missing; companies that give 4-year RSU grants are effectively giving you an (illiquid) advance on your pay that grows until you vest and cash out.
> We have escalated the NAVI Clock Issue to our Engineering Team and they have informed us that you will experience issue from Jan 2022 thru August 2022 and then it will auto-correct. Please be assured that we will continue to monitor this and will advise you if a fix is available before that time.

It's amazing that it will start working again in August/September
Hmmm... Fake? What makes it feel fake for you?
They literally are rights, they're enshrined in law
Sounds like a good approach, and also based on what I’ve read here is inline with how a good interview should be. Thanks for the tip and for the open positions, but I’m in EU and I don’t fit in any of your currently open positions 100%. Other people reading about your process and open positions for sure will find this helpful :-)
If you truly must live your life in fear of dying, look no further than heart disease and car accidents.

Those are not as scary because there are plenty of survivors, in various states of health. Rabies is notable for being a very binary and decisive disease with little advance warning or treatment.
Hairloss is even more of a head scratcher. I've seen people buy pretty much everything to get back or just stop hair loss, and I'd bet the potential profits are way higher than penis growing pills. There are tons of communities of completely desperate men revolving around hairloss. Yet, a part from minoxidil and finasteride, which are far from ideal solutions and can't really regrow lost hair, there's very little good research and no new products in the past decade or so. It's really a testament to how complicated our bodies are, if even hair growth can be so difficult to reliably control.
In a way, its no different than having colleagues with audible push notifications pings..
Average age of a car in the US is 12.1 years:
https://www.cnbc.com/2021/09/28/cars-on-american-roads-keep-...

Average time a new vehicle is kept is 8.4 years:
https://www.iseecars.com/how-long-people-keep-cars-study
Argentina is almost socialist in taxing terms. And 21 million of people are subsidized. I do not see a capitalist system subsidizing 21 million people. That is not capitalism. Call it something else.
The way it was explained to me years ago is that every error deducts an amount (probably 10, I don't remember exactly) from the running total of correct characters typed (WPM was calculated by dividing the number of characters by the time and by a fixed "average" word length (ISTR they used 6 (in Dutch)).

So if you type 100 characters and 24 of them are incorrect, the counted total is 100 - 10*24 < 0, independent of the test length.

This was in the time of typewriters; computerized text entry did exist but was certainly not ubiquitous. There was no real way to correct mistakes, so I can imagine typing correctly from the beginning was a bigger deal than it is now.
Your assumption about the demographics of HN is counter to everything I've seen. Most of these people do have money. Simply by virtue of being professionals in the US, they are part of the 1%.

If someone was really inclined, $20k USD would pay for a year's rent in a comfortable apartment. $20k for other expenses. A year of grinding is open to a lot of people here I bet. They just don't want to do it.

The fear is too large, the inertia of normie life too great.
Yes, it's in the list of guessable words - however it's not a valid answer word. You need to use the WORDLE word list in order to evaluate how good or bad your initial guess is, using another word list will provide distorted results.
One of the exceptions shown was a guy who was asleep below deck when his fishing boat sank. Iirc he treaded water for a while as all crew mates succumbed one by one. He then swam to shore (miles i think) then walked several more miles to a house.

I think he collapsed on the doorstep (again having "made it") but was okay in the end.

He was not a slim guy, not sure if that helped.. but it was one of the dont give up examples. So outcomes do vary wildly.
A few thoughts:

Get the project goals in writing. With good relations, an informal assignment and commitment on both sides is sufficient, if met. That does not appear to apply to you.

If you met the (nebulous) goals, your upper manager might be trying to talk you out of a bonus, or other accolades. This time, let it pass (and say so), but remember how the game is played.

You were criticized for not mining the work of other teams. Place your plans of collaboration before your management, and ask for guidance.

I could say more, and far more options are available to experienced developers within your organization, but the point is that you don't (yet) have these connections, and a grapevine is something you don't have. Your management wants you to have a technical grapevine to mine, but not a running history of their management style assets and disadvantages. Cultivate both.

Be ready to step into another job. Even though you met your goals, they don't seem particularly loyal.

Save your admiration until you are certain that it is deserved. You haven't seen all sides.

Above all, take time to set all this aside, and enjoy your life.
Dont worry too much we've all been there. If you want it easy, work at a junior farm first (badly funded startup), that will both lower expectations from the top (you re cheap, nobody is experienced), and create contrast if you work a little bit better than the rest.

I joined a new industry with new methods and Im one of the youngest dev at 30+, and I can tell you all those years working with result first and insane deadlines because no money, makes me more comfortable: even if I dont know something they all do, Im the one pushing for doing it faster anyway and I know the tricks to use productively things you understand halfway while you learn the other half. And when I screw up something they never would have, it's management defending me "but at least he got it done in 2 weeks eventually when you quote us 6 months all the time", which is unfair to the perfectionist OGs (shortcuts were taken) but such is life.

Also accept, as we all do, that it's the job of some people never to be happy and to try the pressure angle on devs of projects slowing down just in case it does something to move faster. And try to stay on the cheap salary side for 2 years while you become useful, that tends to compensate for your lack of xp and their impression of juniors. In my company, the training material for managers to deal with "millenials" is that "they are impatient, they care more about their impact and the praise their receive than the company bottom line" so while that's exaggerated probably, it's also good to reflect on why you care so much about the kudos. Make the money, claim the money.
Yeah I agree. I think understanding the protocol makes it much less likely to introduce protocol level bugs during implementation. E.g. why certain steps need to be done in certain order.