One of the products my employer builds is used twice a year. People pay tens of thousands of dollars for the privilege of using it twice a year. It's tremendously valuable to be used twice a year.
I think the supply shocks is the part of the pro-natalist view that is hardest for me to accept.
My counter-argument: the full expression of human achievement is not genetic; it depends on the resources given to the human; If we accept that someone cannot reach their entire potential if living in poverty, and we accept that a lot of the advantages of rich children are due to the environment and opportunities that wealth provides, then it naturally concludes that we could get all of the advantages that pro-natalists look for by creating a higher standard living for all existing children.
Only when we can provide the sustainable resources for all people on the planet can we accept the idea that we have room for more.
I guess I'm pro-natalist. I do agree with you on the goal of eradicating poverty, although to me that's a goal in itself that does not need to be justified.
But I don't agree that all people on earth are fungible, and a birth in Mongolia is the same as a birth is Sydney, Australia.
Your "human achievement" viewpoint is highly reductive. The culture of a place is maintained by it's local population. When you have a low birth rate situation to the point that you need to supplement the workforce with immigrants, that signifies that the local culture is slowly dying. While some mixing of cultures is beneficial, we should also try to perserve our local cultures. We should not turn every city in the developed world into a little NYC.
Because you see the IC side of the Atlassian toolkit. The management side is much more expansive and this starts mattering when you are coordinating larger projects.
That said, if you are a smaller company, you absolutely could kill Jira pretty quick.
The frustrating thing is I also thought about this as a natural conclusion - but as a natural workflow that corporations will do when they see AGPL dependencies they want to use. (I also think there's a world where we start tightening our software bill of materials anyway.)
I do not believe it will ever again make sense to build open source for business. the era of OSS as a business model will be very limited going forward. As sad and frustrating as it is, we did it to ourselves.
I mean, this is a task board and not a Kanban board - Kanban implies things like Work In Progress limits, continuous improvement, and measuring flow to get rid of blockers.
But you're right - you can visualize your workflow without using Kanban - I think it's weird how the term gets appropriated here.
People tried reinventing terminals, SSH, and tmux for phones. It's a pretty terrible experience using your thumbs. And it takes significant know-how to set up.
And in modern stacks, it almost necessitates a man in the middle - tailscale is common but it's still a central provider. So is it really the most inefficient way possible?
The cost of those remaining maintenance items are the issue. That said, it's a reasonable hypothesis to say that this is an economies of scale issue.
(Also, as I understand it, tires are used up more quickly on EVs still, but tire companies are learning to adapt to EVs so that may not be as true today.)
I heard a story from someone whose relative was in the Korean War - apparently people manning radar stations used to warm up by getting in between some microwaves. I just looked it up and the danger isn't cancer - but you stay too long you can get unexpectedly cooked (particularly eyes) because your body isn't detecting being warmed up like that.
My Grandfather was around in the early days, had a ham call sign from the early 1930s and was involved in the Manhattan Project as a senior non-scientific engineer.
He was also involved in the development of radar/microwave comms after the war.
He and colleagues did the same - warming their hands in front of microwave antennae.
He developed and later died of some unknown neurological issues related to nerve transmission in the early 1990s.
He had been exposed to so many different possible dangers that it's impossible to tell.
After he died I helped clean out and save/donate the double-garage full of ham equipment and home-built telescopes - one was ~.75metre diameter and ~3 metres long, just huge - I was just a teen and let most of it go as my grandmother didn't care by then.
There were also many containers of classified documents, related to WWII and after. Those were appropriately dealt with.
I've always HAD microwaves but have been aware of the issues.
I'm a ham as well and still occasionally use the morse key he gave me when I was 7. Still miss him, he taught me so much.
> According to legend, one day while building magnetrons, Spencer was standing in front of an active radar set when he noticed the candy bar he had in his pocket melted. Spencer was not the first to notice this phenomenon, but he was the first to investigate it. He decided to experiment using food, including popcorn kernels, which became the world's first microwaved popcorn. In another experiment, an egg was placed in a tea kettle, and the magnetron was placed directly above it. The result was the egg exploding in the face of one of his co-workers, who was looking in the kettle to observe. Spencer then created the first true microwave oven by attaching a high-density electromagnetic field generator to an enclosed metal box. The magnetron emitted microwaves into the metal box blocking any escape and allowing for controlled and safe experimentation. He then placed various food items in the box, while observing the effects and monitoring temperatures. There are no credible primary sources that verify this story.
Value and use are not always synonymous.
reply