Story points are unique to the team that is doing the work. Basically, a 21 point story for me could be a 3 point story for you.
In of themselves, the points are not important. Just size the stories to some amount of points that is reasonable and then do a sprint. The objective is to get a sense of how much work can be done in a sprint, to help create forecasts of when work will be completed.
At this point, it's the JVM that is the real value, not the language itself. It would be better if they started to emphasize that more.
Faster moving, slimmer cartridges are more accurate than their fatter analogues of similar energies. I’m not entirely sure of the sciences behind it, but it is a trend I’ve noticed.
This is bad science.
MSYS2 has support for GTK, since I think the windows installer for git (which uses MSYS2) would include GUI tools built with GTK
They don't care.
That's a real bummer because lots of my clothes are synthetic fabrics and I really like them compared to cotton. Sigh.
That was always the thing I was wondering about. Where was the origin of these microplastics. Surely it wasn't all just those little beads that were in soap and shampoo
How do you define a troll? Anyone who disagrees with you?
MODS HELP I'M SEEING PEOPLE WITH DIFFERENT OPINIONS ON MY FEDERATED WEBSITE WHERE PEOPLE COMMENT ABOUT NEWS STORIES
Tons of Ukrainian political parties were outlawed when they declared martial law, so the elections would be a sham
I have no actual argument so I'll just say Russians are going to rape your mom
brigading is when people disagree with me on a site where people post news articles and everyone posts their opinion
Guess SBF should have spent his time not intimidating/tampering witnesses, if he needed the Internet for his defense preparation
What is a "full stack"
My problem is that there are a lot of layers beyond just the "front end, web/REST, database" layers that most people refer to, that are involved with delivering an application.
Like, do you know Angular and also BGP?
Probably not. So, it's impossible to truly be "full stack" so you're going need to actually define what everyone is supposed to be responsible for knowing, and also recognize that there are going to be folks that are strong in some areas and other areas less so. Plan accordingly
I've been using ConcourseCI because another team manages it and it is integrates with Hashicorp vault.
It's good. The big advantage is I don't have to deal with maintaining it.
The downside is their story on GitHub integration is kind of crummy, you have to create your own web hooks because our ConcourseCI instance is too busy for poll based resource checks.
I think it's YAML.
I'm not happy that it's YAML but it's become ubiquitous. Sure, there are lots of other formats that others have mentioned, but I'm sorry most of them are positioned as "it's better than YAML!" and the fact that everyone is mentioning YAML, even if it's about the things it does wrong (and boy does it do things wrong) still means that YAML is on everyone's mind.
It's very important, so that everyone knows that they are talking about the same thing.
Like, everyone needs to just agree to use the same term, while also not getting into bike shedding around which term to choose.