
#Azure / #dotnet / #serverless / #urdu
London / Delhi / Sydney
Joined May 2009
- Tweets5.1K
- Following747
- Followers323
- Likes2.2K
Ken Ross retweeted
New blog post: "Escaping the LLM Coding Rat Race"
There's only one winner in the AI coding rat race: your inference provider.
There is no permanent underclass. There is no
"falling behind."
It's brilliant marketing and it's ruining our lives.
aaronstannard.com/escaping-a…
Replying to @pierceboggan
@pierceboggan do you have any plans to make sharing skills, agents, prompts easier for teams working across lots of repositories?
Some great #dotnet skills in this repository 🙌
Hi @EmiratesSupport I'm trying to send a compliment through for a flight I took last Friday (first leg of a return flight). But your website says that my flight hasn't departed yet...I had a really standout experience with your Manchester check-in crew I want to share
Ken Ross retweeted
I like this take by @KentBeck on how AI-assisted programming changes the balance of which skills are most important

ALT So you can think really big thoughts and the leverage of having those big thoughts has just suddenly expanded enormously. I had this tweet two years ago where I said "90% of my skills just went to zero dollars and 10% of my skills just went up 1000x". And this is exactly what I'm talking about - having a vision, being able to set milestones towards that vision, keeping track of a design to maintain or control the levels of complexity as you go forward. Those are hugely leveraged skills now compared to knowing where to put the amperands and the stars and the brackets in Rust. — Kent Beck, interview with Gergely Orosz
Both of these extremes suck
Kill your ego, even if it hurts.
Been married to this beautiful woman for 15 years today. Yes I’m a catch now but I have no idea what she saw in me 22 years ago.
People keep asking for tips and advice so here are 15 pieces of advice so you too can have a long happy marriage:
1. don’t
2. be
3. dicks
4. to
5. each
6. other
7. it’s
8. not
9. a
10. competition
11. you
12. are
13. on
14. the
bonus:
15. same
16. team
@davidfowl is there a better way to do the bits highlighted in yellow? this was the best I could come up with (it works and is turned into valid bicep), but feels incredibly awkward and is one renaming away from not working...
Ken Ross retweeted
We just shipped aspire 9.1!
Lots of reliability fixes and new features!
learn.microsoft.com/en-us/do…
#dotnet #aspire
Yes 💯 Devs find it hard to break the habit...a bit like SCRUM all these abstractions make people feel safe
Do we have an over-abstraction issue in #dotnet?
Ken Ross retweeted
Had a customer just demo an @AkkaDotNET -Streams based application responsible for migrating 1 trillion+ SQL rows from one instance to another - "works great!"
The streams code itself was like, maybe 25 lines
My personal brand at $currentJob is asking the question, "what's the point [of doing x]?"
Do you bristle when someone advises you to build a "personal brand"?
Look, you don't have to create a meme coin or hand out stickers with your face on it. No psycho stuff.
But there's value in authentically sharing more in public.
@InfoQ story: infoq.com/news/2025/01/softw…
#akkanet and Microsoft #orleans, a good fit for Programmable Voice? In the post I cover some of basics of using these two Actor frameworks to control Azure Communication Services voice calls
#dotnet #azure #programmablevoice
unravelled.dev/akka-and-micr…
Well...that was interesting @Aaronontheweb
I managed to get the FSM actor working, like I said in the previous thread the syntax and programming model is awkward...but it worked.
I then took a look at using a ReceivingActor, I liked how the Receive method was type safe...
Tomorrow I'm going to take #akkanet for a spin, been waiting ages for a decent use case and now have one. Last week I built a state machine system for controlling #azurecommsservice phone calls, going to try and replicate it with Actors instead of state machines @Aaronontheweb
it was obvious how to integrate with Aspnet/minimal APIs. However the way Grains are written and the "state" i.e. I'm in the state WaitingForResponse or xyz wasn't as neatly expressed, i.e. Become was much nicer here compared to Orleans













