louiskottmann

That is stretching the subject beyond reasonable. Proprietary software as a general endeavor is not an invalid business and nobody is saying that here.

LibreOffice is close enough to Microsoft's offering that surely it makes sense accross the many EU states to stop spending millions on it, and spend a few to close the gap, saving even more millions in the future.

Chosing to pay millions when it is not necessary is definitely not a valid choice. It is at best stupidity, at worse corruption.

In my experience in the public sector in France, I have seen these decisions taken to advance someone's career.

For example, a first year free means a purchase person will get their promotion on incredible YoY progress.

There's frequent discussions about how sonnet-3.5 is in the same ballpark or even outperforms sonnet-3.7 and 4.0, for example.

Indeed, and with the technology plateau-ing, being 6-12 months late with less debt is just long term thinking.

Also, Europe being in the race is a big deal for consumers.

Heavy user and I moved to Atuin because of the shell history scoping issue with regular bash history.

No matter my config it would always glitch. Atuin is backed by a global sqlite db: problem solved. And unlimited history.

I don't use sync though, commands sent to 3rd party servers are a no-go.

I think the upside is that we stop spending limited human time on mundane/easy things and focus on higher-value pursuit.

Because you can no longer be a cheap artist, because you can no longer help students on easy problems en masse, because family businesses no longer need a webmaster.

That's a step in the right direction, maybe even towards UBI.

On growth, I disagree that we reached the plateau already. We won't fundamentally change things but larger context windows, speed, compute and cost? Obviously.

That in itself is a major evolution.

It looks like it is fading out of hype maybe, but that's just like all things. LLMs aren't going anywhere, just like Rails got version 8 out and it's better than ever.

It's not allowed, but you'd have to sue if you uncover one such questionnaire, which is a hassle.

So instead, lying on your answer is not sue-able. Which makes including such questions ineffective.

SEEKING WORK | Paris, France & OSlo, Norway | REMOTE

15 years of experience in tech, developing in all major paradigms, strong expertise in DevOps engineering, as a technical lead, a recruiter, good experience with CTO and COO positions.

I also work with another expert DevOps when my clients needs requires it.

- Do you want DevOps practices with a hands-on, pragmatic approach?

- Need realistic workflows for your developers to quicken release cycles, improve quality, tighten security?

- Wonder how to setup a technical team that delivers, from technology choices to recruiting the team, managing the tooling, and making that team time-resilient so you don't have to do it over and over again?

Let's talk!

Contact: louis@k-hops.fr

I would honestly rather not make any user's Chrome experience better than Firefox given the curtent marketshares. It would not feel ethical to me to partake in helping Google seize more power on browsers.

The big difference in my opinion is that your ad-hoc servers using static binaries, with all the outside stuff specific to your organization, are non-standard.

For some miraculous reason K8S is ubiquitous and everybody uses it. Standardization is a boon.

People complain about git using similar arguments, and yet having a vast majority of the tech world on it is a boon for tooling.

