jochem
This part made me genuinely tear up.
ChatGPT speaks other languages. It's actually a really good translator.
I just asked it to describe an organization using UK English and it indeed used 'organisation' instead (didn't check for other words).
Try to get each test done as early as possible. Even when a feature is not fully finished yet, parts can probably already get tested.
Other than that I would focus on test automation. Very few tests should require manual work. Both your devs and QA engineers should work on this. Devs develop unit tests and component tests, QA is more focused on integration and end-to-end (this is not a hard rule, I currently work in a team where QA only does end-to-end). Of these only end-to-end typically requires some manual testing work, but by then almost all defects have already been found, so it rarely leads to blockers.
With test automation you can run your tests all the time and get much quicker feedback. Your devs don't have to wait till Tuesday to hear if things are ok and certainly don't have to wait another day for QA to finish testing.
This is literally the critique on waterfall (project goes and makes what they believe the customer want, comes back months or years later, turns out they made the wrong thing and wasted so much time) and what agile aims to solve (have regular check in moments to see if the project is still on the right track and adjust when needed).
In my experience it helps to define a roadmap and stick with that direction. Figure out the details when you start working on a roadmap item. Adjust the roadmap every 6 months or so, only deviate earlier when the situation calls for it. This requires sometimes being able to say 'no' to your customer and them accepting it.
For those considering visiting Venice: stay a night or two! As you can see, only 27% of the tourist stay for a night. In the evening it's really nice to walk around and enjoy the peace and quiet of no cars. Of course you're not alone, it's a popular city, but it's completely different from the day.
I live in Amsterdam since 2012 and visited often before. Tourism has increased massively. You might remember having tourist season, where it got busy over the summer, but outside of it it wasn't too crazy. These days it's tourist season year round. With them comes stupid tourist shops (nutella shops were all the rage, now it's candy shops).
The amount of people getting on cheap flights and then absolutely fucked up in the city center is saddening. The red light district has been shrunk by closing many windows, so these people now congregate in only a few streets around the oude kerk. On the weekend you could walk over their heads. Next step the city wants to take is close the red light district completely and move the prostitution to an 'erotic center'. None of the stadsdelen want it in their part of town, so I doubt it will be successful. I think it's also ridiculous to kill such a historic part of the city (prostitution on the Wallen is happening continuously since the 15th century).
Outside of the city center the city still has great spirit. Hardly any tourists and still plenty of excitement to be had. Of course the city keeps developing, for better and for worse (housing crisis is hitting hard), but this is the nature of almost all living cities. I really enjoy living here, although I rarely visit the city center anymore. I have everything I want in Noord, where it's much more down to earth and mellow.
I exclusively use Lemmy via voyager.
Markdown is notoriously understandized, so there are lots of unofficial extensions. This is a major downside of markdown, as you cannot trust a renderer to properly show the formatting beyond the basics.
It's still really nice, because of two great features:
- it's super easy to learn. Just look at a few examples and off you go.
- even when it's not rendered, it's still easy to read (which I think contributes to making it easy to learn).
If I would guess, then it has to do with making long lines fit in a window without requiring horizontal scrolling.
Markdown is used a lot in the context of software development. Software code is usually accompanied by a readme, detailing what it does, how to setup your environment for development, how to contribute, etc.
The defacto standard is to write this in markdown. Since it's written in a software development program (an IDE), you don't have text wrapping, meaning lines continue when they don't fit in the window. This is because otherwise the code becomes unreadable. Most code can also be kept to fairly short lines, normally not requiring any horizontal scrolling. However, a long sentence in a readme will easily become much longer than a line of code. So being able to break a line anywhere without having an actual line break in your rendered output is super useful for that.
This is btw how html also behaves. Markdown gets rendered to html.
It's both.
Enough people need to reduce meat consumption and realize there are alternatives (and make it interesting to innovate alternatives for meat – just look at the explosion of alternatives over the last five years). They also contribute to creating awareness around this subject, influencing others to change or at least consider changing their behaviour.
Because in the end you need enough support to enact changes such as a meat tax. This has been tried in the Netherlands, but there still isn't sufficient support to introduce this.
Unpopular opinion: we shouldn't be sending more murder machines to a war. All it will do is kill more people in name of some power struggle that should not concern them.
Ukraine has also received and used cluster munitions, which is really bad. I remember that there was a lot of outrage when Assad used them in Syria. Now that it's the West, media just glances over the fact that these munitions cause so much civilian death or even support the usage, regardless of how awful they are.