[–] 1 point 1 month ago

To be fair, "the boy that cried wolf" has never been a more important story than it is today. There is an epidemic of lying for attention, and it presents as a false victim (its most pathetic form).

  • source
  • [–] 17 points 4 months ago (1 child)

    Easy win for companies that didn't buy into the hype. I'm the only dedicated software dev at my company, so there was no middle manager to foolishly think a chat bot could do my job. We are a small company that can compete with big players, and those big players appear to be floundering. Now, we are expanding.

  • source
  • parent
  • context
  • [–] 9 points 5 months ago* (last edited 5 months ago)

    I think you're mistaking improvements in tooling as improvements in the LLMs. LLMs are plateauing. The idea of exponential growth is an illusion. We took 20+ year old technology, geared it toward text (the LLM), and trained it on the entire Internet. Then, it's popularity grew exponentially.

    This is the hype narrative that Altman, Dario, Jensen, etc. push. They are trying to convince everyone that what we have is the Model T Ford of AI. Just imagine where we'll be in 6 months!

  • source
  • parent
  • context
  • [–] 3 points 6 months ago

    Yup. The problem was never the hardware. It's the stack. We're all carrying supercomputers in our pockets now.

    Feels like so many (dare I say most) programmers don't even understand the work that the OS does to make the C programming environment as nice as it currently is, let alone a 200 line TODO app that uses 6GB of RAM.

  • source
  • parent
  • context
  • [–] 31 points 6 months ago* (2 children)

    That's fucking nuts because any device that can connect to a cloud is powerful enough to run an operating system (they will probably not give user access to the non-volatile memory). Just not the bloated AI spyware box that they want.

    I work in embedded, and you would be surprised how much work a CPU under 100mhz can do when there isn't an operating system/browser in the way. We need to get back to basics in the software industry. We've been going down the wrong road for a looooong time, and the AI bubble is only accelerating us in that wrong direction.

  • source
  • [–] 2 points 6 months ago*

    I feel like this has more to do with what field you work in and what language/paradigm you use. Especially if you're working within some bullshit walled garden, you may not have a choice. I'm a terminal jockey myself, but I mostly program in C, so my code is procedural and to the point. Maybe I might want some fancy smart refactoring feature if I worked in a language where half the code is boilerplate or glue.

    If I have the choice though, I don't see any advantage to an IDE. It's like the combination of many tools rolled into a single, bloated UI with about 60% of their original functionality. And I guess it lets you build "projects" and choose which files will be built. That part never made sense to me. I don't need a program for that! Just delete it dog. It's in the repo!

    IDE:

    • Text editor
    • Source control
    • Debugger
    • Compiler
    • Terminal
    • File explorer

    I'm my opinion, these programs are just better as separate programs.

    (Rant) One thing that grinds my gears... Some IDEs will leave you with the dumbest possible directory structure imaginable. Like actively hostile toward us terminal jockeys. Remember, we are repeatedly typing these things out like cavemen. For example, c/c++ developers who put their headers in a separate, but identical directory structure. Oh and let's do full taxonomy and go 10 directories deep. And what the hell, capitalize random letters and throw in some with spaces into the directory names for good measure. These things don't have to matter to IDE people, but it is something to be mindful of.

  • source
  • submitted 2 years ago* (last edited 2 years ago) by to c/embedded@programming.dev
     

    Hello all, I'm an embedded software guy struggling with Yocto. I'm not asking for assistance as I cannot be saved. Rather, I'd like to make my own. How hard it would be to put a Linux distro onto a device without it? For example, if I were to get a perfectly good distro (let's just say Debian) with the right architecture going in a container. Is there a simple way to combine that with u-Boot, and other crap from a SoC manufacturer to build an image? If that is oversimplifying, I've done Linux from scratch before, and I'd be willing to go that route as well. I guess the issue boils down to the specifics like building the image and anything else that I'm not aware of.

    So, what part of this idea is going to be a lot harder than I'm giving it credit for?

    By the way, I'm aware of Buildroot. This is more for learning purposes, and who knows... maybe I will actually make something out of it.

    view more: next ›