• 0 Posts
  • 553 Comments
Joined 2 years ago
cake
Cake day: August 17th, 2023

help-circle

  • Makes the problems of capitalism even worse. Instead of the owner class you get an even smaller political class controlling all means of production - the party leadership. It becomes even more prone to corruption than capitalism.

    Adding to problems is the planned economy - it always results in misaligned incentives, bad allocation of resources, constant shortages…

    Third, possibly the worst, is the constant insistence on ideological purity and severe punishment of “thought crimes”. Or as they like to call it “counterrevolutionary activity”.

    Even though it was created out of good intentions, I don’t believe a lot positive aspects can be salvaged.








  • Liked it while I was working on the technology side figuring out MLOps in a company. Well those were technically ML models but same thing. I also did a small pet project creating an LLM from scratch, that was fun.

    But I see little appealing as a user. I sometimes use it as a glorified search engine, and admittedly can be good at that. Mostly because Google search went to shit. Generated images, songs, videos … so pointless and fake. There is nothing human behind it, I can’t possibly enjoy that content. Talking about “serious” AI “art”. Jokes are a different thing, brainrot memes are kinda good.










  • a full stack developer sufficient in sql and python

    Ok, let me first try to explain what happens on a good day, before going cynical.

    Let’s assume we have an existing system. You go to what for you appears to be a website, fill some text fields, click on a button, etc. In the background a lot of shit happens. Typically the backend part of the system consists of tens of services each doing it’s own thing. Some participate in returning a response to you, the user. Others just process data further for analytics, security, etc.

    One day someone (in most companies a product manager, or a UX researcher) comes up with an idea for a new feature. A user should be able to do XY. And of course pay for it.

    That’s where you step in. Since you mentioned full stack, you will need to do everything.

    • Create a new page with forms, buttons, nice colors and pictures on the frontend
    • Accept the result of user actions of the above to an API in one of the services mentioned
    • Save the data into a database (this is where SQL comes into play)
    • Retrieve data from a database (SQL again)
    • Emit various events or API calls to other services, informing about what just happened

    This is all done with code. You can copy/paste, vibe code, just type it yourself. Code is the least of your concern. Making sure it all works together is what’s tricky. You will go through several iterations until you get it right. Then you write automated tests for it (TDD people don’t come at me).

    Also you communicate to other people in the company about any dependencies and overlaps with what others are doing. Finally, you can deploy the code to production which will make it available globally to users.

    I just described about 50% of the programmer job. I didn’t mention code reviews, architecture discussions, plannings, retros, communities of practice, incident handling, herding cats…


    This is all valid in a good case scenario. good company and a good organization in it.
    In reality it’s mostly waiting. A lot of waiting. Despair if you can’t make it work. Happiness if you can. Then despair again because all you do is pointless. A lot of fighting against the system designed to make you as unproductive as possible. Or just giving up and faking it for a paycheck.