Hacker News .hnnew | past | comments | ask | show | jobs | submit | JazCE's commentslogin

I was working on an Arazzo[0] generator as a plugin for the Serverless Framework. This has now become a fully fledged runner. So far I have it using multiple OpenAPI source descriptions, and just about got retry rules working. Next steps will be for it to be able to reference Workflows in external Arazzo documents.

[0] https://www.openapis.org/arazzo-specification


It's something i've also vaguely thought about building myself, because god damn uber, how many times do you need to send me an advert for uber one? just tell me when my car is here.

so congrats to the author of this. I do agree that I'd prefer it open sourced too, it feels a bit risky it having access to all your notifications.


> Really? Wanna give it a try then, without looking up any other documentation?

I mean, that's not the point of SO or any of the SE sites. It's not there so you don't have to do some more work to get to an answer.

From that answer, if you're still having issues, you form a question around:

"I found this answer on [SO](link), which lead me in this direction and found these [documents](link), however I am still having issues with getting the thing to work correctly when i run this bit of code, ```code```, from the output it says it's doing this or that, but when i check something, i find that it's not doing what it claims in the outputs. What might I have missed?"

And even then, that's still a fairly shaky question.

Most people don't know how to write questions, which is most of what this whole comment section is complaining about.


> that's not the point of SO or any of the SE sites. It's not there so you don't have to do some more work to get to an answer.

My brain is spitting out a parse error on this sentence. Too many double negatives.

Zahlman was claiming above that the "duplicate" question linked earlier in the thread wasn't a useful question. Its not useful because if you read the accepted answer in the original thread, you can figure it out easily.

Prove it then. Figure it out easily for us.

I think the point of SO is for people to look up the answers to questions they have. If people have similar but distinct questions with different answers, it seems objectively better to surface both SO threads. Ideally they'd be linked together so if I accidentally stumble on the wrong question, there's a link to the question I'm actually interested in.

> "I found this answer on [SO](link)

Why bother with all of that? I mean, it sounds like all those extra words are all to grovel sufficiently to the SO moderator-gods, hoping in their capricious anger they won't mark your question as a duplicate and wipe it from the internet. Grovelling doesn't help the question asker or the question answerer.

As a user, my problem with SO isn't that people ask bad questions. Its usually that the question I actually have - if its been asked - has long ago been deleted as a duplicate. And the only question remaining on the site is subtly different from the problem I'm actually facing. Or the answer is tragically out of date. Perhaps if people asked better questions, the moderators would be happier. But the site shouldn't be run purely for the benefit of its moderators.

It became a meme. "How do I do X in javascript?" "Here's how you do it using jQuery." "But I'm not using jquery." "Question closed!"


> Zahlman was claiming above that the "duplicate" question linked earlier in the thread wasn't a useful question. Its not useful because if you read the accepted answer in the original thread, you can figure it out easily.

No, I was not. Duplicate questions are often very useful.

They just... shouldn't host separate answers in a separate place, because that leads to a) duplicated answering effort and b) dilution of results for third parties who search for the information later.

Having a question like this linked as a duplicate highlights the fact that the same fundamental problem can be conceived of in different ways, and appear different due to ancillary requirements.

> If people have similar but distinct questions with different answers, it seems objectively better to surface both SO threads. Ideally they'd be linked together

But we aren't talking about different answers. A bit of adaption to ancillary details is expected. Otherwise there would be no duplicate questions, and also no reason to ever try to have Stack Overflow in the first place, because asking on a forum would be fine. Searching the Internet to figure out how to fix your code could never work and never help, because obviously nobody else has ever written your code before.

But problem-solving doesn't actually work that way.

Closing duplicate questions as duplicates is linking them together.

> Why bother with all of that? I mean, it sounds like all those extra words are all to grovel sufficiently to the SO moderator-gods

This is because you are still approaching the site with the mindset of "what do I have to do to get these other people to give me the information I want?"

But it's not (just) about you. A good question will be seen by many other people.

> Its usually that the question I actually have - if its been asked - has long ago been deleted as a duplicate.

Duplicates are not automatically deleted and not ordinarily manually deleted.

> And the only question remaining on the site is subtly different from the problem I'm actually facing.

