skysight-inc/HackerNews huggingface dataset:
There are many different types of meetings, so you will need to give some additional color on yours (number of people, frequency, is it within a team, cross team etc).

Effective meetings are hard. I struggle moderating them constantly. Here’s what I learnt:

- Be clear about the purpose of the meeting - is it knowledge sharing, is it to kick people’s butts to progress towards a goal, is it to build camaraderie, etc. Information sharing can be much looser in structure, a project meeting needs to be run with a more tight agenda. A social meeting should be relaxed and have avenues to break the ice

- Always keep meeting minutes (unless it’s a social focused meeting) and write down who will do what afterwards (and follow up on those points). Even if the first few times it’s unsuccessful, eventually it will improve overall discipline. However sometimes it’s an uphill battle that can’t be won - imperfection is okay, people are lazy and won’t do everything they agreed to do in a time manner. Just push them in the right direction

- Focus on the important things, make sure they are covered off in the meeting. Thus, meeting prep is vital - plan the interactions as much as possible in your head and write the goal you want to achieve from the meeting

- Don’t hold unnecessary meetings. Respect people’s time as much as possible

- Practice makes perfect. There are so many combinations of types of meetings that you just need to develop a feel for them

- Try and understand the personalities of who is attending. This will give you strategies to make the meeting more effective. For example a decision maker who never replies to emails and takes too long to make a decision - you want to pin them down in the meeting and gently pressure them to come to a conclusion, because once the meeting is over, they will spend another week procrastinating! Others like to work together and chat more, for them, meetings help give energy to move towards common goals. Others are less social and want to focus on doing work, those meetings should be much more concise and direct

Hope that helps
This is what I thought the linked article would be about!
No that I definitely wouldnt use.
And Tesla owner demographics (presumably mostly affluent + older) with "everyone".
Yes I was able to get it to successfully work, you just have to keep zapping elements until the page displays properly. This also works on instagram if you're viewing without an account, though they seem to shadowban ip's now as I can't view accounts until after a few days.
The lack of limitations is part of the problem. We're currently at the highest number of COVID cases and deaths but despite that there is a lot of resistance against the government implementing a lockdown, in large part because the federal government is run by science-hating lunatics.

The most horrifying recent news is that hospitals around the country are running out of sedatives used for COVID intensive care. There have been reports of intubated patients waking up from sedation and having to be tied down to their beds to keep them from ripping out the air tube. It's inhumane.

(Link warning: shocking images) https://www1.folha.uol.com.br/equilibrioesaude/2021/04/nas-u...
Couple of notes I'd like to throw out there...
- The Serverless Framework does help ease quite a few of your concerns, local development is made much easier (they have a node server for js development). The company working on it is kinda funny, but I still think it's a good tool. I currently use the raw lambda environment at work and can say that the serverless framework is a valuable abstraction.
- I think Cosmotic is making their deployment setup more complicated than it needs to be. I obviously don't know their use case but there are easier ways to accomplish a CICD w/ FaaS...
- I would recommend trying it. Its pretty painless, and you'll know within ~2-4 hours whether or not it will work for you
> it! You said it yourself!

'It' refers to the word there. The thing the word refers to is a plural.

> It's not a plural, it's a singular company.

That's just not traditional in English. What is a company except a group of people? That's what the word 'company' literally means.

Most people in English speaking countries outside US influence would say:

> Apple, an American company, have announced a new iPhone.
The largest lego market,(states) refers to them as legos. See amazon, NPR, ect
https://www.google.com/search?q=%22legos%22
Not sure if intentional, but this is exactly the opposite of the message of the article.
> NEVER add a possessive “s”, plural “s” or hyphen, e.g. LEGO’s design, more LEGOs to play with, LEGO-bricks.

reference: https://www.lego.com/cdn/cs/legal/assets/blt1a4c9a959ce8e1cb...
> Like, even accessing production logs is weird - you have to "tail" them from your CLI.

Which seems to fail for access-protected sites since `tail` uses the same domain as the real endpoint. Also no error reporting - the exception may be in the logs, but it's missing the stack trace unless you log it explicitly.

The monitoring side of workers is extremely poor currently.

Also unit testing workers is hard to get right - there are no good mock libraries for request and kv which behave exactly like the production versions, so you end up with surprises after deployment.
This is nuts. Having management approve meetings? How about "learn to communicate: decline unnecessary meetings and figure out how to reconcile disagreements".
I have read the criticism of how the Autopilot miles aren't apples-to-apples comparisons with national averages many times. However, this cherry-picks a single number from the safety report and ignores the other reported statistics. If the explanation for why Autopilot miles were so much safer than non-Autopilot miles is that people turn it off in dangerous situations — and thus equal or greater numbers of crashes were occurring for Autopilot users overall compared to the national average, they were just occurring when Autopilot was off — the crash rate without Autopilot engaged would have to be higher than the national average. Otherwise, where would the crashes go?

