I’m in the Pacific Northwest. I wonder if we got lucky on this or just some areas got unlucky.
246 karma · joined June 6, 2020
I’m in the Pacific Northwest. I wonder if we got lucky on this or just some areas got unlucky.
The rest of apple's email landscape sucks. It is pretty poor at managing spam, the client is terrible, it doesn't sync rules between the desktop app, icloud email, and iphone.
I hate email in general. It is getting to be 1 in a 100 type scenario of anything of value and likely worse if I knew all the emails that were deleted before I saw them.
I'm just amazed though how well they nailed the sound of it all. The back and forth, the layer of one speaking over another at the right time, each sounding like your average podcast host in that light style. But the content sucked.
Scaling the number of messages is no longer an issue for us using SQS but size is. Basically there are still constraints. We then need to pass references. “Details created etc find it here”. On prem we could dump around 25 MB into message without issue and could go to 50 MB but it wasn’t safe.
I get your point on the queue and pub/sub not being the same. Just to note we do a lot of hybrid and expect others do to. Publish to a topic and bridge to queues. Fan out is easy and gives choice. I don’t know google’s version, with TIBCO EMS this was easy to manage and was clear to everyone. If you wanted to listen to everything on prod.alerts.* you could or if you want to process prod.alerts.devices.headend you could just queue it and process all.
We use queues like storage for long outages so that senders don’t have to change anything. Not a great use but people were sure happy to know we could help by holding all the events while they could deal with their mess. Never got close to any limit when doing this on prem.
Never used it but isn’t the idea of Kafka to hold all events like a database? Love the idea. Seems so lazy and useful at the same time. Now that I write this I can see the danger too. You become a transaction system of record. Ugh. That’s someone else’s problem ;).
What we liked about it was the ability to contextualize events by keeping a history and relationship between objects and events that we could reference as part of our rules. Particularly when we get an event storm and putting more signal into situational awareness when there is a lot of noise.
"China hasn’t yet proven the superiority of its system, but its successes raise the uncomfortable question: Can this be what wins? Can universal surveillance, speech control, suppression of religion and minorities, and economic command and control really be the keys to national power and stability in the 21st century? How could that be true, when those same things failed so comprehensively in the 20th?. . . it’s useful and to think about how and why totalitarianism might be well-adapted to the world of the 21st century. In fact, I have a theory of how this might be true. This theory is only a conjecture — *it’s something I don’t believe in*, but also something I can’t yet convince myself is wrong."
By the end of it I don't really get what this article is trying say. The first 2/3rds is about all the shiny things China has and people like it because they don't see the dumpster fire in the alley that made it all happen.
If one was concerned about the direction of liberal democracies outside of the West, India would be a more interesting place to look.
It is one of the few (only) diagram types that is easy to draw and fairly close to the real world implementation. Most other formal approaches are wonky abstractions that only true practitioners can make sense of.
https://nationalpost.com/opinion/colby-cosh-where-theres-smo...
(Tried to find a link to the definition of shitweb, wow not a great search)
Better or worse, I don't care, but it was a lot different. I could see people caring about the Oscars more in the past because there was a commitment beyond the couch. You couldn't normally see an Oscar nominated movie unless you got to a theatre. I can see the Oscars becoming a footnote pretty soon.
I've been listening to The Video Archives podcast and really enjoy the analysis and movie lore. It will be interesting to see how this present generation of movies gets analyzed and the stories they generate.
I've seen this decoupling argument used in Canada a lot. It doesn't work very well there. The country is still completely dependent on the US market. They've tried Europe, Asia Pacific, and China, with a minimal budge in its current dependency. The disruption and economic pain are too high to force it in to existence and would be political suicide. Maybe the an authoritarian and central planning model can get over that in China? If the current internal investment inefficiencies are any clue, I would say no.
All the promises of the power of these platforms was lost in the additional effort in managing the complexities. Developer productivity for the work that I've been doing is way more important than hw/sw costs. I can't think of anytime that this trade worked better where I had more focus on the sw/hw costs rather than developer time.
I didn't get it either. I thought it just looks like SQL with some complicated additions. Then I did some work with it and the flow got way better. We could work a lot more incrementally and as a larger team rather than as individuals tripping all over each other. Maybe there is a better way doing something else, but this clicked with the team.
Not sure I get your cost centre black hole comment, but for the most part storage is so cheap that it isn't a concern. ELT has made it pretty easy for us to do less analysis and work on the data gathering side, which is low value, and do more on the modeling side which is higher value. Further, analysts can play with the raw data and find what they want and if they like it they will give it to us to model in a formal way. No need to work with an ETL team and application team to bring the data over. In ye olden times, this was overthought and created friction - "If you don't know what you're going to exactly do with the data how am I going to know what to bring in and how to land it"."But how am I to know what to do with the data if I can't query it and see what opportunities there are."
On the unwieldy part, sounds like you've had a bad experience. Ours has been the opposite. Really easy to setup and use. Easy incremental step for the team to get their heads around. Integration with git and snowflake was really easy. I'm still a bit worried that something is going to get really messed up with the declarative approach that dbt has, but we've not seen any issues yet.
I've been curious as well about what more can be done to make the development lifecycle better. Most of the other "big data" approaches that I've worked with seemed to make it worse not better. A lot more complexity, not thinking in sets, layers and layers of nothing I care about that can go wrong. I can't believe I'm still working with SQL.