Eric Fesler

#java #oss #scala #drupal

[Eric Fesler @efesler]

I just launched my autonomous AI company "Heeliq" on @NanoCorpHQ

Verification: glen-jzWz

[Eric Fesler @efesler]

J-1
#sierrezinal

[Matt Raible @mraible]

The @jhipster v8.10.0 release is now available!

🌱 Spring 3.4.4
⛑️ Many internal improvements
🛠️ Build tools upgraded
❤️ Many dependency upgrades

https://t.co/bc2FQj7Aiu

All of our official blueprints have been updated, as well! 😊

#java #jhipster #springboot #angular

[John Carmack @ID_AA_Carmack]

“Coding” was never the source of value, and people shouldn’t get overly attached to it. Problem solving is the core skill. The discipline and precision demanded by traditional programming will remain valuable transferable attributes, but they won’t be a barrier to entry.

Many times over the years I have thought about a great programmer I knew that loved assembly language to the point of not wanting to move to C. I have to fight some similar feelings of my own around using existing massive codebases and inefficient languages, but I push through.

I had somewhat resigned myself to the fact that I might be missing out on the “final abstraction”, where you realize that managing people is more powerful than any personal tool. I just don’t like it, and I can live with the limitations that puts on me.

I suspect that I will enjoy managing AIs more, even if they wind up being better programmers than I am.

[Eric Fesler @efesler]

@omarsar0 @SaveToNotion #tweet #ai

[LlamaIndex 🦙 @llama_index]

A Five Part Series to Building a Full-Stack RAG Chatbot

This is one of the most comprehensive tutorials we’ve seen to help you build RAG end-to-end (algorithms, frontend, backend) - and it’s still ongoing!

Marco Bertelli has published a series of blog posts taking you through this process:
1️⃣ Model Selection
2️⃣ Setting up Flask Backend
3️⃣ Constructing ChatEngine
4️⃣ Optimizing RAG pipeline (agentic reasoning, cost reduction, reranking)

The great thing about it being ongoing is there’s still new content to uncover. Linking the latest article on optimizing RAG below (links to previous sections):
https://t.co/ErQdmpVhr4

[Alex Xu @alexxubyte]

Open-sourcing over 100 byte-sized system design concepts with high-resolution diagrams.

Goals:
- Become a better engineer by understanding how systems work.
- Prepare for system design interviews.

What's included in the GitHub repository:
- 100 byte-sized system concepts with visuals.
- Real-world case studies.
- Tips on how to prepare for system design interviews.

Topics included (and many many more):
- SOAP vs. REST vs. GraphQL vs. RPC
- HTTP 1.0 -> HTTP 1.1 -> HTTP 2.0 -> HTTP 3.0 (QUIC)
- CI/CD Pipeline Explained in Simple Terms
- 8 Data Structures That Power Your Databases
- Top caching strategies
- What does a typical microservice architecture look like?

Start exploring the repository here: https://t.co/keZF9CNuye

If you find it useful, please RETWEET to spread the word. Thank you.

[Nat Sakimura @_nat_en]

Do not create a home grown user authentication protocol using JWT. Use OpenID Connect. JWT was created for it, to start with. (From an author of JWT)

[Deepu K Sasidharan @deepu105]

#JHipster v8 beta 3 has been released. This beta release includes a plethora of new features, improvements, and bug fixes. Includes #JDK 20 and 21 support, #SpringBoot 3.1, #Hibernate 6.2 and so much more...

@jhipster #java #angular #react

https://t.co/K0KwmweVID

[Eric Fesler @efesler]

@milan_milanovic @SaveToNotion #thread #book

[Eric Fesler @efesler]

@KirkDBorne @SaveToNotion #tweet #ml

[Eric Fesler @efesler]

@BrianFeroldi @SaveToNotion #tweet #test

[Eric Fesler @efesler]

@svpino @SaveToNotion #tweet #LLM

[Eric Fesler @efesler]

@svpino @SaveToNotion #tweet #LLm

[Eric Fesler @efesler]

@svpino @SaveToNotion #LLM

[Eric Fesler @efesler]

@svpino @SaveToNotion #llm

[Santiago @svpino]

Scrum is a cancer.

I've been writing software for 25 years, and nothing renders a software team useless like Scrum does.

Some anecdotes:

1. They tried to convince me that Poker is a planning tool, not a game.

2. If you want to be more efficient, you must add process, not remove it. They had us attending the "ceremonies," a fancy name for a buttload of meetings: stand-ups, groomings, planning, retrospectives, and Scrum of Scrums. We spent more time talking than doing.

3. We prohibited laptops in meetings. We had to stand. We passed a ball around to keep everyone paying attention.

4. We spent more time estimating story points than writing software. Story points measure complexity, not time, but we had to decide how many story points fit in a sprint.

5. I had to use t-shirt sizes to estimate software.

6. We measured how much it cost to deliver one story point and then wrote contracts where clients paid for a package of "500 story points."

7. Management lost it when they found that 500 story points in one project weren't the same as 500 story points on another project. We had many meetings to fix this.

8. Imagine having a manager, a scrum master, a product owner, and a tech lead. You had to answer to all of them and none simultaneously.

9. We paid people who told us whether we were "burning down points" fast enough. Weren't story points about complexity instead of time? Never mind.

I believe in Agile, but this ain't agile.

We brought professional Scrum trainers. We paid people from our team to get certified. We tried Scrum this way and that other way. We spent years doing it.

The result was always the same: It didn't work.

Scrum is a cancer that will eat your development team. Scrum is not for developers; it's another tool for managers to feel they are in control.

But the best about Scrum are those who look you in the eye and tell you: "If it doesn't work for you, you are doing it wrong. Scrum is anything that works for your team."

Sure it is.

[Eric Fesler @efesler]

@svpino @SaveToNotion #machineLearning

[Eric Fesler @efesler]

@jeremyphoward @SaveToNotion #thread #chatgpt

[Julien Dubois @juliendubois]

Just upgraded https://t.co/5TxBzLdyqw to the latest @jhipster 8.0.0-beta.1 release, featuring Spring Boot 3 support!
Thanks for sending feedback on this important release!