nfrankel

I think so indeed ;-)

Migrate to the Cloud, they said. It will be more resilient and less expensive, they said.

I'm so glad I deleted my What's App account when FB acquired it.

I have a fairly long experience of both teaching and grading, even though I stopped a couple of years ago. After a couple of years of trial-and-error, I think I found the "right" way:

* Alternate between theory and practice in the course of a single 2-hours slot. Theory is necessary, but the attention span of people is very limited. * Grade either a homework assignment in the form of a real project with specifications. You give the assignment half-semester, so that students who start early can ask questions. Otherwise, grade a in-session exam, with every resource available, including the course and the whole Internet. However, you don't assess the knowledge, but if the student is able to apply their knowledge to the different tasks at hand.

These approaches are now completely moot in the age of AI.

I was surprised the first time a colleague asked me to do an oral exam. I thought it was a burden on people with poor social interaction skills. It went surprisingly well: you could see in a couple of minutes if the student had integrated the concepts of the course, even if they were shy. Now I wonder if it's the way to go. There's one caveat, though: it doesn't scale.

Fun fact, France did exactly the same earlier this year (though the trend has been there for decades).

[1] https://en.wikipedia.org/wiki/Gold_repatriation#France

Unfortunately, I share the sentiment. Although I have been blogging weekly for more than 15 years, I have less and less incentives to share my learnings.

I don't know about other European countries (well, I know, but I'm polite), but in France, restaurants will always have salt/pepper and frequently oil/vinegar on each table.

For ketchup, I'm afraid you'll need to stay in the US.

I tried. It works in theory: https://blog.frankel.ch/tokensparsamkeit-coding-assistants/#...

Results depend on the model, of course, and your computer is the limit. Mine wasn't up to the task, unfortunately.

What I wrote above:

>I use Home Assistant (https://www.home-assistant.io/). It has an integration for lots of manufacturers. Single app, single entry point, cross manufacturer automations.

I use Home Assistant (https://www.home-assistant.io/). It has an integration for lots of manufacturers. Single app, single entry point, cross manufacturer automations.

Or just use Asciidoc...

Happy to hear your opinions. Obviously, I'm a fan.

As an architecture graduate who never worked in the field, I'm glad this allows to debunk the all bullshits of fame-driven architects.

I have a talk on OpenTelemetry that I regularly present at conferences. After it, I often get the question: "But what's the performance overhead?". In general, I answer by another question: "Is it better to go fast blindfolded or slightly slower with full visibility?". Then I advise the person to do their own performance test in their specific context.

I'm very happy somebody took the time to measure it.

Basically, the author wants Spring Boot for Rust

I wonder if the author has ever heard something called an IDE?

Location: France, Switzerland Remote: Yes Willing to relocate: no Technologies: Java, Kotlin, Rust, Python, enough front-end and database skills. for regular features, APIs, testing, Continuous Integration, GitHub Actions, GitLab, Content writing, Public Speaking

I've been in IT for more than 20 years, 17 of them in development (developer, team lead, software architect, then solution architect) and 6 of them in developer advocay.

My journey has been deeply rooted in Java, Spring, and "DevOps", where I’ve focused on improving software architecture, testing, and continuous delivery practices. I’m passionate about sharing my knowledge and experiences, on top of writing and designing software. My goal is to help teams and organizations bridge the gap between development and operations, enabling them to adopt modern technologies and practices with greater confidence.

Feel free to ping me at nicolas at frankel dot ch.

The Java team is still breaking things despite numerous pleas of the community pleading not to do so? Color me surprised.

The Security Manager send its regards.

Duly noted

I know where it comes from, don't worry :-)

Author here. Yes, it's all about Conway's Law. Unfortunately, it's still a law that governs all companies. Fun fact: I stopped working in projects because I mostly had to find technical solutions to organizational issues.

PS: I wouldn't call it "political" (negatively connotated) but "organizational" (statement of fact)

I wholeheartedly agree. I was about to list it as a reference only, then I forgot.

I can confirm it's forbidden. Depending on how sensitive the company (and its lawyers) is, it may be enforced or not.

Funny to see this here. More than twenty years ago, I did my Master thesis in Architecture using VRML to display a building I had designed and the surrounding district.

I especially loved the Level-Of-Detail object that allows to design different objects depending on the distance of the object with the view point.

I still have the files somewhere, but last time I checked, I found no software to read them.

>As a simple example, imagine a small team of, say, 6 developers: > >The team has created and now supports a mobile app, an Alexa skill, three separate web apps, fifteen microservices, and a partridge in a pear tree.

If a team of 6 developers created 15 microservices, I'm afraid that they don't understand the pros nor the cons of microservices and they should be fired instantly.

I've found the solution a while ago: unfollow. I only follow people who tweet about themes that interest me.

If somebody wants to tell the world their private life, good for them, but without me.

> If your build has really custom stuff

That's the biggest problem. Nearly every developer thinks their build has *really* custom stuff whereas it's wrong in 99% of the cases.

Then comes Gradle with its so-much-vaunted flexibility and deliver you exactly what you think you need. And who is going to maintain the clusterfuck of spaghetti code that your build has become?

I was a consultant and I used the rule of 3 whys. When a customer asks for a feature, get back to the root concern by asking "why"?

Rust newbie here. I confirm both the friendliness of the compiler and of the community.

That's because you don't deal with state