Would reading the answers give you the information need to solve the problem, after first putting in the expected effort to isolate a single problem? If not, why not? That's what we care about.

> Or the answer is tragically out of date.

My experience has been that old answers are not actually "out of date" nearly as often as people would expect. But when they are, this is fixed by putting a new answer on the existing question. The bounty system was created largely for this reason. It has proven a failure, for a variety of reasons, but that's a failure of understanding gamification, not a problem with the model.

> Perhaps if people asked better questions, the moderators would be happier. But the site shouldn't be run purely for the benefit of its moderators.

It's frankly infuriating to read things like this. I have already said so many times that the overwhelming majority of the people objected to are not moderators, but people insist on using that language, not making any effort to understand the existing community, and then wondering why they feel unwelcome. More importantly, though, we are going out of our way to try to build something that benefits everyone. While most people asking questions are thinking only of themselves.


Thanks for replying. I find your point of view for all this fascinating.

With your experience, why do you think the site is failing? What could or should be done to save it?


Top-level view:

from the perspective of people who aren't explicitly trying to teach on their own initiative, overall the site has outlived its purpose. In that time it drew way too many total questions to surface what's actually valuable; between that and no functional search (the internal search was always bad; Google et. al. got worse over time, partly intentionally) you're lucky to find anything valuable.

I'm not generally worried about out-of-date answers; the truly outdated answers are mostly on outdated questions, describing situations that don't come up any more or premises that are no longer valid for ordinary programmers (e.g., fixing problems with obsolete tools).

Combing through to curate properly is too little, too late now. Much stronger (but polite, of course) gatekeeping was required earlier on, which in turn required (among other things) proper means for communication between "core" users and the public. At this point, it's best to start over (hence the part where I'm now a moderator at Codidact).

There's a lot more I want to say, but I don't have it organized in my head and this is way downthread already. Perhaps I could interest you in a hypothetical future blog post?


> Perhaps I could interest you in a hypothetical future blog post?

I'd love that.


> Perhaps I could interest you in a hypothetical future blog post?

yes please!


As one of my good friends pointed out back in 2012, most people don't know how to ask questions[0].

I'm feeling a bit sorry for zahlman in the comment section here, they're doing a good job of defending SO to a comment section that seems to want SO to bend to their own whims, no matter what the stated aims and goals of SO really were. There does seem to be a lot of people in the comments here who wanted SO to be a discussion site, rather than the Q&A site that it was set out to be.

I do think it's very unfair of many of you who are claiming SO was hostile or that they unfairly closed questions without bringing the citations required. I'm not saying at all that SO was without it's flaws in leadership, moderators, community or anything else that made the site what it was. But if you're going to complain, at least bring examples, especially when you have someone here you could hold somewhat accountable.

The problem is, you still see a lot of it today, whether it's in IRC channels, Discord chats, StackOverflow or GitHub issues. People still don't know how to ask questions:

* [1] * [2] * [3]

[0]: https://blog.adamcameron.me/2012/12/need-help-know-how-to-as... [1]: https://github.com/swagger-api/swagger-ui/issues/10670 [2]: https://github.com/swagger-api/swagger-ui/issues/10649 [3]: https://github.com/usebruno/bruno/issues/6515


Anyone remember the Sony Ericsson Xperia Pureness: https://www.gsmarena.com/sony_ericsson_xperia_pureness-revie...


The Author doesn't understand how the streaming business works, and as far as I can tell, no one in the comments here has shone a better light on it.

There is and there isn't just a pool of money that goes to beyonce, the weeknd and taylor swift... i say there is because what actually happens is, the collecting societies will collect the money, then distribute it based on streams correctly to the artists/writers/producers etc that are registered. now if it so happens that a collecting society can't find the correct person to distribute to, the money might sit for a while before it is divvied up between the biggest players, so that would mean taylor swift, elton john etc might get a share of any unclaimed royalties.

When i worked in the business, we would often have many a drunken night talking about how we should just record the rain on the roof, upload it and use the "royalties" as beer money.

for the most part, being on spotify does pay, but i think people don't really understand how the pie is cut and when the artist actually gets a slice. there are many routes to being on spotify (or any streaming service), the router for taylor swift will be different to the route for your dad's garage band, as will the payout.


Since you seem to understand how it works, can you explain the following to me:

