@hyper-neutrino I believe it means that they have "word of god" over what is and isn't correct. A lot of SO questions fall victim to the idea that the answerer may not actually know the answer but has just found something that works. Between this and the Outdated Answers feature, it seems as the SO is working towards improving the accuracy and correctness of their answers
when I initially saw it I thought it was like codidact's categories but without actually dividing them into separate locations and just grouping questions belonging to one category together, but didn't expect it to actually fundamentally change the way SO works
I think the ability for a corporation to mark an answer about something they created as "this is an actual good solution and not just some stupid hack" is a good thing, and I mentioned this in the codidact server discussion too, but like
I believe the current answer is "You don't, this is a trial", and they're working on expanding that out to more clients. But ultimately, this isn't something users create, it's something we'll use
like even if they don't disclose details on it due to corporate interests (which always sounds sketchy, but I don't understand enough legal things), at least like announce the upcoming things and get a bit of feedback on maybe potential issues or if it'll be absolutely hated and rejected
if we asked a CM about it they'd probably tell us "I just found out a few hours ago too" - I've been noticing recently that even CMs don't seem to find out about these things and the users and mods of the sites themselves are just kinda left wondering what'll happen at any time :/
Pretty much every major change recently has been "We're going to start doing X beginning from Y. Feedback?" This is a rare (but not rare enough) example of them saying "As of today, X is live"
I mean, community everything was the entire design principle of SE
it's honestly IMO what makes SE distinctly SE and not at all similar to like, quora, reddit, yahoo ans, whatever other somewhat related (or maybe not) things
@hyper-neutrino Something a lot of people were extra unhappy about when Jon, Shog and Robert left was the fact that after they left, they made it very clear that, as CMs, they had tried to help the community and were actively prevented from doing so by the higher ups
I like Catija, I think she's an excellent CM who genuinely cares for the communities both individually and as a whole. Honestly, I see a lot of Shog in her (hope you take this the right way if you're reading this Cat). I don't interact with the other CMs enough to pass judgement unfortunately, but I also like JNat (despite him often being the bearer of bad news). However, I can't think of a post by either Sara Chipps or Teresa in the last 2 years where my immediate reaction to seeing it wasnt to grab the popcorn. I don't know why those two in particular are/were often the lightning rods for…
It's an interesting contradiction to see, where even the company itself is split over the issue, and I hope it gets resolved in the best way possible for the community rather than for the corporate partners
If someone is willing to write up a whole post about something relevant to the site, I applaud them. For discussion style posts, it's less applicable, and it's always good to get some extra eyes on anything written, but if Razetime wants to write a blog post, good on them :P
Yeah, I definitely agree with that. Unfortunately I didn't have much interaction with Shog and by the time I started not just participating in my bubble of PPCG but building connections on the whole network it wasn't shortly after that 2019 happened, and by the time I returned to being active and eventually became a mod Shog was long gone :( I've only really interacted with Catija and JNat and I really do love working with both of them; unfortunately like you said JNat does often get the task of posting the bad news, but I really do look up to the way they handle things and honestly try the…
@cairdcoinheringaahing Proton, (&) :P
take the value on the left and the function on the right, or if you want to bind the right argument, vice versa
@hyper-neutrino My biggest takeaway is that 1) Neither Sara nor Teresa nor anyone in particular was entirely at fault for the shit SE went though (and is going though) recently, and that they are still people who deserve to be treated that way. 2) The day that SE makes it clear that they will only prioritise their corporate partners over their communities is the day I leace
you can use like tonality plus stress accenting plus pitch accenting plus whatever else and then use abuse overloading or whatever else you can think of
And the way that a lot of people were treating Sara in the Monica incident was disgusting. SE shouldn't have treated Monica the way they did, but even if Sara had clicked the button herself, she's still a person who deserves respect, and too many people forgot that in the heat of the moment
1. Yeah, that's a good way of putting it - I mean, it makes perfect sense to criticize the individual behaviors staff do if not the posts that we can assume (if we're being generous) had nothing to do with them and are just "corporate says this" - but I agree; treating other people that way no matter _what_ happened just makes the whole situation worse and is honestly really disappointing too. We can say "this staff action shows that the community isn't prioritized" but attacking Sara herself was just unacceptable.
like you could say 私は食べました (I ate) but if you just say 食べました (ate) it's implied that you're talking about yourself and you can get away with it, whereas english has an explicit need for the subject with a verb
@Razetime Burger is meat. Meat is dead animal. Dead is not alive. Animal is alive. Bread is yeast and time. Yeast is bacteria. I eat burgers with bread. :P
the grammar system didn't make sense to me at the time but I vaguely remember it having a similar concept to japanese? or like, having particles to indicate things and then the main sentence structure just being verb
like something I read somewhere IIRC said like "english is SVO, some people think japanese is SOV, but a native japanese speaker will tell you japanese is just V"
here's another idea - instead of tacit where everything is a verb, we find a way to construct everything into nouns and a sentence is just a block of nouns that follow some structure
like you place two nouns next to each other to equate them
It's ambiguous because you don't know what it is until you decipher it, at which point it's too late and Rick Astley has already kidnapped you and brought you back to his archway lair
@hyper-neutrino I say SE switches to the business model when they sell one byte each of source code to millions of different people for a few dollars each
You can pay extra to make your byte stop working that month :P
@hyper-neutrino Nah. Not in this case. We've been working with them on it for months, helping them understand the Community perspective along with the mods/users they were talking to.
@Catija Oh - good to know then. That makes me a bit more comfortable with the direction it might be going if y'all actually got to get involved in the discussions/decisions(?) this time - still uneasy about it overall though, also especially since the NDAs mean we have no clue what sort of community discussion occurred. ¯\_(ツ)_/¯
I've not been closely involved with the process but I'm generally aware of stuff. There's good things in this feature - things that can bring dev rel teams to interact with devs directly on SO. And that's exciting because it potentially means we'll have more expertise participating in some tags. But I'm concerned about other things. The thing that I remember is that it's an MVP. So there's still a lot to do.
@hyper-neutrino monthly 1-1 sessions with the people who were participating to discuss the features and what the product would look like. Gave the participants the opportunity to voice concerns and guide the team.
Ah, cool. I still definitely wish there were some more public community discussion or even just an announcement beforehand and a chance to raise some concerns/questions instead of it just appearing - but as long as there was a good feedback system with some of the community members that's always better than nothing.
@Catija I see. There are definitely positives I think this can/will bring and I hope it'll mostly change in that direction. I definitely have some concerns too but it's not like the end of the world, it's just a precedent I'm not sure I like seeing but without any necessary harm done or benefit gained for now - we'll see and hope for the best :P
While it's not necessarily obvious, we really don't want to muck with the great parts of SO. We want to enhance them and make it even better. That's not necessarily going to mean that we'll get everything right the first time but there's room for us to change and grow. I think it would have been great to give a preview ahead of time but there's also a need for us to be able to get the first parts of a new product built. Much of the initial release is benefiting the clients by making it easier to access the tags they need to and have one place to see things that are relevant to their work.
@Catija Yeah, true. I can understand the decisions even if I strongly disagree with them; at least I can see some reasons for them. Again, nothing catastrophic :) many things I would rather hadn't happened but it's more of an "I'm a bit worried about this" than "this is already really bad"; it's not like that or anything.
TBH tag grouping / access seems like the main benefit and I see absolutely nothing wrong with that. (Also, thank you SE chat for showing the (see full text) thing, at least for me, and then not showing anything extra when I click it)
We have spent nearly a year actually working on this since it was first presented as an idea at our meetup in November 2019. I don't think we're generally planning to follow this process for many future projects but products (Teams, CoSO) tend to need to get an MVP built so that people can actually play with it and see what it does. Users are great for development and that's why we did work with some of the most in-tune and thoughtful people... but there's also the element of too many cooks in the kitchen.
And, well... who knows the actual impact. We can make guesses - and they can be well-informed and thoughtful... but we kinda need to try things sometimes to see what actually happens... even if it's just to prove that we were correct.
Anyway. If y'all have specific questions, I can try to answer them. Just let me know
Oh, so it's been a while then. And yeah, I totally understand needing an MVP. It's hard to talk about and raise concerns with something that doesn't exist after all :) and "people can play around with it" definitely doesn't seem something Teams has seen a shortage of, lol.
That's true; we can't really tell exactly how something will turn out if it's not tried beyond guessing, which no matter how educated, is still guessing.
@Catija Alright, will do :) Thanks for explaining some things more.
> Mullis won the 1993 Nobel Prize in Chemistry for development of the polymerase chain reaction ... and claimed that he once encountered a fluorescent raccoon that spoke with him.
Elevator sequence code-golf sequence grid
Totally not inspired by Lyxal repeatedly mentioning elevators in chat :P
Challenge
In short: simulate some people filling up an elevator and then leaving it in the following.
The elevator is simplified as a grid, where each person can occupy one cell of t...
It's quite unclear to the current standards, but IMO the way to go should be adding necessary details of the game Pong and its graphic parts, not unilaterally closing it
I honestly find Jelly easier to understand than APL and stack-based languages. Is this any indication about the language types? No, it just means I'm used to Jelly :P
> Tacit programming, also called point-free style, is a programming paradigm in which function definitions do not identify the arguments (or "points") on which they operate.
@PyGamer0 you arrange functions in a specific manner. This makes the interpreter look at the functions and assume where inputs should go. Then, the interpreter converts your code to what it assumes you want and executes it.
Input a non-empty array with \$n\$ positive integers. Test if the input array contains every integers in \$1\cdots n\$.
In case you prefer 0-indexed numbers, you may choice to input an array of non-negative integers, and test if the input array contains every integers in \$0\cdots (n-1)\$ instead...