I asked it to translate 'meeting agreements' to Dutch and it came up with the word 'bijeenkomstafspraken', which is a valid but very uncommon Dutch word (I'm native Dutch and don't think I've seen it before). If I throw it into google with quotes around it, the first page is results with 'bijeenkomst afspraken', where 'afspraken' is used as the past tense of 'afspreken' (to agree) instead of as its noun (agreements).
It btw also suggested 'vergaderafspraken' as a translation, which is a way more common word.
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.
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.
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.
Have you seen how meta does business?! Talk about a straight up evil corporation.
They don't know how to play nice. They have no interest in playing nice. They're out to make as much money, whatever it takes. They either buy their competitors or try to kill them. The fediverse is not for sale and we need to keep a healthy distance so they don't get a chance to kill us.
I'm not surprised at all. Bird flu has gone form a major to a massive problem in the last year. We just had to wait for it to mutate and infect mamals regularly (it already happened every now and then).
A few days ago there was also news about cats in Poland being infected. It already infects humans sometimes. No human to human infections yet, but I guess with a strain that's mamal compatible, it will come sooner or later (probably sooner).
This is what happens when you put a shit ton of animals in cages together. It will not become better until we find our place in the ecology again, instead of believing we live outside it. This doesn't just apply to infectious diseases.
It's a bit surprising that the virus hasn't mutated enough to infect more people and eventually spread from human to human, given that in e.g. the Netherlands there is no bird flu season anymore, but that it infects birds year round. Earlier this month they finally ended the requirement that birds had to be locked up, after almost 9 months! That's the longest lock up period ever. (They also killed millions of chickens and such in an attempt to prevent spreading of the flu.)
Doesn't mean that this won't become the next pandemic. It sounds quite likely given this news. Cats are mamals and they're also spending a lot of time around humans.
Given how evil they are, this definitely seems plausible (although threats isn't available in the EU and they are actively preventing usage in the EU). Another option is that they're still out to kill the fediverse. That one honestly seems more likely to me, given how they've acted in the past (buying up platforms before they could outcompete them).
I started a little over half a year ago with Go, coming from Python like the author. I definitely enjoy working in a strongly typed language and Go is usually quite fun to work with. This week I'm actually implementing a concurrency pattern for a 'real' problem, so eager to see how that works irl. I've yet to come across something where generics really make sense, but definitely curious to explore that with a real case as well.
I once calculated that if we reduce the land use for livestock by 50% and then use 10% of the newly freed land to build housing (the other 40% can become nature), we can build a city something like 1.5x times the size of Amsterdam, the largest city in the Netherlands.
It's not a lack of land. It's how the land is being used. Almost half is for livestock (or more accurate: to dump the shit of that livestock, as the majority of the animals is kept indoors).
When smart watches came about I thought it would be cool to be able to look at your watch when a notification comes in. Never ended up buying one and when I see how some people behave, I'm glad I never did. Some people will just glance mid conversation at their smart watch, which imo is just as bad as grabbing your phone mid conversation.
I'm happy with my cheap Casio. Looks heaps better too.
I work in IT and we have truly self steering teams without formal hierarchy. Not everyone is used to it and IT people can be interesting characters, so it's quite a process to get the team to perform well.
This would also be my advice. Aeropress has been my daily driver for many years. Such a simple satisfying process (especially ejecting the coffee puck), forgiving in nature and a really smooth cup of coffee. It's also extremely sturdy: I still use an old version with the blue markings.
My recipe is slightly different. I stopped doing the inverted method, as it felt clunky and caused a mess once. Didn't notice a change in flavor.
My recipe for light roasts:
Boil water to 100c.
Grind 15g of coffee quite fine (I have the Wilfa Svart and I usually go a few notches finer than its Aeropress setting). Feel free to start with preground coffee, but get it at a place where they grind it for you when you buy it (they'll ask which brew method you use, so they can adjust the coarseness). Make a cup the same day you bought it so you get the full flavor. Notice how the flavors deteriorate over time. This is when you probably want to get a grinder. When I was on a budget, I used a manual Hario.
Set Aeropress on a cup, add coffee and 200ml of water right when it's done boiling.
Stir a bit to let any clumps fall apart and let it brew for 2 and half minutes.
Slightly swirl the cup with the Aeropress on top of it, like you'd do with a wine glass. This settles the bed of coffee evenly according to James Hoffman.
Press, remove coffee puck, rinse the Aeropress parts and enjoy your coffee.
Light roasts are great with boiling water. Darker roasts are better with ~90c water. I rarely drink dark roasts, although recently I had a light to medium roast with an interesting flavor profile.
15g to 200ml seems to be my sweet spot for most coffees. I do experiment with the grind settings and brew time when I get new coffee, but my starting point is the recipe above.
Looks like it does: https://chat.openai.com/share/1b487711-c1be-468a-877b-98091449b55e
I asked it to translate 'meeting agreements' to Dutch and it came up with the word 'bijeenkomstafspraken', which is a valid but very uncommon Dutch word (I'm native Dutch and don't think I've seen it before). If I throw it into google with quotes around it, the first page is results with 'bijeenkomst afspraken', where 'afspraken' is used as the past tense of 'afspreken' (to agree) instead of as its noun (agreements).
It btw also suggested 'vergaderafspraken' as a translation, which is a way more common word.