fvt

Interesting article. The second paragraph was a tad confusing so I thought I'd share what I found: I think there's maybe confusion between two "camel AIs":

> CamelAI is an open-source, modular framework for building intelligent multi-agent systems for data generation, world simulation, and task automation. > [...] said Miguel Salinas, CTO, CamelAI.

1. CamelAI, where Miguel Salinas is CTO, their website is camelai.com, but it's not a an open source framework they offer. Their "AI data analyst" tool seems cool though.

2. CAMEL-AI, camel-ai.org, the actual open source multi-agent framework, and it also looks like some nice technology right there.

I had no idea this existed but seems useful.

Took a quick look at the Terms of Use and Privacy Policy. Notable gotcha: kids under 16 (in the EU, 13 elsewhere) are prohibited from using this.

(Also, it says "Au revoir mes petits choux!", and I think it's funny.)

I agree with that. The engineering process can be applied on every type of problem.

Yet, for that specific web dev problem, I haven't seen any way of formally testing the rendering web pages, which would make it consistent on every browsers. The testing process (almost) always leave that up to the developers themselves, and refreshing pages is the norm.

Some day we will recognize that some areas of "programming" are very different and require different skill sets, and eventually different titles.

We tend to call everything "software engineering" so that everybody can feel proud of such a title ("I'm an engineer"), but engineering is certainly not about figuring out how to vertically center divs with CSS (and it's also not about proving algebra theorems either -- even if it can be essential when it comes to specific problems that require it).

I can't imagine Linux and PostgreSQL being built without "science", they use a lot of it, and I'm pretty sure the authors all have read SICP and those theoretical books. Poking at things proved to be efficient to building things quickly, but it's just not how one builds critical systems/software that are robust, efficient and maintainable.

IMHO learning about a new language (without becoming proficient with it) is always good as it makes you think about the one(s) you're proficient with.

+1.

Most text editors operate text substitutions (like "<-" turning to "←" automatically), so ASCII doesn't seem inevitable anymore (and I believe it's even truthier with virtual keyboards).

I worked in a company where APL used to be very strong (large french truck manufacturer) and they even had lots of programs written in Scheme for assembly-line optimisations in the late 90s. Most of those have been rewritten (should I say... painfully rewritten, and now buggy) in Java in 2005.

I feel like APL/CLisps/etc. were the right solutions but developers/managers were/are scared when they saw some of the mathematical/proof concepts they had to use, and were afraid of when they learned about them at the university.

While you're definitely right when it comes to printed books, self-published books tend to be pretty up-to-date (as an example, I believe "Agile Web Development With Rails" runs a test suite against Rails and the author gets notified the moment something's not accurate with the book, maybe it's the case for this one).

OP here. Just came across it and I found it was interesting enough as there's not so much books about Docker.

Now that Firefox's teaming up with Tor, I would have been tempted to think they would make users switch to StartPage or DuckDuckGo.

Also, they really should start asking what search engine a user prefers during the first boot of the app.

It's true yet it's going to be free as in "build it for yourself and maintain it all your life". I tend to forget how I've built some tools I'm using and I sometimes spend hours re-understanding what I've done.

Regarding the price, services like feedly - disclaimer: I've been a paying subscriber in the past - cost $45 per year, and it's not been clear to me what value it was providing me (except some integrations with 3rd party tools maybe).

Anyways, I would certainly love to see an integration with RSS readers like the one mentioned above (which would also mark as read all the posts I received in a digest).

When private views become public, one should expect to be "judged" by others, especially when this person is explicitly enlisting the company he is working for in such a campaign and is a well-known field activist.

AFAICT he _had_ to tell what company he was working for. On that very moment, I'm curious to known what went through his mind. Was there any hesitation? Was he realizing he was bringing Mozilla into this debate?

My personal believes is that whether this was deliberate (bringing Mozilla explicitly) or not (being "forced" to list his employer), this was a really bad move you - as a board advisor or investor - will have to deal with and take public actions against.