←
Khurram533 posts
Khurram avatar

Khurram

@khurram

engineer by profession, artist by heart

◷ Joined April 2007▧ 45 Photos and videos
Khurram avatar
Khurram@khurram·6 Jan 2024

which VM type/size is recommended for #Azure to run Ubuntu; will be running Docker / Elasticsearch consuming about 2 gigs memory and generating 1gig data per day (which I will rotate) is there any #copilot to get such suggestions :)

Khurram avatar
Khurram@khurram·25 Dec 2023

@DCFaisalabad should dig into this as a resident of not Lahore and paying GSTs and other taxes equally i am sick of seeing lda videos about underpasses and overpasses, and we don't have a single city transport here WHY? Any comments from politicians like @RanaSanaullahPK ?

Khurram avatar
Khurram@khurram·20 Dec 2023

it was genius to make / let these cuts in the middle of the road (d ground example) and not along the footpath few feet away to save thekeydar/tendar money because the road was made from crrrency that grew on d ground trees @DCFaisalabad @SNGPLofficial

Stefan Đokić | .NET avatar
⟳ Khurram retweeted
Stefan Đokić | .NET@TheCodeMan__·10 Dec 2023

Exceptions should be rare. Minimize them. Try something else 👇  Throwing and catching exceptions is slow relative to other code flow patterns. Because of this, exceptions shouldn't be used to control normal program flow. Recommendations (by Microsoft): • Do not use throwing or catching exceptions as a means of normal program flow, especially in hot code paths. • Do include logic in the app to detect and handle conditions that would cause an exception. • Do throw or catch exceptions for unusual or unexpected conditions. The Elegance of Result Object: A Result object encapsulates the outcome of an operation cleanly and expressively. It's designed to convey the result explicitly, without relying on exceptions. The beauty lies in its simplicity. Why use the Result object? Expressiveness: By just looking at the function signature, one can deduce the possible outcomes, making the code self-documenting. Performance: This paradigm avoids the overhead associated with throwing and catching exceptions, especially in expected error scenarios. Unified Error Handling: Errors are now values that can be passed around, manipulated, or logged, making error handling more uniform and predictable. Extensibility: It's easy to extend the Result class to carry additional metadata, validation errors, or other contextual information. I will show how to implement the Result<T> object in the next .NET Pro Weekly Newsletter issue, tomorrow morning. 9600+ engineers will read it. Join them for free: stefandjokic.tech/?utm_sourc… #dotnet

Post attachment
Daniel Cazzulino 🇦🇷🗽 avatar
⟳ Khurram retweeted
Daniel Cazzulino 🇦🇷🗽@kzu·5 Aug 2023

Ok, I've had quite a bit of fun the past few days creating "cloud native (POCO) actors" on top of @msftorleans. My goal was to have a uniform interface (message-based, "IActorBus" essentially) that can also (optionally) support #EventSourcing github.com/devlooped/CloudAc…

Santiago avatar
⟳ Khurram retweeted
Santiago@svpino·27 Aug 2023

Scrum is a cancer. I've been writing software for 25 years, and nothing renders a software team useless like Scrum does. Some anecdotes: 1. They tried to convince me that Poker is a planning tool, not a game. 2. If you want to be more efficient, you must add process, not remove it. They had us attending the "ceremonies," a fancy name for a buttload of meetings: stand-ups, groomings, planning, retrospectives, and Scrum of Scrums. We spent more time talking than doing. 3. We prohibited laptops in meetings. We had to stand. We passed a ball around to keep everyone paying attention. 4. We spent more time estimating story points than writing software. Story points measure complexity, not time, but we had to decide how many story points fit in a sprint. 5. I had to use t-shirt sizes to estimate software. 6. We measured how much it cost to deliver one story point and then wrote contracts where clients paid for a package of "500 story points." 7. Management lost it when they found that 500 story points in one project weren't the same as 500 story points on another project. We had many meetings to fix this. 8. Imagine having a manager, a scrum master, a product owner, and a tech lead. You had to answer to all of them and none simultaneously. 9. We paid people who told us whether we were "burning down points" fast enough. Weren't story points about complexity instead of time? Never mind. I believe in Agile, but this ain't agile. We brought professional Scrum trainers. We paid people from our team to get certified. We tried Scrum this way and that other way. We spent years doing it. The result was always the same: It didn't work. Scrum is a cancer that will eat your development team. Scrum is not for developers; it's another tool for managers to feel they are in control. But the best about Scrum are those who look you in the eye and tell you: "If it doesn't work for you, you are doing it wrong. Scrum is anything that works for your team." Sure it is.

Post attachment
rahul avatar
⟳ Khurram retweeted
rahul@0interestrates·7 Aug 2023

Introducing Animations on Julius.ai (beta) You can now animate your data visualizations 🎥 📈 AI powered data science for everyone sharing some interesting animations generated with Julius in the thread below

0:19
Khurram avatar
Khurram@khurram·3 Aug 2023

the survey option in app, its closed help and support, unable to create new request 1966 help line is only Arabic, Ajmis are equally important no?