However, it isn't. The crash rate with Autopilot off (but with other safety features on) is about 4x better than the national average. And with all safety features turned off, it's still 2x better.

I don't think you can explain away the high safety record of Autopilot by claiming the crashes are concentrated in the non-Autopilot miles, because they aren't. While Autopilot miles are safer than non-Autopilot miles, non-Autopilot miles are no more dangerous than the national average (and in fact are less dangerous).

Autopilot+human is considerably safer than human alone.
I feel we need to read all these stories with a skeptical eye because, frankly, Huawei's become a political football, and there is a very strong motivation to cast events in the most unfavorable light possible by officials who are working backwards from the conclusion. Perhaps they do have some kind of spying master plan but I have found a lot of the fanfare for these stories hasn't held up to scrutiny.
1) is a great advise that I think I can make use of, same for 2).

For 5) I feel it is hard. Often there are expectations that you join meetings just in case a higher-up manager needs a piece of information or I am afraid to loose out on critical information. Do you, in your organization, have an active meeting culture with feedback for meetings? It feels to me that in my organization too often when a conflict, next steps or any other decision is needed, instead of writing about it people just schedule meetings to discuss things. And then there are meetings where people just share information ("team meetings") that could be shared in writing much more efficiently (people read faster than others talk, so reading information is often more efficient from my point of view).
The biggest challenge I see is the years of experience requirement on certain technologies that disregards ones that are very similar, particularly when that requirement isn't central to the problems being solved.
it’s not terrible because the middle upper classes don’t use it. the middle/upper classes don’t use it because it’s terrible because of the people who live in it and do terrible things. sorry it’s not PC but it’s true
Yep, The three others I know of are Center, Texas, which is not in fact in the center of Texas; Earth, Texas, which I suppose is in fact on the Earth; and Texas City, Texas, which is indeed a city in Texas.
I live close to the tower and I was really positively surprised how it turned out. It is located next to Rottweil, the oldest town of Baden-Württemberg with a lot of buildings of historical value. There was the fear it would destroy its overall appearance, but I feel like it complements it just perfect.
Especially during sunrise/sunset the light creates a beautiful effect on the tower's winding facade.

See:
https://commons.m.wikimedia.org/wiki/Category:TK-Elevator-Te...

https://commons.m.wikimedia.org/wiki/Category:TK-Elevator-Te...

https://commons.m.wikimedia.org/wiki/Category:TK-Elevator-Te...
This comment has it all. A lot of other folks are missing the importance of a follow-up email. I always send a follow-up with notes/conclusions and action items assigned to people.

Too often I’ve attended meetings that might have well never happened because whatever got discussed was forgotten a month later and another meeting was held to discuss the same thing.
+2x - The logs are funny. they'll duplicate, show up late, etc
Though I can't read the actual report, this article does not support your claims.

>Apparently also a list of numbers under surveillance by Dutch intelligence was found in possession of Huawei. Which was clearly well beyond those boundaries

Wouldn't the ones running the network need to know which numbers were under surveillance to provide the intelligence agency access?
You can easily process the audio on the fly and reduce it to a probabilistic estimate of whether a tag from a predefined topic set was present in the conversation. Doesn't need to be 100% accurate. You don't need to store the audio - just stream it through the recognizer. The output of such recognizer will be something on the order of 8-32 bytes (an int for tag, a float for probability, an int64 for timestamp), possibly less if one's clever - and it only needs to be stored until the next opportunity to send it out.

Also: people seem to be looking at modern speech recognizers on their phones and wrongly concluding that speech recognition in general is very compute-intensive. It isn't, if you're willing to make some sacrifices on accuracy and generality, and to do it locally instead voice data off to a cloud somewhere. A proper benchmark here isn't Siri or Google Assistant - it's Microsoft Speech API, as shipped with Windows 12+ years ago.
NSA tapped German Chancellery for decades, WikiLeaks claims : https://www.theguardian.com/us-news/2015/jul/08/nsa-tapped-g...

Supposedly, that did actually happen.
Ends up being sort of like QEMU, translating VT52 input/outputs into the input/ouput whatever your actual terminal is. That's pretty neat.
I completely agree that they should not show up. It looks like I went lightly over that sentence and focussed more on the one after:

> Some of those keys are related to people who bought it, or who searched for it, or more indirectly who lingered while reading a page with an ad for it...and in most cases are very short lived.
What they of course should do is count any manual intervention as a possible autopilot accident.

