• 3 Posts
  • 92 Comments
Joined 3 years ago
cake
Cake day: June 25th, 2023

help-circle



  • One day I mentionned this rule while having a dinner with friends. One of them was a woman I met fir the first time.

    It turned out his husband was way older than this rule allowed when they met. And now that the rule is fine, she didn’t felt bad about her husband.

    Seriously, I felt so shitty. Let people loves who they love without discrimination as long as this is consensual between adults.








  • From my experience of boss looking at people working. Working hard is by a huge margin a lot better than working smart. Trust me I know my shit. Once I even wrote a formula in Excel! /s

    That being said with experience you stop using anecdotes, easy pre-made sentences like “premature abstraction/optimisation is the root of all evil!” and you understand that there are no generic solutions and you need, every time, to think hard about the best way to produce something relatively to the context and constraints which, most of them, aren’t technical but organizational and human related.

    And also, if you intend to work on a project more than 6 months. Quality is really worth it. The lack of quality works like accumulating mud. After a while, you are stuck, and the next step will require a huge amount of energy.




  • yogsotothtoPeople Twitter@sh.itjust.worksLearning on the job
    link
    fedilink
    arrow-up
    3
    arrow-down
    1
    ·
    6 months ago

    Before ; someone with a salary did some work.

    After ; you the customer do the work, are not paid for it, forced to see ads, and naturally more and more steps will be added. (do you want to give to charity? do you want our premium card? what is your city? and other bullshit).

    Sorry but I refuse to self checkout. Pretty often if there is only self checkout I left everything in place for the staff to put again in the store.

    If I am forced to use them, I am already in such bad mood that I make my best to make the experience as terrible as possible. I lie systematically to any question, I tend to make mistakes, wait for someone to come. Mainly, I try to make it worse economically.

    How in one generation people have accepted to work for free. Not for me.


  • I didn’t see Claude 4 Sonnet in the tests and this is the one I use. And it looks like about the same category as o4 mini from my experience.

    It is a nice tool to have in my belt. But these LLM based agents are still very far from being able to do advanced and hard tasks. But to me it is probably more important to communicate and learn about the limitations about these tools to not lose tile instead of gaining it.

    In fact, I am not even sure they are good enough to be used to really generate production-ready code. But they are nice for pre-reviewing, building simple scripts that don’t need to be highly reliable, analyse a project, ask specific questions etc… The game changer for me was to use Clojure-MCP. Having a REPL at disposal really enhance the quality of most answers.



  • He looks from company money perspective. And I think AI is difficult to monetize. A google paper explained a long time ago that big company cannot easily have a huge competitive advantage because new techniques exists in the open source world to learn incrementally on top of costly models. Mainly you don’t need millions to make another good quality LLM.

    That being said. LLM add some value, but as everything hyped to no end the real value is negligible comparatively to the « market expected value ».




  • Moreover, codebase in pure funcional languages is hard to understand and maintain, that’s why they are rarely used in production.

    hahahah how to trigger a lot of people working with these pure functional languages (like me).

    I’ve worked with both “normal languages” like C++, java, Perl, javascript (node + UI), etc… and then I switched to Haskell and Clojure. And our current production code is a LOT better than in traditional languages. In particular, maintenance is a lot cheaper that what I was used to when working with more traditional languages.

    Regarding the community impact I would advise to use Clojure instead of Haskell (or Purescript, or Elm). Clojure is a nice middleground that has a huge advantage of being very stable (by that I mean, the code you write today will probably be very easy to deploy in 10, or 20 years from now).

    Note however, the language alone is not sufficient to write good code, but it helps you choose better abstractions that will be easier to maintain. If you dive into the spirit of the language, you will have a better intuition and understanding about state management of big applications and will probably make more visible some design issues.