This has been the the case all the time: most of our work are connecting pipes using glue code/duct tape so to speak. But now, we are delegating this to AI. Nothing new for me.
Maybe it is just me: I feel Anthropic most recent product announcements resemble more and more like what IBM tactic was at its high. For instance, the Watson AI hype after it defeated Kasparov. The difference is IBM actually wanted and let businesses buy and use Watson as opposed to time released like what Anthropic does to even boost the hype higher.
I really appreciate the documentation. But, it appears to me that this is how I also use Claude daily and I thought I am just using it as a coding agent. The intro however sounds like a recipe to use Claude for everything else beyond a coding agent.
Also, this stuff feels like alchemy to me . I bet some of you have the same feeling.
> Oral sodium sulfate in a single dose has been found to cause increased gastrointestinal (GI) events
> Sodium phosphate is no longer recommended as a bowel preparation regimen due to its serious side effects
Essentially, put in the effort and do the liquid bowel prep.
Consider adding flavour drops to your drink, icing it or turn it into a slushie to make it slightly more interesting to drink. The PEG will make the ice crystals slightly more smoother.
Essentially, put in the effort and do the liquid bowel prep.
It's not just about effort. I must do the liquid prep due to my Crohn's disease. And while I am able to get the liquid down (as you note, it helps to make it as cold as possible; also, suck on an ice cube before drinking to numb the taste buds), I can't keep it down. Within an hour it has me evacuating from both ends.
For my last test, I barely slept at all the night before on account of the vomiting, and even once I got to the hospital I was lying on the wonderfully cold tile of the floor between rolling over to vomit in a trash can.
They know it affects me badly, but still assess that it's necessary due to my risk factors. And because I'm losing much of the drug due to the vomiting, the prep is poor, so I have to start fasting a day early to ensure that I get sufficiently cleaned out. It's torture all around.
It must be really challenging to feel like you are an outlier, and that medical advice does not fit you.
There are going to be niche clinical situations where the benefits outweigh the risks of what is otherwise generally not recommended. If you’re not able to tolerate the liquid prep, you’re obviously better to take an oral fleet than no prep at all.
What helps for me was using cool/chilled water, and a swimmer's nose clip to help reduce the smell of the ingredients. If you are adding flavor drops - go with lemon and not anything blue or red in color.
One other piece of advice - stay off the internet afterwards until you're sure the anesthesia has worn off. My doctor related that a previous patient had gone on the Carvana website and bought a car while still under the effects. Oops.
These are best practices guidelines that are ultimately implemented (or rejected) by surgeons who still go by feel, whether following the latest-and-greatest or by what they are used to.
I can’t compare the two, but fwiw, in my experience, while the drink is mildly unpleasant it’s only the texture of the drink itself that’s bad and the fact that you have to drink quite a bit of it. It doesn’t taste bad per se (and you can add flavored drink mix to help) and the “purging” part is painless, ie no cramps or anything.
I find this so hard to believe, but I've nearly always worked in small groups/companies. Can you, or any of the commenters above, explain why the reasoning that leads to such a service isn't rejected by, well, common sense? Some super-special requirements?
So they had a team of SWEs who knew the system they were responsible for was absurd, but they weren't able to adequately explain that to the senior management folk who came from that DCOps culture and held asset management & configuration tracking to be paramount. The uniqueness was seen less as an inherent property, and more as a constraint that needed to be enforced.
My team of DevOps-y proto-Platform Engineers struggled with the org's culture in similar ways, so I had a lot of sympathy for the situation they found themselves in and how they were handling it. I believe their Zookeeper-based system was intended to be more of generic lightweight config registry which would eventually have replaced the gigantic SOAP-based CMDB nightmare - basically Consul a year or two before Consul existed.
The reason why they struggled to get it into production was that it would have been so obviously useful that they kept having additional requirements and use cases forced into their "MVP". That sort of scope creep, driven by tech leadership wanting to make their mark on a successful project, is also pretty common in large orgs.
Fortunately, I've neverencountered that. But still, I can see the usefulness of a guaranteed globally unique UUID, at least for certain purposes. However, a service to add numbers baffles me. The operations needed to create, send, receive and check the message are so much more complex than addition...
I must say, I did experience some lousy tech+sales leadership in one company, which was indeed the biggest I ever worked at. A decent product with a well understood scope was completely scrapped and rewritten. Some team spent more than a year on the (waterfall) design of the new system, which was then scrapped too. When I joined, there was an 8 man team for just the message bus for the new new system. Which didn't even work correctly. The whole was flexible, but in nearly every other aspect inferior to the original product. And it needed much heavier hardware.
Sure. In this case, this started as a method with two parameters; each were validated internally before addition.
The validation was long running, as it required checking two other services to confirm both of the numbers were OK.
Because of issues calling those services, instead of two nasty synchronous calls, it turned into calling a microservice asynchronously and using a callback. Then that microservice was owned by the team that owned those two other services.
reply