[–] [S] 2 points 3 months ago (3 children)

I don't quite understand that. I did some research, and I read that the requirements.txt is somehow generated from requirements.in. But what is the difference between the two files then? Could you give me an example of what a requirements.in file would look like?

Thank you!

  • source
  • parent
  • context
  • [–] 4 points 3 months ago (6 children)

    Curious what others have to say, but my go to is to have a requirements.in with direct packages I need for the project, and then run pip-compile to generate all the dependencies with their exact version at the time so that deployments are repeatable. This works well for deployment, but if I were writing a library for others to use, I think you put the direct dependencies in setup.py

  • source
  • parent
  • context
  • [–] 9 points 3 months ago*

    Comp sci and software engineering are 70% the same, the difference is CS is more math and theory oriented, software engineering is hogher level and more about methodologies, software architecture, systems design.

    (Consider any other science discipline vs. Engineering discipline)

  • source
  • parent
  • context
  • [–] 62 points 3 months ago (7 children)

    You know what I'm saying? I have zero interest in using AI to code. It's taking all the fun out of coding and leaving me with only the boring parts.

  • source
  • [–] 4 points 3 months ago

    I did an MSc in Computer Engineering. my uni also had computer science, but it was only a BSc and they did more theoretical stuff. We built hardware, debugged assembly, and studied signal propagation, while they looked at ACID compliance, data deduplication, and high-level architecture. well, we did that too but much less of it.

  • source
  • parent
  • context
  • [–] [S] 17 points 3 months ago*

    My bachelor's was actually called Software Engineering (it was 10 years ago, so it migh've changed a lot), on Faculty of IT. It was mostly just applied programming (but also indepth - from assembly through smalltalk, to bash, C and Prolog), with a lot of courses about SDLC, UML, DevOps, and all that.

    We also had a lot of advanced math, from integrals to logic, and some CS like data structures, algorithms and all that jazz.

    It was not as theoretical as actual Computer Science on other faculties, and was more devops oriented, but I did learn a lot of fundamentals about every language I can imagine, including lambda calcul, and also all the math I could ever need. And I'm pretty glad I was forced to learn about proper processes, am able to read and correctly design an UML, and have some insight into various types of the SDLC - which apparently isn't that common, judging by my experience when actually working. Not that it ever matters - all it ever got me was being internally annoyed that people are using/doing it wrong, but it's not a big deal because everyone understands eachother, and there's no reason to point it out and be smug about it.

    But yeah, CS was mentioned a lot, but the difference was mostly that CS is theoretical and way more math heavy, while SWI is pretty similar in most of the circulum, but instead of obscure theoretical proofs about big O of algorithms, you are learning about UML and SDLC.

    Also, I got to do an Ethical Hacking optional course, which landed me a job in cybersec and started my carrier (before I moved to gamedev), so that's also nice.

    In general, it gave me a lot of "technical soft skills", it was also team project oriented and asked us to have all the requirements and documentations and architecture designs 100% formally written, and that is a really good skill to have.

  • source
  • parent
  • context
  • [+] -6 points 3 months ago (5 children)

    Do people study “Software Engineering”?

    Usually you study Computer Science.

    We had a class called Software Engineering, but it was more about the business process, project management, QA, docs.

    I met someone once who was attending a trade school for some degree or certification or something in “Software Engineering Management.” And this dude wanted to try talking shop with me lol.

    Those are people who probably should be the condom between clod and prod.

  • source
  • [–] 57 points 3 months ago (2 children)

    When you're working on a big enough project, you'll inevitably find yourself acting as a condom between people who don't understand your niche field and the thing you're all building together.

    That's not unique to Claude. However, the fact that Claude can drop big salty loads far faster than you can catch them does present additional challenges.

  • source
  • view more: ‹ prev next ›