144 karma · joined June 4, 2019
Interestingly the English explanation is much more ambiguous than the Dutch:
"These officials [police] may not ask to see proof of identity without giving a reason. " https://www.government.nl/topics/identification-documents/co...
Whereas in the Dutch version:
"De politie mag alleen uw identificatiebewijs vragen als daar een goede reden voor is." Translation: "The police may only ask for your identification if there's a good reason to do so" Typical.
I would lodge a complaint: https://www.politie.nl/onderwerpen/klacht-over-de-politie-in... (page in Dutch)
But hey, I like boring things ;-)
All the above depends on the tool that's used. I've set up many sites that had page builder features but didn't have these drawbacks. Certainly there's many other tools out there. What OP seems to be talking about are page builders that output and store raw html.
> There’s always a missing feature (page builders cannot solve all your problems).
True, but that goes for literally anything you can use to build websites, all the way down to the HTML spec. And extending the page builder is often possible with professional help.
> Getting to know page builder doesn’t make you a developer (leave the job to a professional).
Developers are not by definition a professional in all aspects of page creation. A user well versed in, say, WordPress, will know about the drawbacks as well, and know how to mitigate them.
I'm not a big fan of page builders myself, but there's a place and time for these tools. I'm currently working with a team to implement a 1.000 page website in contentful and react, based on similar thinking as OP. It's an absolute shit show and it feels like being the hostage of 'professional developers'.
In the end the most important is to choose the right tool for the job, and there's a place for these page builders.
"But why did it fail? How does a $35 million rebranding project fail?"
But because we want to do scrum or agile ‘properly’ we need estimates.
The Scrum guide only mentions sizing as a responsibility of developers, not how it's sized.As a developer that moved to product owner I've seen both sides of the coin and certainly had my share of "estimate theatre". For me the most important consideration now is predictability of being able to deliver value, to support my communication with upper management, clients and stakeholders. I do need to have an understanding of what's complex, uncertain or will take a lot of time, so I can weigh it against other priorities and I rely on the developers to provide me those insights. I don't believe this predictability comes from having perfect estimates, it comes from knowing how much can typically be achieved by the team and the trust the team has in it's own abilities. User stories of course need enough detail to know what needs to be done, but I disagree that you'd need to "do the work to know how long it takes".
The problem described in this blog is very recognizable, but I suspect it's foremost a problem of "management" trying to control things.
I've been a Drupal developer for 15 years and started using it for it's low code abilities. In my opinion it still is an amazing low code platform which is extremely versatile. If you really need to customize, it's all there under the hood to hook into, override and extend.
The quote comes from the official Scrum guide. I'd say that is an authoritative source (just like yours, mind). I was just pointing out that according to 'the bible' you have to incorporate the framework as a whole, or not call what you're doing Scrum (Scrumbut perhaps?).
I agree with you on the commercialism surrounding Scrum and the financial incentive.
From the perspective of Scrum this is incorrect. It is specifically stated that:
> Changing the core design or ideas of Scrum, leaving out elements, or not following the rules of Scrum, covers up problems and limits the benefits of Scrum, potentially even rendering it useless. [1]
Eg. If you don't follow the framework, you're not doing Scrum
If I may, how do you ensure you're only getting one or two cards per book? Do you create a deck per book, or is all in one deck and there's some trickery in the review settings you do?
Additionally, it's really interesting to me that there is a non-linear approach for the reviewing, what's the impact on your enjoyment of books? And, does this approach give you better retainment of details?
Finally, is the length of text set, and how did you determine what it should be?
Sorry for the interrogation
In my personal observation, working in a cross functional team which includes frontend and backend developers, and ui/ux designers, an MVP only consisting of functionality just wouldn't be considered. Perhaps the author is used to environments where those disciplines are siloed.