havkom

10 ms·

1.
by havkom 2mo ago
They are great instruction followers in general. This is, one single bad instruction during months of work can mess things up.
2.
by havkom 3mo ago
I am mostly worried about the current AI use in management. I’ve met a few with ”AI hubris” making poor managerial decisions that stem from their poor usage of ChatGPT (not understanding the importance of context, model sycophancy, etc).
3.
by havkom 9mo ago
Some people that are immune to listen to people with more experience will continue to be ”junior” forever. They may eventually not have the title junior, but they really are.
4.
by havkom 9mo ago
There are fundamental differences. Many people expect a positive gradient of quality from AI overhaul of projects. For translating back and forth, it is obvious from the outset that there is a negative gradient of quality (the Chinese whisp
5.
by havkom 10mo ago
My tip is: don’t use SDK:s for agents. Use a while loop and craft your own JSON, handle context size and handle faults yourself. You will in practice need this level of control if you are not doing something trivial.
6.
by havkom 1y ago
What about GLP-1 antagonists to lower inflammation / hs-CRP?
7.
by havkom 1y ago
Does this matter much? Git is a ”distributed source control system”. Are you using git in the wrong way? :)
8.
by havkom 1y ago
Reminds me of C#.. IDisposible and IAsyncDisposible in C# helps a lot to write good mechanisms for things that should actually be abstracted in a nice way (such as locks handling, queue mechanisms, temporary scopes for impersonation, etc).
9.
by havkom 1y ago
I tried: -red and: red-red-red But it did not work and did not get any response. Maybe I am stupid but should this not work?
10.
by havkom 1y ago
What is the difference between them? Both seems like quite trivial implementations?
11.
by havkom 1y ago
Good investigation! Software developers nowadays barely know about transactions, and definitely not about different transaction models (in my experience). I have even encountered "senior developers" (who are actually so called &qu
12.
by havkom 1y ago
The big threat of LLM:s is not the diminishing skills of established skilled developers, but rather the skill set building of junior developers.
13.
by havkom 1y ago
try catch - where you catch the right types of errors at the right level is hard to beat. However, many make the mistake to handle any errors at the wrong level. This leads to really buggy and hard to reason about code and in some cases rea
14.
by havkom 1y ago
Amen!
15.
by havkom 2y ago
How to apply these rules on junior co-workers (who think they know what is best from reading a hyped blog post)?
16.
by havkom 2y ago
Yes. It shines with real problems.
17.
by havkom 2y ago
I have seen tons of ”abstractions” in recently created code bases from ”senior developers” which in actual fact is only titanic-grade mess of complicated ”indirection”. Many people nowadays are unfortunately not fit to work in software deve
18.
by havkom 2y ago
BTW, I am currently working in an enterprise with a small team mixed with experienced developers (heros - but still always learning because of new complexities) and new developers (heros in becoming). Absolutely fantastic and we create won
19.
by havkom 2y ago
Yes. Focus on building all your team members to heros instead. The other way around is possible, but you will end up with a team of 1000 people doing the same work as 10.
20.
by havkom 2y ago
Windows 2000 Professional was the best OS ever. Only downhill from there.
21.
by havkom 2y ago
This looks cool!
22.
by havkom 2y ago
Using these technologies or frameworks may just as well indicate that they are not agile. Nowadays much more common that the wrong technologies are used in the wrong places.
23.
by havkom 2y ago
The document vibe to me is like it is written by some junior engineers who have just read a blog post about the Netflix stack and think they know it all now.
24.
by havkom 2y ago
First parts of the document are pure BS focusing on hype technologies rather than “Agile”. I mean, questions about ”Kubernetes or Docker Swarm?” etc. The last section with flow chart is good though.
25.
by havkom 2y ago
Lots of very strong opinions here what they should have done in terms of code/pipelines/etx from people who have no idea how CrownStrikes stack or build systems works and people who have no clue how to write that type of software
26.
by havkom 2y ago
The doctors example is good, however may not only be health communication between a parent and a doctor but among parents themselves to figure out what action (if any) to take in relation to a condition. The hesitation to effectively commun
27.
"Developerocracy" – A New Challenge for Scandinavia?
6 points by havkom 2y ago|3 comments
28.
by havkom 2y ago
Did they recall the recall product?
29.
by havkom 2y ago
#14401370
30.
by havkom 2y ago
But now with 856+ points on HN about it, it is probably a valuable relic!

More ›