struppi
Joined 15 years ago
Joined 15 years ago
More performant? Maybe - at least multithreading, fork/join, ... would be easier.
Smaller binaries? No, probably even larger, since the chromium embedded framework (CEF) is biiig. But it would probably be possible to add other HTML renderers later (i.e. CEF during development b/c of the excellent debugging features, JavaFX WebView later).
It would make most sense when you either need multi-threading or have existing Java libraries/code you want to re-use or have mostly Java developers...
But one could probably add other HTML renderers too (Android, JavaFX WebView, ...).
My goal was to use java-cef, but hide all the weirdness.
Also, there's no pre-defined data binding, so a bit less opinionated in this case.
Train: Go to the station (near city center), arrive 10 mins before train departs, get on the train, read/work/eat/drink for 6 hours, get off the train. And then you are already at the city center of your destination!
The total time spent when flying might be shorter (4.5-5 hours), but that is not worth the hassle.
The coverage, all from Blue-aligned media, largely presented Mastodon as a cool new alternative to Twitter that would be free of "harassment," which is a Blue code word for the mere existence of the Red side.
This is clearly not from a neutral person. He very clearly picked a side.
Then we thought about what might happen when we have a violation (endless discussions about whether that was actually a real violation and whether our response was justified, maybe even within the team).
So, we sat down and wrote a slightly longer version, which tries to spell out some unwanted behaviour and some guidlines for conference stuff ( http://socrates-conference.at/code-of-conduct/ ).
We also wanted to explain why we have the CoC in the first place and how we'd like people to behave. It surely is not perfect (probably too long and too short at the same time).
But if you think "don't be a dick to other people" would suffice as a CoC, imagine you are the organizer of an event, and then try to list all the things that might go wrong. Be creative - I'm sure you can imagine situations where it does not suffice.
e.g. Sebastian Kurz, a few days ago (1): "The American President is unconventional and American politics has become unpredictable. [...] This is a challenging geopolitical situation."
(1) German Interview - https://derstandard.at/2000081642343/Kanzler-Kurz-Wer-auf-Or...
And there are other organizations who can make any agile method work for them.
So, it's not really Scrum's fault when it fails (at least not always). And it's not really (or not only) Scrum's achievement when it succeeds.
As a friend of mine, Samir Talwar, once said: "To be good at software development, you need an organization that's optimized for software development. Most organizations are optimized for something else."
Anyway, if you implement a process, but ignore even the very short (22 pages) guide that summarizes the process, but instead cherry-pick what you think will work well in your org, then don't blame the process when it does not work.
As I wrote in my book: "But changing Scrum so it works within your company will not make you more agile – It will make Scrum less agile!"
I wrote a whole book about "Agile Anti-Patterns" [3]. Most of the book's content is about things that many companies get wrong when they start with agile or lean software development. Because it is very easy to get those things wrong.
Yes, those problems are extremely common. Not only with Scrum - Organizations also face those problems when they try Kanban or SAFe or whatever. Because, change in a traditional organization is hard. And to really implement Scrum, you'd probably need to change more about the organization than the org was willing to change.
But those problems are not Scrum's fault. If the team has no power, it is also not truly self-organized. And the Scrum Master is not doing their job.
You could start to improve by creating awareness about the problems. Blaming Scrum may or may not be a good idea to do that - Because, some people in your org may be invested in Scrum. Some mentoring or coaching for your Scrum Masters, Product Owners and developers and managers might be a better start.
[1] https://www.davidtanzer.net/david%27s%20blog/2014/03/26/no-t...
[2] https://ronjeffries.com/articles/018-01ff/hills-to-die-on/
Find out more about me at http://davidtanzer.net Twitter: https://twitter.com/dtanzer Email: [email protected]