🧭Curious how engineering teams are really handling software delivery today:
We’re doing a bit of market research for a project, and I’d love to hear from people working in software delivery, DevOps, or platform engineering.
If you have 3–4 minutes, we’d really appreciate your honest thoughts in this short, anonymous survey.
No sales pitch, no follow-ups just curiosity.
As a small thank you, we’ll share the overall findings with everyone who leaves their email at the end.
Here’s the link:
https://t.co/XDLt67KKGg
Thanks so much your input genuinely helps.
The 3rd edition of my book Deep Learning with Python is being printed right now, and will be in bookstores within 2 weeks. You can order it now from Amazon or from Manning.
This time, we're also releasing the whole thing as a 100% free website.
I don't care if it reduces book sales, I think it's the best deep learning intro around, and more people should be able to read it.
I have 12 years of experience and working as a Principal Engineer @Atlassian and I have seen concurrency scaring the hell out of a lot of junior engineers.
It’s one of the most feared topics in system design & backend interviews — race conditions, deadlocks, thread pools… you name it.
But once you internalize these 20 must-know concepts, everything clicks.
Save this thread. Read till the end.
Your future interviews and production systems will thank you.
Google DeepMind researcher argues that LLMs can never be conscious, not in 10 years or 100 years.
"Expecting an algorithmic description to instantiate the quality it maps is like expecting the mathematical formula of gravity to physically exert weight."
The AI industry discovered that fear sells better than features. “We can’t release this because it’s too powerful” is the most brilliant marketing strategy ever invented. You generate more hype by NOT releasing than by releasing.
You've been saying the same things since GPT-2:
• We can't release this
• We have god in a bottle
• We are all doomed
• This one is different fr
• AGI is here
• End of civilization next week
So spare me the grandiose speech, show us the model, and let people judge.
Rule of thumb for Concurrency Pattern selection In Go:
-> when you need to process data in stages, USE Pipeline
-> when you need to speed up a slow stage, USE Fan-In/Fan-Out
-> when you need to Limit Concurrent workers, USE Worker Pool or Semaphore
-> when you need to handle flaky services, USE Circuit Breaker
-> when you need to Cancel on done channel, USE Or-Done channel
-> when you need to Run tasks and get first error, USE Error Group
-> when you need to Add timeouts,
USE Context
-> when you need to Flatten nested channels, USE Bridge channel
-> when you need to Duplicate a stream, USE Tee channel
-> when you need to broadcast events,
USE Pub/Sub
If you want to understand Docker and Kubernetes networking, you need to know how computers talk on L2 (Ethernet).
Most of us have an idea of how TCP and IP work, and it's often enough. But setting up container networking or configuring Kubernetes CNIs requires deeper knowledge.
@naoshad2012 Biman’s digital payment initiative is impressive! With SCB’s support, transactions will be smoother, safer, and faster. Keep it up, Biman!
My laptop shut down suddenly yesterday! Tried everything—disassembled it, disconnected battery, RAM, SSD—but no luck. 6 hrs later, it powered on by itself. Felt helpless, no backup for important tasks