Love the idea, I immediately went to grok (testing for work) and asked it to give me a few placeholder paragraphs in WG's style:
"The street pulsed with a neon hum, data streams threading through the air like ghost veins in a concrete jungle. Holographic hawkers flickered at the edges of vision, their pitches fragmented by the static of black-market neural rigs. She moved through the crowd, her optic implants slicing through the visual noise, parsing faces for tells of corporate loyalty or freelance desperation. Every step was a negotiation with the city's rhythm, a dance of survival where the wrong move could flatline you in a datastream dead-end.
In the shadow of a megacorp tower, its glass skin reflecting a fractured sky, the air smelled of ozone and recycled dreams. He jacked into a public terminal, his fingers dancing over a haptic deck scarred with use, pulling fragments of encrypted chatter from the dark pools of the net. The data was alive, slippery, coded in dialects of machine and man, whispering secrets of a deal gone sour in some offshore server farm. Trust was a currency nobody carried anymore, not when every connection could be a trojan horse.
She crouched in the alley, her smartcoat shimmering to match the graffiti-smeared wall behind her. The drone overhead was a cheap model, its sensors blind to her cloaking, but she didn’t trust it to stay that way. Tech evolved fast here, and yesterday’s edge was tomorrow’s obsolescence. Her neural feed buzzed with alerts—proximity warnings, encrypted pings from a contact she hadn’t seen since the Osaka run. The city didn’t sleep, and neither did its ghosts, their voices woven into the code that kept this sprawl alive."
To be fair to AWS, they do work really hard to (at least at an account level) to optimize workloads with you. They do this so overall you'll move more workloads to them.
its quite simple, if workload x can be done 100% cheaper on-prem then its an obvious move (probably) if AWS manage to get that closer to 30-40% then the operational benefits of using AWS make more sense, more workloads, more total spend.
> -There is a semi-obfuscated IP tracker in index.html
you mean that counter script, it wouldn't expose anymore information than a basic access log, I would assume it just makes it marginally easier to see which of his subdomains are popular.
Not all requests are created equally, maybe you don't check jwt revocation on some high throughput read endpoints but on updates or reading of sensitive data you do check that list.
with JWTs you have the flexibility with the opaque you don't.
JWTs also allow you to do client-side logic on things like entitlements but then verify against database when the user tries to view something
Add on to that developers that use Dependabot or Renovate to automatically merge PRs with minor version bumps to "ensure the latest security patches are applied"
In my car when spotify is playing through carplay I get a nice album art on my screen and between my dials, it also uses the colour as a blurred background effect, quite nice and makes me appreciate the art even if i'm (hopefully) not directly looking at it.
I am in the same industry and we have the same problem. We are moving to having "insecure" proxies that support TLS 1.1 for devices that can't update. It won't add much security but at least demonstrates its was an active decsion to support it rather than a config mistake.
"The eagerness to kill Stars and Stripes is hard to fathom. As the senators note in their letter to Esper, the $15.5 million saved by eliminating the newspaper’s subsidy would have a “negligible impact” on the Pentagon’s $700 billion budget."
In some spaces it is required to split out the backend from frontends. We support nearly 100 different native devices (web, mobile, tv, stb) there is no way you could have a team own a feature from end to end, without having huge teams with very shallow domain knowledge.
Really looking forward to trying this out. I get K8s is the bees knees and everything but we have an ECS history that will take time to migrate to K8s. I'm glad to see a modern service mesh not just targeting the collective
I agree, I have Android Auto in my 2019 VW Tiguan. Its awesome but its very easy to spend more time than you think picking a playlist from spotify etc.
With your phone you know not to touch it when driving but the center console feels acceptable.
I had one close call where the car's auto breaking saved me from hitting a car that decided to turn without indicating. now I treat my centre console almost like my phone, I will use the console stopped at lights but not my phone.
Where I work we spend millions per month on AWS, its our primary cloud platform.
At that scale the UI of the console really doesn't matter, everything is IAC so developers rarely need to directly access AWS. The one thing we do use is the Cost and Usage explorer which has a reasonable UI
Although I agree in principle one other aspect that becomes critical in high volume systems is efficiency.
Logging is generally a text stream and in production should only be warning+ levels (imo) so the impact on performance is negligible and really only when something is going wrong.
I want metrics all of the time, potentially 10 or 20 metrics per request/action, a high performance, low network method for sending those metrics with low latency is critical.
We need both systems and both should be treated as tier 1 systems within an organisation. I don't think pushing metrics into a log stream is a scalable architecture.
For me I have always found the best projects to work on are Developer Experience projects.
In most companies its hard to dedicate the time to DevEx but as a manager I can rock out a few features for our cli in a couple hours. If i'm delayed it doesn't really hurt the status quo but when I succeed my developers love it because I make their lives easier (the (almost) entire point of being a manager). It scratches the coding itch too although I have lost many evening and weekends getting carried away.
"The street pulsed with a neon hum, data streams threading through the air like ghost veins in a concrete jungle. Holographic hawkers flickered at the edges of vision, their pitches fragmented by the static of black-market neural rigs. She moved through the crowd, her optic implants slicing through the visual noise, parsing faces for tells of corporate loyalty or freelance desperation. Every step was a negotiation with the city's rhythm, a dance of survival where the wrong move could flatline you in a datastream dead-end.
In the shadow of a megacorp tower, its glass skin reflecting a fractured sky, the air smelled of ozone and recycled dreams. He jacked into a public terminal, his fingers dancing over a haptic deck scarred with use, pulling fragments of encrypted chatter from the dark pools of the net. The data was alive, slippery, coded in dialects of machine and man, whispering secrets of a deal gone sour in some offshore server farm. Trust was a currency nobody carried anymore, not when every connection could be a trojan horse.
She crouched in the alley, her smartcoat shimmering to match the graffiti-smeared wall behind her. The drone overhead was a cheap model, its sensors blind to her cloaking, but she didn’t trust it to stay that way. Tech evolved fast here, and yesterday’s edge was tomorrow’s obsolescence. Her neural feed buzzed with alerts—proximity warnings, encrypted pings from a contact she hadn’t seen since the Osaka run. The city didn’t sleep, and neither did its ghosts, their voices woven into the code that kept this sprawl alive."