Conversation started Nov 10, 2016 at 22:36.
Nov 10, 2016 22:36
@amon Thanks for the reply, those are some interesting points, I think it's interesting to hear those 4 as separate concepts instead of just lumped together
@Tom a SATA to USB bridge could work as well, plug it into another (Windows) computer and it's just like any other external drive, I tend to carry one of those in my backpack these days.
Alternatively if he's enabled file sharing there's some fine print that causes Windows to share your entire user folder by default, so all you have to do is type in the computer's ip address into windows explorer and you're in.
@amon Also in case you're interested, on the project I'm on, I felt that OOP as a design philosophy (i.e., treating real world things as objects) works OK sometimes; sometimes I found it very counter-intuitive (for me the
dog
example just seemed to introduce a lot of room for misinterpretation). As a design goal, I'm not ready to make a conclusion (I'm still reading)... Nov 10, 2016 23:00
I've worked with some really nice procedural codebases, but the OOP-ish? codebases that I've seen didn't really seem all that uncoupled or modular (e.g., all of them had the gorilla/banana/jungle problem and some even worse problems) , I'm still sort of hoping to find either a really good OOP codebase that achieves those design goals as an example, or some kind of book that goes into enough detail for me to implement it on my own.
Nov 10, 2016 23:40
@jrh In my experience, OOP is generally overdone. Either there's too much inheritance, or too much coupling, or just too much. Software problems tend to be solved by piling more software on top of the existing software... things like DI containers and ORM's. The GOF book is practically a study on how to pile more software on top of software to solve problems.
Conversation ended Nov 10, 2016 at 23:57.
OOP Pt 2
Nov '1610
The Whiteboard
General Discussion for softwareengineering.stackexchange.com P...
Participants
- jrh 66%
- Robert Harvey 33%
all times are UTC