- 0 Posts
- 13 Comments
4·7 hours agoReally went downhill after volume 3. You hope that they’ll get back on course by volume 6 at least, but alas.
Not if it is filled to the brim with 3 TB of porn
Horseshit. Computers aren’t tools for a software engineer. Computers are tools to an administrator, an accountant. Computers are the sandbox you are building castles in as a software engineer. If you don’t understand the system upon which you build, its abilities and features, its limitations, it’s dependencies, you are going to make some stupid mistakes.
You need to understand discrete mathematics as a consequence of computer computation. You need to understand parallel processing and threading for muli-core processors. You need to understand networking, package management, security vulnerabilities, etc. from different architectures and protocols. And it ALWAYS helps to understand the very basics of a computer’s functioning, from hardware, CPU architecture, machine code, assembly/low level programming, memory management, etc.
print('Hello, World!) is day one shit for a reason. Programming language and logic is the basics. The real expertise comes from your 3rd and 4th year materials. Databases, architecture, theory of computation, discrete mathematics, networking, operating systems, compilers, etc.
My CS degree had a hardware/IT support class, but A) it was entirely simulation based. We never touched any actual hardware. We “built” PC’s or identified physical issues in 3d sim software, set up RAID arrays in software, etc. B) it was super hand holdy and you only ever go over a problem once, so nothing on the class has stuck. I know much more from having built, troubleshot and maintained my own computers and network than I ever learned from that class, then learned more by doing in an actual IT support position before becoming an engineer.
This shit sounds like when you’re mom tells you that the Facebook printed out her bank statement on the tax machine. I’m not smart enough to even guess how you did something dumb enough to make that happen.
How bad are you at writing queries? How does your hard drive overheat even under 100% load? Do you have it smothered under a blanket? Did you crack it up and expose it to cheeto dust? What does running a query on your, presumably, remote database even have to do with your harddrive in the first place? Are you trying to copy the entire database locally to a laptop? Do you know how to tie your shoes yet, or are you still on the velcro?
8·4 days agoPrivate premium platform curated it’s programming to it’s audience’s interests.
CENSORSHIP! YOU’RE OBLIGATED TO PROMOTE MY INTERESTS AND IDEALS!
9·5 days agoThe average person has slightly less than half a penis, one testicle, half a vagina and uterus, and one ovary. No one is average.
302·5 days agoIt feels like Chinese windmills with backdoor controls from the Chinese government is both a crazy idea and pretty easily solved. Just rip out and replace whatever remote control system is in it. Unless it’s wired to a bomb, worst case scenario they shut it down while you manually restart them.
I guess I’m an awesome nerd!
Javascript should say “you are a masochist and a nerd”
Javascript Standards Team is such an Oxymoron.
Depends on your degree. CS is meant to be theory heavy. If your degree is for Software Engineering, it should focus more on pragmatic skills, team projects, etc. Either way, certain theory should still be taught to support those skills. But yes, with Computer Science you are definitely going to learn a broader set of theory with less focus on software development.
If all you intend to ever do is code or manage development projects, go SE. It’ll give you a more direct leap into that pool. CS gets you access to more pools, but because of that broader access, you only get your foot wet in most of them. They leave it up to you to expand your own knowledge and experience in those areas that interest you. And to be fair, that’s basically always the recommendation or expectation in tech no matter your degree. You can seek certifications, courses, or boot camps, or otherwise learn about new technologies, build a portfolio of projects, spend time unskilling. My employer gives us a full paid day every 6 or 8 weeks that we are meant to use specifically upskilling in some way. And my boss encourages us to do that on Friday afternoons too.
My point is that there is value in the CS approach. Getting a taste of different avenues you could go down, a broad set of knowledge seeded that you can grow, and a penchant for learning concepts that you will use for the rest of your career anyway are all good things. And whatever gap in your knowledge you have, you can learn about when the job calls for it or by playing around with your own projects in your free time. That goes for SE too.