Both those technologies are excellent but take some time to master (you don't have to be an expert though).

I can get on a project using git, kubernetes and say RoR and understand it very quickly without help. It is well bounded. It takes a git account and a kubeconfig. All set.

A custom python codebase deployed on custom servers running in big enterprise-y network, not so much.

It is statistically significantly harder to have a successful company as a solo founder. Having someone with a stake to bounce ideas and solutions off of makes a big difference. My associate and I regularly thank each other for catastrophes we avoided by our weekly night of talking over beer (and other daily exchanges).

I'm not too sure about _absolutely_ selling before making, but definitely do a market research and check if you can find people who would, at least theoretically, buy the product you intend to make.

If you make before you sell, you're saying that you are a visionary and people cannot understand your genius. Those are not odds to my liking, but if you like them you do you.

Like I said in the last paragraph: I would not.

If the bash program evolves to span multiple files and lots of lines, I usually switch to ansible/ruby/clojure

I am a bash expert.

This paper reads like it was written by clueless academics with no real world experience.

Multicore bash already exists and is seldom used, through the "parallel" cmd.

Other points address no particular issue, and would actually make the language more painful to use.

Bash has its limits, which pushes you to use a full fledged language if you attempt to walk past them. It's a good system.

That would become unreadable in many cases, like du -sh *

Same complaint here, I really like the project, hosted a server for a while, but ultimately the problems of verified users in channels were too much of a hassle.

To be fair, other E2E chat solutions have similar problems, like Signal. It feels more to me like we did not properly crack this problem yet.

I have yet to try it again but definitely want to.

I disagree. Discussions about diversity and equality are absolutely political debate. It's even boringly trending I must say.

It's barely a 30seconds discussion between founders, not a company-wide debate. You follow it up with a yearly report on actual diversity vs real world distribution. That is, if you're big enough a company to be compared to it.

For example: if you have zero women in tech, there is a problem, and you have people to remove from recruiting roles. If you're close-ish to the median of your recruiting pool, you're fine. What need do you have for ceaseless internal discussions about it?

Serverless is not so shiny when compared to a cloud-managed Kubernetes cluster.

I get to deploy stuff "the regular way", that is with a constantly running application, I don't have to re-train my developers, I have extra power in the cluster should I need it, I don't depend on a cloud provider in particular, and my costs are bounded.

Cherry on top: I don't maintain the infrastructure either, there isn't even a SSH daemon running.

There is another problem, beyond the initial ads-based business. This information gathered about you, albeit anonymously, is correlated. This helps train models about groups of people, in order to derive value from group information. It can then be sold to insurances, banks, etc.

Derived information may look like: "Clojure programmers buy a new computer every 3 years on average" "Women in medium socio-economic groups tend to have kids at 31 years old"

But maybe I'm a programmer that cares about waste, and use the hell out of my computers, until it is completely unusable, making them last way longer. Maybe I'm a woman with trouble getting pregnant, and I won't have kids until much later.

Nevertheless, insurances and banks will use that information against me.

This information grouping you take part of, is de-humanizing. Humans are infinitely complex, ever-evolving creatures and categorizing us is profitable business. I do not want to be treated through the lens of the probability of a group I belong to, no matter how small the box.

You can start off with an example you would find online, then use "kubectl explain" to read about the options used and other ones you want to use.

Whenever I see video content I automatically think "I do not have time for this".

Text lets me efficiently skip through most of articles if they do not get to the point, or if they linger in ELI5.

The more I know about a field, the more I want to skip bits, because I don't need to be explained the basics over again.

Decorators and AOP are very similar concepts in my opinion then, if you prefer.

It is very close to python's @ syntax on top of methods definitions.

Like:

@get('/posts')

mymethod

  ...

The single biggest productivity boost is when I realized over 90% of my time is spent in Firefox+Terminal+Emacs.

Alt-tab drove me nuts so I bind F2/F3/F4 to a script that will cycle through instances of these 3 programs.

F2 is terminal, F2 again is next terminal, etc.

The thing is, when you start having a lot of candidates at your door, say, because you are a big company with interesting problems and/or good benefits, and the position is sought-after, your recruitment process costs even more. So you look to lower that cost by filtering out applicants based on some criterias. People from renowned schools go first because they are more likely to be skilled on average, if you ever deplete that pool, you look for the rest.

I recruit for my company, and we don't do that, in fact we do quite the opposite. But I'm pretty sure that's how big companies see it.

Hexagonal | Experienced Frontend Developer | France, Netherlands | Full-time | REMOTE

Hexagonal is a web agency built around Faveod, which is macro-programming on top of Rails.

Our client are big French companies that are sick and tired of the old contracting way of doing things.

We do everything from idea to execution and long-term maintenance. That is project definition, project management, design (real, with artists), frontend, backend, devops, and infrastructure.

We wanted to make the company where we would have loved to work. It is remote-first, there are no offices. Many standard benefits and not-so-standard ones, like the often talked but rarely practiced several week-long retreats per year with everybody in a fun location.

Apply at cv@hexagonalconsulting.com

Hexagonal | Ruby on Rails backend/fullstack developers | Full-time | REMOTE from France or the Netherlands

Requirements: Fluent in French and good English speaking skills Must work from France or the Netherlands, and be a resident from there

3/4+ years of experience in:

- Ruby on Rails

- SQL/Arel

- "Vanilla" JS

- CSS if you apply for fullstack

Good at communicating

The Role: You will be part of a team of 5, and together you will work using Faveod (macro-programming on top of Rails) on projects for our clients.

The Company: We are a company of experts in Faveod, which is a macro-programming engine on top of Ruby of Rails. Our typical clients are big french and worldwide companies.

We don't have offices, each of our 25+ employees are working remotely from France and Amsterdam, in teams constituted of a project manager, a lead developer, 1-2 developers, a frontend developer, devops and an artist. Teams change per-project.

You will meet your coworkers overs dinners, pool-table tournaments, initial kick-offs at the client's and 2x1 week long retreats per year. We are very keen on keeping the good vibe we have at the company. The previous seminary was in Martinique (Caribbean island), the next one will be in Athens.

Benefits:

25+5 paid vacation days

Tickets restaurants (9€ per worked day to purchase lunch)

PEE (saving account where when you put money, we do too, with a multiplicator and threshold based on the current year's revenue of the company)

Flexible hours (although we try to all be present between 14h00 and 18h00 on work days)

CDI+cadre jour (good French status)

Email cv@hexagonalconsulting.com for more informations!

Hexagonal Consulting | Web Integrator | Full time (CDI) @35k€ | REMOTE from France or Netherlands

Requirements:

- Fluent in French and good English speaking skills.

- HTML/CSS/Vanilla JS/JQuery

Bonus:

- Interest in fullstack

We are a consulting firm of experts in Faveod, which is a macroprogramming engine on top of Ruby of Rails. Our typical clients are big french and worldwide companies.

The service we offer is fast-paced projects from top to bottom.

For example: a client has a long-failed line of projects to handle specialized maps, they want an innovative technology with a team of experts to finally bring it to life with reasonable budgets and good timing on deliver-ability.

What we do: we define the request (macro-planning, features required for the MVP), hand it over to the project manager who further breaks it down into sprints, then the development/integration team starts working on it. Meanwhile, the devops sets up the infrastructure. We also offer design with our in-house artistic director.

We don't have offices, each of our ~20 employees are working remotely from France and Amsterdam, in teams constituted of a project manager, a lead developer + 1 to 3 developers, a web integrator and a devops.

You will see your coworkers overs diners, pool-table tournaments, initial kick-offs at the client's and 2 week-long seminaries per year. The next seminary is next week in Martinique (Caribbean island).

---

Get in touch: cv@hexagonalconsulting.com (I personally reply on that address).

---

I believe the problem is not so much about finding and flagging criminals, but treating the reasons criminals act like that.

These cameras do not explain how they got there. Who profits from it? Whoever likes the situation that put criminals in that place.

Then there's no need to treat poverty anymore because they'll be dying in a corner as intended, instead of stealing food.

I think many believe that "this should be easy, just add commits and get versioning, voilà!" and thus never invest the time (what, 2 days max?) to actually dig in, try a few common scenarios on a dummy repo, before actually using it on a live project.

The truth is, it's not so easy a task to get versioning right and git does, people are not humble enough.

Well, to take on the other side of the coin:

Would you like to work on a custom-built project of someone else, decent-sized, in a language you grasp poorly?

Because that's what your "small, light system, out of large frameworks" will look like to someone who dabbles in ruby/rails and looks for a job (most of the force never reaches mastery, let alone wants to).