When I say possible, what I mean is they should go back, run the sensor data through the system, and see what autopilot would have wanted to do in the time that the human took over.
My tinfoil hat theory is that making local development difficult is the goal rather than a side effect. Why not just run the stack yourself if it's that easy? Better for Amazon if the development process for using their services involves as many other AWS services as possible.
Mice fed fast food get noticeably stupider, scientists warn
Brings a whole new meaning to thermal runaway
> Fundamentally better for whom?

In the long run it's better for everybody. But it is true that "the long run" can be pretty long.

> Do you think Google has never considered that business model?

I think Google probably considered it early on but found it easier to go the way they actually went. But "easier" is not the same as "best in the long run".

> their current business model will let them extract the most money from their products

Google doesn't have products, they have services. And of course, since their services are free to users and users are now addicted to that, they can obviously extract more money with their current business model since they have made a concerted effort to make the "users as customers" business model impossible.

However, their current business model was being built during the same time period when "Don't be evil" was still the company's motto and still apparently taken seriously by company leaders. Which means those leaders were either very disingenuous or delusional. Because addicting people to a free service and then exploiting them and their personal data in order to make the money they can't make from the users directly, as customers, is evil. And trying to keep their current business model propped up in the face of users becoming increasingly aware of the ways in which they are being exploited, is only going to force Google to be more and more evil. Sooner or later, if it doesn't change, it will kill Google as a company.

> That’s why we need regulation.

Regulation won't fix this problem. Corporations can always either buy their way around regulations (oh, another million dollar fine because we broke regulation XYZ about exploiting user data? just rounding error in our accounting) or buy enough influence to get the regulations written so they don't actually impose a burden on them (but do impose a huge burden on potential competitors, the new startups that would otherwise be finding ways to disrupt Google's current business model, since users are clearly becoming dissatisfied with it).

The only thing that will fix this problem in the long run is for users to realize that there is no such thing as a service that is (a) free and (b) valuable. We are going to pay the costs somehow. The simplest way to pay them--with money--is also, in the long run, the best.
> what you're asking is far beyond "illegitimate"

Wanting to be acknowledged is illegitimate? Because that's really all I read from that. Being acknowledged not even for one's self, but at least for what one does or has done.
> “If the tenant and the notary both vote that there is bullshittery going on with the property, rent is suspended.”

First, I think the word you're looking for is arbitrator. Notaries don't resolve disputes.

Second, you've simply replaced a judge with a "notary", and left many questions unanswered. Who is this trusted 3rd party? How are they accountable? Can you appeal their judgements? Do they have an ongoing business relationship with one of the parties? And so on.

I suspect that by the time you've answered all those questions, and dealt with all the issues that arise that require human judgement, you'll have reinvented government. Or worse, digitized mandatory arbitration.
Hi there, product person here. Due to the nature of the role I have to create meetings to agree on approaches, align on directions and communicate often. Very very, keen not to waste anyones time, so I try my best to email first and be present when facilitating meetings.

Two quick frameworks that you might find helpful:

1) The POST method, to give clarity at the beginning of a meeting:
Purpose: What is the purpose of the meeting?
Objective: What are you trying to achieve in the meeting, and what does success look like?
Structure: What is the structure of the meeting we are having?
Timing: How much time is allocated to the meeting?

https://gist.github.com/aaronbuchanan/2dcf936daceab925da61

I like this because it helps give quick context, also the mnemonic is quite handy.

2) Try to structure your meeting around other people's questions:
- Going from basic what questions working up to why we need to make a decision, how they might be impacted etc.
- I wrote a short post about it here: https://www.logikblok.com/supporting-asking-questions

I like this because it focuses your communication around your audience/user needs.

Aside from that and keeping everyone on the same track of discussion / time / documenting agreements all help out. Hope that helps.
Profit motive drives your rent up.
SST is an Open-Source framework worth checking out if you are looking for a lighting fast local dev environment for serverless.
https://github.com/serverless-stack/serverless-stack

I often see ppl adopt one of two development patterns:

1. Locally mock all the services that your Lambda function uses. Like API Gateway, SNS, SQS, etc. This is hard to do. If you are using a tool that mocks a specific service (like API Gateway), you won't be able to test a Lambda that's invoked by a different service (like SNS). On the other hand a service like LocalStack, that tries to mock a whole suite of services, is slow and the mocked services can be out of date.

2. Or, you'll need to deploy your changes to test them. Each deployment can take at least a minute. And repeatedly deploying to test a change really slows down the feedback loop.

SST lets you develop your Lambda functions locally while connecting to others AWS services without needing to mock them locally. Behind the scene, the lambda requests are streamed to ur local, runs ur local function, response streamed back to Lambda. So you can iterate on ur function code without redeploying.

