I only tested it with the two pieces, but was not impressed.
80,188 karma · joined March 24, 2007
I used to run reddit.com's servers, then I ran Site Reliability at Netflix (and invented Chaos Engineering), then I worked on making Alexa faster and smarter, and then I helped build a GPU cloud.
I enjoy technology, hanging out with my daughter and son, advising and investing in startups, and some other stuff.
You can reach me at {anything}@jedberg.net, and also send me any great investment leads there!
Or you can book at meeting with me (but please tell me why in meeting request!): https://calendly.com/dbos-ceo/30min
[ my public key: https://keybase.io/jedberg; my proof: https://keybase.io/jedberg/sigs/f2MDMfeLg---Sa3dsAQASZXctDSSz4GutwD8oOnuUzE ]
I only tested it with the two pieces, but was not impressed.
Cool! What model does it use now? Enterprises will definitely want to know.
And the other big question: Why not just use Claude or Codex (via CLI on a desktop or droplet)?
Are you able to use multiple models? Or I guess the first question is, what model(s) are you using? At this point, many enterprises care so that should be front and center, especially if you're using models hosted in China, because a lot of non-Chinese companies care about that.
You mention some things about unique ways to store memory. Do you have any data or use cases on how that improves performance? If you do, you should get those on your website too.
I'm not sure you have a very strong answer to "Why not just run Claude or Codex on my laptop?" Sure, you provide compute, but so do they, and most enterprises and even regular people are getting desktops/droplets to run their agents now because of this problem. This is kind of solved already.
Also there is a small nit with your website. The graphic next to "Proactively gets things done for you" gets bigger and smaller, so if you're trying to read anything below that, it keeps jumping up and down.
- what is going well,
- what is not going well
-what do hope that I will fix
-what should I do
-what should I not do
I put those question in the agenda for the meeting invite so they could come prepared. Then we took the conversation from there.
I put it all into a google doc, then synthesized it into summary that hid the identities of the people who said it and used it as my guide for the first few months.
Hopefully since it's so old, the copyright holders are cool about it.
ps. Hi Seth, good to see you around!
If you know anyone who has worked at one his companies, especially at a high level, you would know that they made those achievements despite his directions. The SpaceX team was ecstatic when he bought Twitter, because it meant he would be around a lot less.
The policy at SpaceX was basically avoid Elon, and if you had to talk to him, just agree to whatever he said and then not do it. He almost always forgot by the next time he talked to you, and if he didn't, you just said it was really hard.
Since he doesn't understand rocket engineering, it was pretty easy to get away with that.
And the people who worked with him at PayPal would tell you that he knows nothing about software engineering and they basically threw away everything he wrote, but they had to be nice because he had a lot of stock after his company was acquired by PayPal but called a merger.
Elon's main skill is marketing himself. He next best skill is marketing his companies' jobs to talented people and getting them to agree to work there.
That is certainly a critical skill for a CEO, but he is not a great engineer.
Then they would pitch in front of investors with both. Sometimes the ideas got funded and the kids would actually keep working on them.
Nothing until they start failing exams and maybe seeing the error of their ways. My suggestions wasn't for you, it was for the smart student who wants to use AI to enhance their learning but not have it do all the work.
But cheating isn't new. People have been cheating in school for centuries. It's easier now, but the consequences were always the same. At some point the chickens come home to roost and you pay the piper.
AI gives you a way to get the same help without asking another human. Say of that what you will, but not everyone was comfortable asking other humans for help even back then.
Put that in your agents.md.
We've actually changed the therapy procedures based on the data and then been able to show it was effective with the data that came after.
So think about the insights the tracking will provide you and your doctor, and that might help motivate you.
We use old school paper and pencil. I have a clipboard with a tracking sheet created in excel with rows for each thing that needs tracking and columns for the day. Then I don't have to think, I just fill in boxes, and the pencil and paper are always right there on the wall in the bathroom, where the data is "generated" :)
This also lets me scan quickly across for daily and weekly trends. I have room at the bottom for longer notes if necessary. I put a [1] in the box and then a note that matches.
I even studied writing in college. I’ve written published books and articles. I can write well. But thanks for the tip!
1668 — Old ’76 House — Tappan, New York
1673 — White Horse Tavern — Newport, Rhode Island
1681 — King George II Inn — Bristol, Pennsylvania
1742 — Black Horse Tavern & Pub — Mendham, New Jersey
1747 — Reynolds Tavern and 1747 Pub — Annapolis, Maryland
1753 — The Pirate’s House — Savannah, Georgia
1776 — The Griswold Inn — Essex, Connecticut
1779 — Old Talbott Tavern — Bardstown, Kentucky
1779 — The Tavern — Abingdon, Virginia
1780 — Warren Tavern — Charlestown, Massachusetts
1789 — The Inn at Hancock — Hancock, New Hampshire
1790 — Ye Olde Tavern — Manchester, Vermont
1806 — Old Absinthe House — New Orleans, Louisiana
1827 — Ye Olde Trail Tavern — Yellow Springs, Ohio
1831 — New Hudson Inn — New Hudson, Michigan
1835 — Knickerbocker Saloon — Lafayette, Indiana
1842 — O’Malley’s — Weston, Missouri
1847 — The Village Tavern — Long Grove, Illinois
1850 — Landmark 1850 — Milwaukee, Wisconsin
1852 — Golden Gate Saloon — Grass Valley, California
1852 — Breitbach’s Country Dining — Balltown, Iowa
1853 — The Genoa Bar and Saloon — Genoa, Nevada
1857 — Hays House Restaurant and Tavern — Council Grove, Kansas
1859 — The Buffalo Rose — Golden, Colorado
1860s — Buckhorn Saloon and Opera House — Las Vegas, New Mexico
1862 — Miners and Stockmen’s Steakhouse — Hartville, Wyoming
1863 — Bale of Hay Saloon — Virginia City, Montana
1864 — Kelly’s Logan House — Wilmington, Delaware
1866 — Scholz Garten — Austin, Texas
1876 — Glur’s Tavern — Columbus, Nebraska
1877 — The Palace Restaurant and Saloon — Prescott, Arizona
1877 — Buffalo Bodega — Deadwood, South Dakota
1879 — Shooting Star Saloon — Huntsville, Utah
1883 — Pioneer Saloon — Paisley, Oregon
1887 — Neumann’s — North St. Paul, Minnesota
1887 — Bluebird Inn — Bickleton, Washington
1891 — Imperial Bar — Juneau, Alaska
1896 — Eischen’s Bar — Okarche, Oklahoma
1896 — Springwater Supper Club & Lounge — Nashville, Tennessee
1899 — North End Tavern and Brewery — Parkersburg, West Virginia
1903 — The Palace Saloon — Fernandina Beach, Florida
1905 — The Ohio Club — Hot Springs, Arkansas
1906 — Ford’s Bar — Idaho Falls, Idaho
1932 — Antlers Bar — Blowing Rock, North Carolina
1933 — Henry’s on the Market — Charleston, South Carolina
1935 — Town Hall Bar — West Fargo, North Dakota
1936 — Forest Gardens — Portland, Maine
1946 — Callaghan’s Irish Social Club — Mobile, Alabama
1948 — Blue Front Cafe — Bentonia, Mississippi
1957 — La Mariana Sailing Club — Honolulu, Hawaii
Source: https://www.businessinsider.com/oldest-bar-every-state
But AI was trained on good writing. Good writing looks like AI. I've had to reduce my use of em dashes for example because they are an "AI tell". I used to like using the term "load bearing".
And the list gets longer every day. Eventually every mark of a good writer will be an AI tell.
I don't know how to resolve this. But I've been accused multiple times of copy/pasting AI when I did no such thing, and it's getting equally frustrating.
The thing microservices is supposed to solve is eliminating the need to make atomic changes across services. There is an inherent overhead in doing that, like making your service support both new and old APIs as long as any service exists using the old API. This is the cost of microservices.
You have to make the change to service A and B, and then test both and deploy both. You haven't saved any time or effort in a monorepo.
A library needs updating, you still have to update it and then test and deploy every service that relies on it independently. Again you haven't saved any time or effort. In fact you've made it worse, because if those services are maintained by different people, you just forced them to test and deploy on your timeline and priority, not theirs. You actually made the coordination problem worse.
You're probably not using your microservices correctly if you need to change more than one service at the same time. The whole point of microservices is independently developing and deploying the services. Sweeping changes like that should be done in pieces, one service at a time.
Which is why microservices are best for larger organizations, because it reduces coordination between dev groups.
If you have a monorepo, you're almost certainly violating that somewhere, using a shared library, or a shared database, or even just blocking deployment because some other service has turned the repo red.