newtonapple

My real point is this: if you're not allowed to bring your experiences with you, then the company exists to extract your creative thinking and skills. You can argue that's a fair trade for money. I don't necessarily disagree. But I think most of us find joy in learning, in building our own skills, in being able to reapply them elsewhere. And before LLMs and agents, I couldn't lose those skills and experiences no matter where I worked. As we progress, though, we've hit a point where we have to ask ourselves: at what price are we willing to trade complete ownership of our thinking and experiences for money?

It is also illegal in CA.

This is my personal conclusion as well. But think about where this leads. In the future, agents will do most of the coding and our job is to guide and train them. Most of our skills would be externalized somehow, living in the agents instead of in our heads. Which means once you leave a company, you may have effectively lost a lot of your hard earned skills and experiences.

I'm not arguing for either side, but here's a fun thought experiment I've been thinking about a lot lately. If I learned things at one company, took my experience and memory to another company, and applied what I had learned there, am I technically stealing that company's secrets? What if I trained a team of agents to think and code like me at work, then exported those agentic skills and took them with me to another company? At what point would they still be considered the old company's property? Let's say I didn't take any code or proprietary information from the old company, just the coding style and best practices my agents learned from the old company's live metrics. Is that considered stealing from the company? Is that any different from me learning those patterns and skills personally and then reapplying them elsewhere?

Has anyone tried immudb in production? What are some of immudb's performance characteristics? It'd be nice to know how it performs under various conditions: query per sec, database / table sizes, SQL join performance etc.

Also, what are the system requirements for immudb? What kind of machine would I need to run a medium to large website (say, 1TB of data, 5-25K qps, e.g. Wikipedia)?

It mentioned in the documentation that it can use S3 as its storage? Are there performance implications if you do this?

I drove through North Lake Tahoe one time on a weekday around midnight, and Google Maps was showing all red as I was driving up the mountain... I was super confused as there were no cars around me and it was not snowing either. What I later realized was that all the trucks were parked alongside the freeway taking breaks... I never realized that you could basically trick Google Maps by using a bunch of cellphones. Very neat!

For low level APIs, I would say anything that could be configured on a per call basis should be parameterized: memory allocations, database & http connections etc.

What will happen if you have bug in your function? Take the fibonacci function for example, what if you have a bug and created an infinite loop? Will Prepack terminate?

"Then again, with Chrome taking up >4GB of RAM, they probably could have gotten half that performance just by closing their browser or using Safari." This is so true. I've recently stopped using Chrome and switched to Safari. Now my 5-year old MacBook Pro runs like butter.