Let's say I pay $10 to listen to my favorite indie band, for 1 hour each week.

Let's say another user listens to Taylor Swift 24/7.

Does my favorite band get my $10, or do they get $0.12? You see, when I pay $10, I don't expect $9.88 to go to Taylor Swift.

Or does my favorite band actually gets my $10, like it used to be when I bought CD's?


Spotify uses a pro-rata model, so your favourite indie band would only get $0.12 in your example.

This effect does not drown out once you scale up to a full user base either - it appears that the most popular artists benefit disproportionately. Other music streaming companies like Deezer apparently are pushing for a fairer model. See here for example: https://musically.com/2018/03/02/user-centric-licensing-real...


people seem to be confusing the $10 spotify premium sub with actually giving money to music.

i think there's an over-simplification of how this works going on. When you buy a $10 cd from let's say your dad's friends garage band, that $10 is going to your dads friend, and obviously they might have expenses before they really see that $10 (buying CD-R's, printing, etc etc).

you spend $10 on spotify premium, and exclusively listen to your dads friends garage band, that $10 is not going to your dads friend, it's going to spotifys bank account which will then be used to pay for execs, macbooks, operating costs etc, but also be used to fund the artist pool. so your $10 and some other persons $10 that they use for elton john records, all sit in the same account. Elton John via EMI or whoever, might have negotiated a 0.000005c per stream deal and so gets that. your dads friend might be on a very basic rate of 0.000002c per stream (numbers made up), and will receive that. so yeah elton or taylor or other big names will get a better deal.


If you listen to a single band for 1 hour a week, then you should not be paying for a Spotify subscription, but rather buy the music of that band.

This situation is obviously constructed, but if you were in it and unhappy about it, it would be your own fault for misunderstanding what you're paying Spotify for.


complaints about spotify payment will almost always have a critique along the lines of

"i pay $10/month to listen to {obscure band}, but only $1/month is going to that band and the rest is going to {popular band}!"

this is a technically true statement that seems to fuel a lot of anti-rich-getting-richer / popular-thing-is-bad-but-my-taste-is-good backlash. but the fact that is always overlooked is that while you are only sending $1/month to the obscure band you love, the millions of listeners that are into {popular band} will also be sending a tiny fraction of their monthly payment to your artist as well.

determining whether pro-rata payments or user-centric payment systems are more equitable is complex and is studied in the academic literature (e.g., [0]) but ALSO internally by streaming providers (i know from firsthand experience[1]).

[0] https://www.sciencedirect.com/science/article/pii/S016517652...

[1] it's interesting to note that the difference between the payment systems affects how payments are distributed to artists but not the total amount, so theoretically the streaming provider isn't biased toward one system over another for business reasons. the streaming platfroms don't really care one way or another and it's 100% driven by what the labels dictate during licensing negotiations.


Spotify should add an option to pay an additional $3/mo that is in fact distributed to the artists you listen to.

However based on my past experience with general public users, it will be a rounding error number of people who will opt into it.


Swift owns her master recordings. So her bottom line on every listen is MUCH more than artists stuck with a label.


Kelly Somers has been vindicated.


The problem with judging any of this is the same as knowing your history lessons and sources.

All we've really got to go on is Brittney Peaches account and Matthew Princes account and neither are going to be reliable sources. We'll never know if what Brittney Peach said is reliable and we'll never know if what Matthew Prince says is true.


She made a video of the whole conversation??? What else do you need to make a decision?? You heard both sides, take a position, (by the way, Milk Toast is not a position)....


Exactly. Much of the debate is about how HR handled this so poorly and that's what we can all hear on the video. It's not really about whether her performance was worthy of getting fired. Nor is it about the Cloudflare bottom line.


The problem with judging any of this is the same as knowing your history lessons and sources.

All we've really got to go on is Brittney Peaches account and Matthew Princes account and neither are going to be reliable sources. We'll never know if what Brittney Peach said is reliable and we'll never know if what Matthew Prince says is true.


Why is Brittney’s video not a reliable impartial account? Also note that nothing she says about her performance and feedback is in any way disputed during the call. They had nothing to say to the contrary.


We don't actually know what her manager said to her during all her one to ones. We don't know what feedback she was receiving. Just because the person on the other end of the call did not dispute any of the things she raised, it does not mean she was correct and not biased.

