cientifico

Correction in 2. Contrary to popular believe, sunnier countries in Europe have higher deficiency in vitamin d.

Spain have lower levels of vitamin d than Denmark.

Also got it last year.

I used to play with omarchy. It is good enough for a lot of use cases. For powerful work I just connect to remote session.

Perfect for planes in economy

Love it.

I would love that the size of the article is based on the number of upvotes (hardcoded).

* > 500 => take full width or 3. * 500 > 100 => Show it as right now. * > 100 => Just show the title.

Right now, local inference only make sense for privacy reasons.

This is common when processing PII. Lawyers, doctors our similar should not be using cloud solutions.

Also it's harder to setup and always more expensive than any cloud solution.

We tend to forget

There is one missing that i am using as primary for the last 5 years.

The UX pyramid but applied to DX.

It basically states that you should not focus in making something significant enjoyable or convenient if you don't have something that is usable, reliable or remotely functional.

https://www.google.com/search?q=ux+pyramid

In my case. The prompt is normally a collection of ideas connected over time. Ai groups, structure, challenges and help me organize that ideas. Then, once I see something that I consider worth sharing, I ask to draft a blog post. 20 iterations over, and I have a blog post.

The prompt is normally larger than the content generated.

I find some parallelism between writing articles and Pull requests.

We are moving to a point in time, where we don't care if the PR was written by AI. We care that the author understand what is about, that it tested it and in general, we want the ownership.

With articles is the same. I don't care if it was written by AI, if the content is interesting, and ai make it easier to digest... That's a win win.

The problem is not the presentation. Is the content.

My self.

LLM helps me communicate my ideas better.

Thinking in different angles, focus on the main idea, structure in a post series... It constantly challenge my mess.

Opus and I, iterate over 20 times a single blog post.

Unpopular opinion.

Until now, ideas were only relevant when the owner was able to communicate then regardless of the impact of the idea.

LLM "democratize"(VC term) sharing ideas, as people with low communication skills can be heard.

For most users that wanted to run LLM locally, ollama solved the UX problem.

One command, and you are running the models even with the rocm drivers without knowing.

If llama provides such UX, they failed terrible at communicating that. Starting with the name. Llama.cpp: that's a cpp library! Ollama is the wrapper. That's the mental model. I don't want to build my own program! I just want to have fun :-P

Click on any Youtube video from any web in android. If you press anything that is not the back button immediately, you will loose the option to go back.

So this coming from google... it's funny. Welcome, but funny.

Thanks, I agree.

I’ve been asking myself the same thing for years. My take:

1. Peter Principle: people get promoted to their level of incompetence.

2. In many companies, it’s the only way to increase salary.

3. Some developers think it gives them more leverage or impact.

But honestly, most of the time it’s simpler: stakeholders want more output, and the best dev gets pushed into leading because there’s no one else.

It’s often less a “promotion” and more a gap the company needs to fill.

This feels jumping on the train of complain about Europe and fully bias.

If I apply my own bias I will call it:

    American companies abuse their dominance my enforcing non documented requirements, making other companies not able to reach their users.

Github says 2.8k files when selecting c (including headers...) https://github.com/search?q=repo%3Asystemd%2Fsystemd++langua...

If the project is even split in different parts that you need to understand... already makes the point.

Looking for postgres unikernel seems like some people are trying seriously...

https://nanovms.com/dev/tutorials/running-postgres-as-a-unik...

I don't know how it is in US, but in Europe, the amount of scams is growing. Twitter blue checkmark was created to distinguish real humans vs scammers.

The fine was to protected the users from that scam.

I like paying taxes to protected the users that don't have the ability to detect scams as we all here have (most of the time).

EU miss the point equally to the Congress in uuss when non tech people believe they can rule (or just lobbied).

But on this case, there will be no problem if Twitter had decided to use another checkmark for pro accounts.

That it's an osx ONLY app.

One hidden gem.

The closest free alternative is https://www.mitmproxy.org/ that is not even close.

And off course, https://www.wireshark.org/ but that is too generic and with a bigger learning curve.

Worth the money. And no subscription (or there weren't a subscription back then)

Services (or a set of Microservices) should mimic teams at the company. If we have polytree, that should represent departments.

That was the same conclusion I got by playing with the graphs.

I concluded that better IO planning it's only worth it for "slow" I/O in 18.

Pretty sure it will bring a lot of learnings. Postgress devs are pretty awesome.

I wouldn't generalize it that much. There are few patterns where Turbo Streams, subscriptions, and permanent frames still make a lot of sense.

One classic case is user notifications - like the user icon in the corner. That's perfect as a permanent lazy frame, with a subscription watching for any user-related updates. This way you don't have to think about updating that widget across different pages, and you can centralize all user-related async events in

one controller.

Another pattern is real-time dashboards. You never know which part of the dashboard will change, and it's actually simpler on the backend: you just track what was updated and push that specific part. Clean and efficient.

Been using Turbo (and Turbolinks before it) for 10+ years, mostly outside Rails. It's awesome in that context.

Can't really see how making it more Rails-centric would help - more likely it'd just cause a fork for everyone using Hotwire without Rails/Ruby.

Killing all the fun.

Remember when you could trick a colleague into posting in Twitter, Facebook... by just sending a link?

CSRF fixes are great for security - but they've definitely made some of the internet's harmless mischief more boring

The license was MIT until two months ago.

That gives anyone the right to get the source code of that commit and do whatever.

The article does not specified if the company is still using the code AFTER the license change.

The rest of the points are still valid.

Because that’s literally the definition of open source:

Open-source software is software released under a license where the copyright holder grants users the rights to use, study, change, and distribute the software and its source code, for any purpose.

That’s the first result you get on Google—and it’s exactly why so many companies relicensed their projects (Redis, HashiCorp, Elasticsearch, MongoDB…).

If it’s open source, you can sell it, host it, or give it away for free. The only difference is which obligations the license attaches:

GPL → you must keep the license.

AGPL → you must keep it and extend it to hosted services.

BSD/MIT → do almost whatever you want.

But the core right is always the same: distribute, host, and sell. Courts have even confirmed this is the accepted definition of “open source.”

Can you clarify the following sentence:

We are open-source (https://github.com/cactus-compute/cactus). Cactus is free for hobbyists and personal projects, with a paid license required for commercial use.

If it is open-source, one is free to distribute even for commercial use by definition. Which one is correct and what's your business model?

We've adopted Google Wire for some projects at JustWatch, and it's been a game changer. It's surprisingly under the radar, but it helped us eliminate messy shutdown logic in Kubernetes. Wire forces clean dependency injection, so now everything shuts down in order instead... well who knows :-D

https://go.dev/blog/wire https://github.com/google/wire

I like Hotwire/Turbo more than HTMX because of its core philosophy: start by building a fully functional page without any JavaScript, and then layer in enhancements only as needed. That approach has stayed consistent for years and feels really straightforward to work with.

Justwatch | golang | Berlin | https://www.justwatch.com/talent/jobs/tech/streamingguide-ju...

Backend development at justwatch. Looking for all levels, not only junior.

Go, postgress, kubernetes.

No remote.

Feel free to contact: guillermo.alvarez at justwatch.com