Think of your Lambda functions are Live Reloaded. You can see it in action here — https://youtu.be/hnTSTm5n11g

I’m the core maintainer of the project. And folks in our community are saying using SST feels like "working in the future" ;)

I'd love for you to give it a try. We are also a part of the YC W21.
Scoop is maintained, but just... really slowly. It's a shame. For example it took more than a month and two maintainer pings to merge an absolutely trivial PR to add Python 3.8 (a single character change over the Python 3.7 manifest): https://github.com/ScoopInstaller/Versions/pull/226

For the most part, this does not matter. Most of the existing stuff is already present in buckets and auto-updated by CI. The problem is just when something breaks or something new needs to be added, which can take a non-deterministic amount of time.
> Public transport works well when your city prioritizes it.

And when there is critical mass. Public transit works in dense urban centers, because it's less worse than driving and parking. It doesn't work in smaller towns. There, it just becomes something that everybody pays for but a tiny minority of people ever use.
> and test your system end-to-end.

How do you automate this?
I could have written your message word for word. I recently had a very similar experience moving to AWS Lambda using AWS CDK and SAM. It is pretty shocking how unhelpful the AWS documentation can be at times.

Each use case is so unique, that it is likely difficult for them to account for every single situation where Lambdas are being used. Instead they opt for a generalized and non-specific documentation site, which results in docs I find practically useless.

I frequently find solutions to problems for AWS on someone's obscure blog, who after many days of suffering stumbled onto the answer, rather than finding anything of use directly from those who wrote the software.

Does a site exist where programmers can submit useful findings? Similar to stackoverflow, but rather than asking for questions, you just submit answers. I would think being able to search across such a crowdsourced utility would save programmers a ton of time.
Ask HN: Good resources to become a better Product Manager?
I’m trying to improve my skills as a PM to better work with my team, customers, and help define the best features, goals, and products to help my company grow.

Given that Product Management is a little bit more nebulous in terms of specific skill sets, I’m looking for great books, blogs, videos, or courses that will help me become a better PM, not just for myself, but for my team.

What help you become a better PM?

How did you take your skills to the next level?
This is getting silly. Huawei is the most prominent Chinese company and because of the economic war, you get such speculative articles.

And a few days ago, Cisco was found to have a bug in their routers for small businesses that lead to remote code execution. https://portswigger.net/daily-swig/cisco-router-flaws-left-s...
The Tesla Safety Report is so misleading:

1. The accident rate does not take into account of drivers age, credit score and prior safety record, or the age / value of the car.

2. Most people only turn on autopilot when driving is easy (e.g. on a highway).
AutoPilot will also disable if you unbuckle your seatbelt or lift your butt off the seat.
Maestro is MasterCard btw
Your third point, setting an "end goal" is a great point! I have not thought about that often enough. I usually set agendas for my meetings but too often I do not define the ideal "final state" I would like to see from a meeting. Do you expect this also from others when they send you meetings? How do you handle regular meetings as a product manager, e.g. Sprint plannings in a Scrum context, do you then say: "My end goal for our planning is that everybody knows what to do in the next sprint"? Also, I tried to also ask this to others, but how is meeting feedback in your organization? My own meetings I have control over, but those are less than the ones other schedule where I am a participant, not an organizer.
Not sure that these guys are in the reddit demographic... but regardless, Tesla intends their cars to be a mass-market product. Peer pressure is a thing, and many of the people who buy these cars are showing them off to their friends who are eager to see the "autopilot" in action. When people are given conflicting information, they'll believe the story they want to believe. ("that fine print is just stuff the lawyers put in there") While drivers have the ultimate responsibility for sure, the situation this perception has created is foreseeable.

https://abc7ny.com/amp/tesla-crash-houston-fatal-car-autopil...

> two men who were found dead inside the car had dropped off their wives at a nearby home and told them they were going to take the 2019 Tesla S class for a test ride.

> The man, ages 59 and 69, had been talking about the features on the car before they left.
Woman Collecting Shellfish Discovers Dinosaur Footprint of ‘Jurassic Giant’
They really should
Not really.
Housing resembles nothing like a free market.
Supply and demand is driven a lot by political forces (regulation, political favoritism) that effectively limit supply.
Large land-owning political entities or blocs have outsized influence on these factors.
TIL: The desire to inform people that they have been doing the buzzcut on themselves for a long time before the pandemic is quite strong. ;)
Op asked:

> Anyone have any suggestions or share my frustrations?

I shared my experience and asked them a question. I at least contributed to the discussion.

Your comment basically adds nothing to the discussion and is essentially cyber bullying.