The sensitivity to prompts and response quality are related to an agent's functionality, A2A is only addressing the communication aspects between agents and not the content within.
346 karma · joined June 6, 2016
The sensitivity to prompts and response quality are related to an agent's functionality, A2A is only addressing the communication aspects between agents and not the content within.
It was fun to present it in demos, but it can also be annoying to users.
I was pleasantly surprised to see him driving and trying to charge the car in public locations.
I am previously the founder of a synthetic monitoring startup, devraven.io.
Just sharing my experience - monitoring is brutally competitive. From my conversations most large enterprises have very little synthetic monitoring, they use DDOG or other APM tools and do not want to try any new tools for few thousand dollar savings. And in a lot of cases they are comfortable with their custom test frameworks that use Selenium. Some are even worried that setting up synthetic monitoring will bring down their environment or trash their database with junk data ::sigh::
Most smaller companies we spoke to are not mature enough to have monitoring and did not have resources who can setup monitoring. They used to ask us for help to build tests for them. Asks for discounts on $29.99/mo price point were not uncommon.
After few months of operating the product, we did find few angels who were interested in investing in us (not the product). But in the end, we did not feel that we can make good use of investor money and provide a decent return to them, so we ended up backing out of the investment and chose to shutdown the product.
Fair feedback. I definitely need to anchor myself to specific niche instead of saying it can work for anything and everything.
But the APIs are accessible today with basic auth.
1. Create a Source for each customer and send customer specific data to each source. Configured pipelines for each source will receive the event data and processes it.
2. Create one source with multiple pipelines connected to it. In each pipeline, you can drop processing the data based on any conditions.
#1 is preferred so you are sure each customer's data is only reaching the pipelines configured for that customer data.
A ServiceNow integration is on my radar. But if you can provide more details I can definitely try to address it when I build the app. Please feel free to log an issue in github if you can provide any details or send an email to me (email in my profile).
Something like - if x or x% events are failing in a pipeline, pause the pipeline for y minutes or until some one unpauses it.
I can look at adding it.
It's about 3 months in the making and needs improvements around ops, tests. I am hoping to make progress with adding tests in the coming days and provide monitoring capabilities.
I think there are a number of platforms for building workflows and integrations today. Some of the platforms serving specific niche (e.g. RudderStack chose to serve CDP, airplane for building internal dev tools). But in the end all of them act on a trigger to transform inbound event data and send it to a destination end point.
Windmill looks cool with support for multiple languages, no-code editor and all the OOTB integrations.
cptn is still evolving - it needs to have more integrations, UX flows need to be improved, it has to get better from Ops perspective.
Licensing "seems" to be restrictive if you want to use for commercial purposes (I am not quite sure about Sustainable Use License).
RudderStack is AGPL while cptn is MIT.
For complex cases or specialized integrations, you can use any npm library to build your flow.
You can integrate into your stack with HTTP API and we can build SDKs for popular languages so it's just a function call to send the events.
I am glad I went through all the pain.
minimize is the keyword here. I assume you have seen regressions with Friday pushes and team had to spend their weekends resolving that at least once.
People will do mistakes, bugs will go into code, regressions will happen. It's just inevitable and no amount of automation can cover all your user paths.
People will hate this unpredictability to plan their weekends and spend a peaceful weekend. IMO, it's not worth it.
I am resetting all the passwords for all my accounts. It's super annoying and it will days for me to reset all the passwords. But thankfully I have MFA for all important stuff.
You may consider trying this extension - https://chrome.google.com/webstore/detail/devraven-recorder/.... This extension can record the tests using your Chrome browser instead of launching a separate Playwright chromium browser. Full disclosure: I am the developer of this extension.
I took BART - there are hardly 10 cars in the entire parking lot by 8AM. The lot used to be full. There were three people in the train car I boarded, which used to be pretty full.
I walked from train station to the venue, there are very few people overall in the city. It used to be usually busy on workdays people trying to get to their workplaces.
I felt less than 10% of the people who used to commute are now going to the city, I am not sure if there are any official stats published.
I preferred to strip away the .html extensions anyway, so it was okay in my case. CF should trigger a HTTP 308 for older .html to the new urls automatically.
I have contemplated Stripe vs Paddle couple of months ago. But ultimately chose to stay with Stripe and deal with tax complexities when there is sizable revenue.
1. Enter your email address, receive 2FA token.
2. Enter the token, show the hiring status.
Ignoring that part, even if they just stick to collecting the background information, SSN, copies of drivers license - that is just good enough information for full-blown ID theft.
Even legitimate companies use varieties of third-parties that help with hiring, background checks, payroll etc. I remember entering data to Workday, some background check provider's site, jobvite, {mycompany}benefits.com etc. the last time I went through hiring process. It's just easy to scam candidates unless they pay close attention to smallest details.