We also see from Matthew Prince's reply to the video that he is also an unreliable participant as he is suggesting that a manager would always be involved in redundancies, and we can see from the video that was not the case.


HR is not going to argue on a call like that, so the viewer will always see a one sided account. The decision has been made, and not by them. They likely do not even know or have access to that information and are given a list and told "fire these people today." She could have come to work drunk, and you would still not hear about it on a call like that. I don't like it either, but it is the way things go at big corps.


We might never know if it was "justified", but we have everything we need to judge how the termination was delivered though, and that one is a shitty look for Cloudflare.


We also have the words of the HR loons who couldn't say anything consistent. So we kind of have both sides.


> In the UK (and most other places with fairly strong employee protections I imagine)

People keep saying this, but I'm not at all convinced anyone commenting really understands UK employment law. It's really only after 2 years of working for the same company that you get any decent employment protection.

It takes a bit more legal work, but if within the first 2 years they don't want you, they can get rid of you. If you're within your first 3 months of probation, they can just extend it to 6 months and get rid of you.

The UK is not a great country these days to go "employment laws keep you safe". There are better ones.

If you don't want these rug pulls and employment laws to keep getting watered down, instead of asking about 4 day work weeks, start voting for candidates and parties that have better employment laws at the top of their policies.


So I made a very vague comment about it being more tricky to get rid of employees in the UK. If you think it's not actually that hard as "it takes a bit more legal work", great.. but we still seem to generally agree. It's a bit patronising to imply I know nothing about UK employment law because we have a small difference of opinion around how robust we would say the protections are.

It was a minor anecdotal comment based on my own experience of hiring/managing employees. Maybe I'm a crap manager but I've always found it labourious to get rid of people (especially passed the 2-year mark as you say). I may as well add that my wife has worked in HR for coming up to 15 years as well and I've been privy to all sorts of juicy legal drama via her.

I generally try and give every response to me some consideration but I'm not sure what else to say. Seems like maybe you just wanted to use my comment as a segway into your point about the erosion of employee protections, which you're entitled to do of course.


> Seems like maybe you just wanted to use my comment as a segway into your point about the erosion of employee protections, which you're entitled to do of course.

That’s like a quarter of the comments on HN at this point (minus the employee protections bit, usually it’s something much more insipid). It’s pretty much impossible not to trigger someone. Everyone’s got their pet issues and culture wars these days.


Well, that's...fine, I guess, right? I mean that's how conversations work in real life, right? Just as long as the parent commenter doesn't interpret it as a direct attack or a direct argument. It just takes the conversation down a different path.

I'll agree with the word choice of 'insipid' however...


Segways are dangerous, just look what happened to the one time owner [1].

ITYM "segue".

[1] https://en.wikipedia.org/wiki/Jimi_Heselden


I think I typed something like that originally but my phone autocorrect didn't like it. Assumed Segway was the American spelling


Meh, you contributed to a certain meme and they contributed a counter-meme because they feel strongly about it. I don't see the problem though their tone might put you on the defense.

But these vague claims are how we end up with memes like "oh that would never happen in $place/Europe/Japan" and such.


>If you don't want these rug pulls and employment laws to keep getting watered down, instead of asking about 4 day work weeks, start voting for candidates and parties that have better employment laws at the top of their policies.

I think in the US employers would be more amenable to a four day work week than making it harder to fire people arbitrarily


>If you don't want these rug pulls and employment laws to keep getting watered down, instead of asking about 4 day work weeks, start voting for candidates and parties that have better employment laws at the top of their policies.

What would "better employment laws" look like for you? After all, the parent's theory was that she was fired because she was on the verge of getting additional employment protection, and her performance was mediocre, so rather than risk being saddled with an underperforming employee they fired her just to be safe. Stronger laws against termination would make this problem worse, either by causing companies to be even more aggressive to fire people before their probationary period ends, or try to mitigate risk earlier in the hiring pipeline.


Please show me the candidates that aren’t coin operated by big business. Either party is entirely beholden to the giant corporations and lobbyists. So voting literally does nothing.


>start voting for candidates and parties that have better employment laws at the top of their policies.

Unfortunately they may have other less savoury policies. Which is [one of several reasons] why I don't vote.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: