Youtube comments of Jeffrey Phipps (@jeffreyphipps1507).

  1. 113
  2. 79
  3. As a university teacher, I wholeheartedly disagree. Frustration is a terrible tool. Repetition is a good tool. The more your do something with a good outcome, the more fluidly you'll remember it. Frustration breeds psychological blockage. It can even lead to an irrational amount of anxiety. Why should anyone learn that way when there is an easier way. The problem is that traditional math leads people to believe that they are learning something that is useless to them. Theory is often pushed to extreme without real world examples. A person does need to see theory, but people also need to see relatable real world examples (preferably two or three for each concept) so that they can see how it relates to things they already understand. We build our knowledge on foundations of pre-existing knowledge. You can't build your knowledge practically out of thin air. Will you make mistakes? Yes, but it will be for the right reasons - you executed the solution wrong. You'll figure out what you did wrong and try not to do it again. However, that won't be frustration - that's disappointment. It's not the same. If examples trouble you that much, you need to ask questions. Your instructor is PAID to answer your questions. If you need a tutor (though I haven't seen many good tutors) you are paying them for better answers, better examples. These people are paid to answer questions. They may think of you as a pest for asking a lot of questions, but you have the right AND the responsibility to ask questions. Your instructor cannot read your mind. If you are working and you have a question, ask your colleagues to avoid missing the deadline. Missing deadlines costs money. Write down every question you ask in a notebook including the answer that made perfect sense, that "a-ha" moment you finally got it. If you are learning something and you don't understand, try to figure it out. If you haven't figured it out in one hour, stop and ask questions. Here's why, after an hour your chances of finally finding a solution drop 75%. It's like the conundrum of trying to remember how to spell a word - you can think of two ways, but both can't be right (most times), and in fact neither might be right. Your brain can and often does get stuck trying to fill-in unwanted details. You need, as they say, a "new pair of eyes". What you really need is a refreshed brain. Sometimes you can do this yourself. Stuck? walk away for a few DAYS. Then come back. Sometimes the time will reset your view. Just never keep pounding at it for hours on end. That's just wrong and does nothing for your ability to learn. In my 35 years of teaching, I've never seen one instance where frustration helps. I have seen many instances where students refuse to ask for help. I have seen many instances where math is poorly taught.
    67
  4. 29
  5. 25
  6. In other words, learn to identify what your inputs will be, what your outputs will be, and how to go from point a-to-point b before you head to a computer to code. Coding is easy once you know how to develop ideas. I was taught assembly language after being taught how to set out the inputs, outputs, and flow. We had to learn to write steps to go through. What inputs will we need (with output prompts), what outputs from computation will we need, and what computation steps were required to get there? We were first taught via geometry proofs and statistics. Not the best way, but did get me to understand step-by-step via geometric proofs, and a little statistics (mainly for looping). However, I was taught that a simple step-by-step process led you to know where to go next. Don't get bogged down by the big picture, just take baby steps until you get where you are going. When I took assembly language on the mainframe (before all of you young people had home computers), we had to draw flow charts and draw up plans for input/output, then a plan for the program. If that was approved by the instructor, we were allowed to code and then do a desk check - pretend you are the computer, use data, and execute the code line by line on paper. If that was approved, we could schedule time with the card punches (yes, I'm that old) to punch the program and data. Then I took the cards to the system operator (SYSOP) for execution. a few days later you could pick up the cards and the printout. That was the cycle. If you had coded right, you turned in the assignment. If not, you went back to find where you failed. I then took two semesters of COBOL, a semester of FORTRAN, a semester of RPG, a semester of BASIC, and an optional semester of ALGOL or Pascal (I took both - I was paying for it, one more wasn't going to break me). C didn't exist then, I picked it up later. The assembler I took was S/360 BAL, I later got microcomputers and learned 6502 assembler, Z-80 assembler, and ultimately moved to x86+ assembler and I learned Motorola 68K assembler. I have yet to consider learning the newer RISC assembler concepts at my age. I learned many dialects of languages (BASIC, Pascal, C/C++/C#/Java/JavaScript/TypeScript/ECMAScript, RPG/RPG III/RPG400/ILE RPG, database languages leading up to SQL, etc.). I learned new languages like Perl, Python, Ada, Natural, Supernatural, Lisp, Prolog, Logo, Pilot, and so many others that I forget to name here. Then there's shell scripting languages. Early shell languages could not be considered languages per se, but each later generation added necessary structure to make them full scripting languages. Almost 60 years of programming has taught me personally one thing - students in schools don't get the startup understanding they need. They're pushed into a programming language course and onto their computer and told to find answers on the Internet. Regrettably, most examples on the Internet are at best sloppy or at worst wrong. Worse, it gets to the point where programming instructors don't even interact with students and students get stranded in dead-end degrees.
    24
  7. 19
  8. 14
  9. 13
  10. 8
  11. 1. Use your GenEd courses to refine your communication skills. Knowing how to speak, present ideas, and read with understanding is important. You will always need to learn more in whatever field you're in, and you likely won't get it at college - as stupid as it sounds, no matter what your major is you'll never learn enough. 2. Everyone learns differently. Watch videos, take notes, record lectures (where allowed), do a little bit of everything until a pattern emerges that works for you - and find more than one method, because one may not be available sometimes. Also, note taking doesn't have to be super organized at the time. Write a number and scribble down an idea or a page number. Don't get caught in the details. Just write down what it will take to remind you of what the concept was. 3. If you are attending a publicly funded school, remember that the school is motivated to see you graduate. Here's the thing most students don't know: if you are stressed or your life has hit a bump - maybe you got sick for several weeks, the school can provide programs to help you. It may delay your graduation (they may move your classes to another term), or they might find funds to help pay for a single semester, or several other things. Life happens, but schools have programs to help - but you have to tell your advisor and be willing to work with them. Also, if it's just one course you can try asking an instructor for an extension, but it's often better to ask your advisor. The school will then reach out to your instructor(s) to see if they are willing to work with the school. As an instructor, I prefer for the school's retention coordinator to assist in working with the student. It's sort of like a contract between the school and the student to encourage them to not procrastinate. 4. Ask questions - for the love of everything... I have students who either never ask any questions or wait until a deadline before asking questions. Your instructor hates it when you don't ask questions and despises it when you wait until the last second. Seriously. If you ask me early in the week, I have lots more time then and I can take more time to explain extra things you might be missing. I also cannot read your mind. When I taught CompSci in the classroom I walked around the lab when students were there (I'm old - computers where in labs, or terminals for mainframes were in labs). As I walked around in the lab, I could sometimes see that a student was having a problem by the look on their face. However, I teach online now and am completely dependent on students asking questions. If you work on projects for a classroom on a home computer/laptop I'd still not be able to see your face if I wasn't walking around. 5. Modern CompSci is sometimes taught wrong IMHO. There's no explanation as to what comes before you start coding on the keyboard. That's wrong, and far too many schools have brushed that away with RAD tools. Nobody discusses proper GUI development either, or the necessary psychology needed to understand it (even though it'd only take a few minutes to read about some necessary basics in a $5 book on the topic). OK - enough of my rants. I'm not at all sure that getting a second bachelors is worth your money. Most of it will be a recap of GenEd. You'll have around 6-8 courses tied to your engineering degree. You could have taken them separately, unless the GenEd courses were more than five years old. Then you'd likely be required to take them. You might also have been better with certificates covering the same material. Most jobs these days only look to see that you completed some college, then look to see what certificates you have. I'm sure your college didn't tell you that.
    6
  12. 5
  13. 4
  14. As a university instructor, I always stress to students that if you have an error, to not spend more than 15 minutes to solve it. In the real world, there's usually someone to ask. Spending time blending your mind into cheese wiz never helps. It's like when you can't remember how to spell a word then you never will. Even if you don't ask someone for help, taking a break after 15 minutes of struggle, doing something else helps. Play your favorite song, watch a fun YouTube video (watch a funny cat or dog video), or do something fun for for 15 minutes to an hour. You'll likely come back refreshed and maybe even think of one or more solutions. Write them down on a pad of paper. Don't rush back to the computer - you'll probably just forget it. You're absolutely right about this is how to learn, and students spend years NOT learning how to learn. This is complicated by the fact that each level of education isn't the same as another level. To complicate this further, not every student learns the same way except for ONE specific item that you mentioned - experience. However, schools have adopted the erroneous concept that churning out students in short periods of time using certain metrics will accomplish significant learning and students leave thinking they are fully prepared for the workforce. Often, what they really need is a course on various ways to learn and retain information. Learning in elementary school isn't the same as writing a research paper for a PhD. In addition, tools exist for various types of learners that will help them get the experience they need to learn.
    4
  15. 4
  16. 4
  17. 3
  18. 3
  19. 3
  20.  @HansBezemer  Local variables in languages (particularly numbers and memory locations are stored on the stack in any language). Forth is closer to assembly language in that fashion. His description is simply structured programming. All languages are interpreted/compiled down to binary/machine language - your primitives in this case. This brings up a point - a language like C can do OOP, but it gets difficult and ugly. However, C++ didn't compile to machine language originally. It compiled to C and then the C compiler was used to make it into machine language. C++ OOP was converted into the ugly commands in C for use in the C compiler. In math we start with arithmetic. Algebra is merely a group of formulas that save serious quantities of arithmetic being necessary. Similarly, Calculus breaks down the monotony of repetitive Algebra. We use what's appropriate for the job. Still, I've been trained on 40+ programming languages (I'm old) and the one thing I've come to realize is that they are common and get easier and easier to learn. He mentions FORTRAN - heck, that's an easy language to learn. I subbed for a uni teacher for the first class in a course and zipped through the entire book in the night class with a break in the middle. When he came back from his family emergency, all he could talk about was how everybody knew the language. Some languages are easier than others. Many are quite similar if you exclude I/O statements. C/C++/C#/Java/JavaScript/ECMAScript are fundamentally the same - except for their I/O statements. If you change from command line to a GUI, that changes the I/O even more. AND/OR/NOT are command primitives in silicon, in math we call this Predicate Calculus. It's all relative to what we need.
    3
  21. 3
  22. 3
  23. 3
  24. 2
  25. 2
  26. 2
  27. 2
  28. 2
  29. 2
  30. 2
  31. 2
  32. 2
  33. 2
  34. 2
  35. 2
  36. 2
  37. 2
  38. 2
  39. 2
  40. 2
  41. 2
  42. 2
  43. IDE was the successor to hard drives with controllers on ISA ports that were not integrated on the hard drive itself. What you kept calling IDE was parallel ATA (short for ATAPI). This was significant because prior drive controllers required settings in the CMOS to hold the cylinders/heads/sectors for the drive before it could be formatted. The IDE technology hid that information largely or returned it only when requested. The OS needed only know abstract information common to storage, not how to run the device. So initially, it applied to hard drives and tape backup drives. When CD drives came on the scene, they too were separately controlled (usually from the sound card). CD drives were then converted to IDE later, probably a result of sound being added to the motherboard. Making CD drives IDE made sense. It also made them bootable. Somewhere along the line (as you showed on motherboards) we switched from parallel ATA (PATA) to serial ATA (SATA) which had various advantages including speed and improved airflow without ribbon cables. The drives still use IDE to simplify OS interfacing. Prior to IDE, each drive had to have separate drivers added to the OS to interface them to the system. Two different manufacturers or even models within the same manufacturer would potentially lead to two drivers. Adding tape backup required another driver, CD drives yet another. Multiple drivers may conflict or cause other issues. IDE made this simple one driver interfaces all hard drives, tape backup, and CD (etc). The IDE driver identifies the drive and enumerates it. It controls reads and writes (where possible) and does not require a manufacturer driver. The BIOS can boot from the devices because it has base code to do so. USB drives use the USB driver to direct drive transactions to the IDE driver. It acts as a middleman between the IDE drive and the system. This is why some motherboards that recognize USB can boot from external IDE devices, including thumb drives (which are also IDE devices).
    2
  44. 2
  45. 2
  46. 2
  47. 2
  48. 2
  49. 2
  50. As a CS professor at Uni, I am not pleased with either your initial explanation or you first example. Your initial explanation assumes older processor logic or the use of a non-multicore or multi-threading OS. With the proper OS, it is not necessary to discard a section of code because ALL possible predicted code can be loaded into different threading and/or cores. As for the example, one should NEVER use multiple return statements. Structured Programming dictates that all structures including functions should be written such that there is only one-entry/one-exit to guarantee no mistakes are made by the compiler (and I've seen students have problems have problems based on this even as late as the last year). Not all compilers properly resolve this issue. This is a common and sloppy thing that I always have to break students of when teaching recursion. The problem is that returning static variables can work, however the returning of dynamic variable might fail and damage the stack. Switching between upper and lower case without context can be done by logical masking (as you know), but if I am programming in a mid-high level language (and not using the built-in libraries), I don't want to switch to AL just for minimal things. Simply put, if you're willing to shift to processing that your processor is faster doing to optimize for some reason, that's great - but there needs to be a reason. Also, you didn't mention the one way to massively increase mathematical/logical calculations - GPUs are specifically designed for this. Lastly, swapping branching for multiplication may or may not be efficient. Multiplication takes multiple cycles on some processors. Having said that, some optimization is worthwhile.
    2
  51. 1
  52. 1
  53.  @amberjean4044  I don't know if I overheat (though I might). I definitely have issues with words. What you describe as tunnel vision might be related to two issues I experience. One is that I (erroneously) believe that if I do this or that I can stop the seizure. Two, I have a separate thing not directly related to the seizure. Not sure how to describe this. Normally I can focus almost to an OCD level to problem solve. However, if something important pops up, I can drop it and walk away. When I am leading up to a seizure, I'll randomly pick a thing I was working on and laser-focus on working toward a solution. This is bad. It's like starting a second mind-storm in the midst of another. It almost always accelerates the seizure. I've become accustomed to try and push all thoughts out, but that's also a thought. So then I began inserting random thoughts - noise. It doesn't stop the seizure - nothing would. It just stops the acceleration. I live with my sister. If I know I'm working toward a seizure at home, I literally park in the middle of my bed. Pillows, padding - best place for me. If my sister sees me, I apparently look "offline" and she asks if I'm "having problems" If my response isn't what she thinks it should be she marches me to bed. I'm lucky - we have "fluid" lives. I work online and my hours can easily be adjusted. The rest of my life can be readjusted if necessary. The only serious problem for me is that as I need more and more medicine it makes me more tired and this causes the meds to build up tolerances. At some point, the balance tips and the meds no longer work. I'm fast approaching that mark. I may have and out, but it won't be easy or cheap. My epilepsy is caused by a birth defect in my brain. It's increasingly common in late births (my mother was 39 when I was born). However, advances have made it possible to spot on an MRI. Surgery is VERY expensive, but I could end up free of the epilepsy forever. I don't like the idea of poking about my brain, but my doctor happens to be a specialist in this and if I reach the end of meds control - you get the idea. Take care of yourself. Take care of your family in this pandemic also.
    1
  54. 1
  55. 1
  56. 1
  57. 1
  58. 1
  59.  @ianfurqueron5850  One area that hospitals make up the difference is medical reuse. It might sound gross, but tubing, needles, etc. can be sent for sterilization. Although it can never be reused for medical use for humans or even animals, it can be used for other things like mortuary use, training purposes not involving actual medical use. Needles can be used being stuck into fake skin to practice phlebotomy or sewing up wounds long before a student gets to do that on a person. Some medical waste can be recycled. The rest must be destroyed as a bio-threat. Some things are sent home with each patient and are included in your bill. These are fees that your insurance must pay. The costs that insurance will pay may cost more than you could source individually, but cover basic services - every hospital has a handyman department, an IT department, an electrical department/plumbing, engineering - the list goes on and on. Hospitals have check-in people, various people whose jobs are otherwise not listed in the billing. People think the expenses listed are expensive, but averaged across all the personnel and daily expenses, the cost isn't as bad as you would think. In a socialized system, a lot of these costs are absorbed by taxes. Specific additional costs are averaged and absorbed by taxes. Taxes, taxes, taxes. When a country says "we have free health care", that's a lie. They have health care paid for by taxes. "Free" is an illusion paid for by some other action. That doesn't make it something we should demonize or something we should admire. It just is-what-it-is. When we need doctors we hope that they are available. In the first-world nations that's something we typically can rely on. In third-world nations, not so much.
    1
  60. 1
  61. 1
  62. 1
  63. Mine is the "feature" changes I didn't want. Let's take the Snipping Tool or Paint, threatening to replace the simple tool. Would it kill them to simply make a separate tool? I have ZERO need for all the fancy extra features. I'm not saying get rid of the new options, I'm simply saying don't make my simple tool complicated. Make your options in a new tool. You own the source code for crying out loud! I'm less an less sold on the registry. Use it to integrate the OS - I get it (mostly). If you MUST have a database of default apps to open certain files - fine. I have never needed that (coming from the DOS era and before, that was never an option). Opening the program I want an getting the data file from the menu was fine. DLL Hell. I get why this was originally a thing (and why it screwed Windows over again and again). However, today we have enough space to put a dedicated copy in the folder where the program is located so that programs can be both installed/deleted without involving the registry as a rule. Be gone shared DLLs, or find a DLL/library manager that works to disconnect a program from a shared DLL/library. Not being able to fully uninstall programs is the bane of Windows. Programs and Websites designed by idiots. There's a line between clever and garish and MANY programs/websites cross that line. I teach CS. I have to force students not to play excessively with colors, fonts, etc. This is because schools NEVER TEACH UI/GUI DESIGN ANYMORE! When I was a student, the UI had to be practical first, had to meet accessibility requirements, and more. Creativity was what was left AFTER YOU DID THE JOB. Students seem to think that it's their decision what the program looks like - it isn't. It's the decision of the systems analyst who determined the specs. The programmer's job is to write the program in accordance with the specs and within the constraints of the OS. Color themes in an OS are set to meet the needs of disabled (dare I say the PC term "Differently Abled"). One out of eight men are at least partially color blind. Certain colors mean different things in different cultures psychologically (and yes I studied GUI design). Changing the color on a control is also disruptive - the whole idea for a GUI is to make things the same from program-to-program to make using new programs easier to learn. So this all drives me bonkers. Web layout. At the risk of offending web designers, put the products and services at the top so that I don't have to scroll. Like he said in the video, setting a scroll is a pain. Trying to scroll with a skinny bar is hard and scrolling with the wheel can be difficult. Put all the options at the top. Design multiple pages and don't scroll. How's that for an idea? While I join the complaint about skinny scroll bars, WTF is it about programs with tab closing x's that ARE ONLY ACCESSIBLE IF YOU CLICK THE DAMN X??!?!? Yes, I'm shouting! Because of you I have a difficult time closing a tab/program with the mouse. I have tremors. Would it be so bad to make the whole box the x is in clickable??? It's getting to the point where I don't use a mouse for much. The device is becoming almost useless. I can more easily use the keyboard - MOST of the time. Which brings me to the next thing... Just because you have a GUI, don't assume that the mouse is always available. I had a situation arise where the default driver for the mouse croaked/got corrupted - dunno. I do know that no mouse worked, not a wired one and not a cordless one. I used the keyboard shortcuts to get to the device manager to flush the driver and rebooted and a new copy was found at startup that worked. On a job, I had a user who had a six button mouse that he reprogrammed so that finding the right buttons was just impossible. I could have reset it, but he was a client and I just had to install software. Since the GUI prompts for doing that were the defaults, I could use the keyboard and ignore his mouse. It's not that I hate the mouse. It's that I hate that we have gotten to the point where in a few places there is no option for the keyboard. I could go on-and-on.
    1
  64. 1
  65. 1
  66. 1
  67. 1
  68. 1
  69. 1
  70. 1
  71. 1
  72. 1
  73. 1
  74. 1
  75. 1
  76. 1
  77. 1
  78. 1
  79. 1
  80. 1
  81. 1
  82. 1
  83. 1
  84. 1
  85. 1. Python isn't a bad language to start (even if it's still incomplete). However, when I started learning, it didn't exist. I started with BASIC because there were far fewer languages. 2. Learn data types as part of Structured Programming (loops/if-else/sequence) and functions. OOP is not fully supported in Python. It does not implement inheritance nor part of polymorphism requiring inheritance. OOP must implement all three pillars (Inheritance, encapsulation, and polymorphism) before qualifying the language as a fully OOP language. I foresee a time (probably in the not too distant future) when Python will extend itself into the total OOP implementation. As a longtime instructor, the worst thing that I see is that new programmers have no experience with Structured Programming. Without this start, progressing into OOP is dangerous. 3. I agree here - having an interactive environment is very helpful (not unlike BASIC in the past). IDLE does provide this partially, but if you miss one little checkbox at the beginning of installation or have another language installed that supports Python (e.g. VS or VS Code) you might run into conflicts. 4. I agree here as well - unless you practice (and more than once) you'll forget it. The more often the better. I worry that some books and web sites provide horrible examples. In Python, I find the whole "while True:" construct poor quality. For the same number of lines you can do it right and avoid the "break". This construct in Python breeds bad habits that wouldn't be allowed in other languages. 5. Yes - there are details, but don't keep banging your head on the table if some detail eludes you. If you get stuck, and the detail isn't essential, move on. You may well get an exercise that clears it up later. Also, if the basic concept is eluding you, see if someone is available to help. I teach online and remind students constantly - ask questions. I'm here to teach you, you paid tuition whic includes my salary. 6. a. I tell my students to find projects that are interesting/useful and think about that for a final project. In a classroom (physical or online) work with the projects assigned and after you do them play around with them to try the concepts further. Keep practicing all along. Just remember - in a classroom you are expected to follow the specifics of the assignment, however, I want you to keep using what you learn outside of the projects. b. Start small - in classroom assignments we generally start small, however, outside of the assignment practice extending it. 7. Algorithms and data structures are something necessary to take programs to the next level. Eons ago when I was a beginning student, I was expected to figure out how to make a program sort (in FORTRAN). learning how to create these algorithms and data structures helps you to understand how things work - and how to experiment on how to make things better. 8. One gripe I have regarding Python is that sometimes error messages are vague. If you do manage to install an environment like VS Code, you can use debugging tools to help find causes of errors. StackOverflow is generally a decent source, but sometimes the examples are from sloppy programmers (another reason I tell students to ask me questions - I owned two businesses and I've taught programming since the 1980s - there's very few errors I haven't seen). Another minor issue is that Internet access isn't always available. 9. Sometime you may have to learn a newer programming language, a new scripting language to interface with, or even an old language that you need to interface with to update a business (for me it was ALGOL!). Not all businesses use the same programming languages or tools.
    1
  86. 1
  87. 1
  88. 1
  89. 1
  90. 1
  91. 1
  92. 1
  93. 1
  94. 1
  95. 1
  96. 1
  97. 1
  98. 1
  99. I own both an F (which I started with in school) and an M (which came later). The thing I remember most about the F is how heavy it is. I always said that if someone broke into the house that I could grab the keyboard and kill the intruder with it. Yes, it's that heavy. The M was a little lighter - (you'd only put an intruder in the hospital with it - maybe six weeks in traction). I use the keyboards on the respective machines that I now own. On my modern machines I use mechanical keyboards because of medical reasons - I can tell on a tactile key type if I have pressed the key far enough to make it register or if I have accidentally pressed it twice. I have tremors, and this type of keyboard helps. I can also pull the key caps AND the keys to clean it thoroughly. I'm not a keyboard snob per se. I like what works for me. Use what you want. Other than the F, M, and my mechanical keyboard, I have two identical keyboards from MS that for some reason the layout fits my hands perfectly. The key quality is tolerable. I use one on a 486 computer and one (through an adapter) on a Tandy 1000 which I bought before heading off to college after HS. The Tandy keyboard was adequate at best at the time, but the MS keyboard works great with the adapter. I could use a mechanical keyboard, but the MS keyboards were already in my possession. I can't begin to tell how many crappy keyboards I've thrown away and that I still have because they'd work in an emergency. Mostly. I have three "solar" keyboards that take FOREVER to charge. I have two USB wireless keyboards that aren't bad, but with my tremors I really need the keyboard to be mechanical. I did get different color key caps to help separate function keys, Windows, and context key. Makes them easy to spot. It's what works for me. It's funny that the layouts on the C64 I had and the Plus/4 seemed "normal" at the time. Now going back to those two seems really hard. I imagine that's true for users on other retro machines.
    1
  100. My mechanical keyboards DON'T have SysRq. Neither did the Model F. This begs the question - why was it on the Model M? Wait, I just checked the MS Internet Keyboard and it is there. One of the old crappy Dell keyboards has it (I have a walk-in closet of computer parts). Someone traded me a keyboard for something minor or I wouldn't know. I have a keyboard with HUGE letters for the visually impaired and it doesn't have it (though if I needed space on a key cap...). The Tandy 1000 is an odd keyboard. It has 12 function keys and directional arrow keys. However, it doesn't really have the standard organization between the keyboard and the numpad. I don't see SysRq at a glance, but given the layout it could be almost anywhere. I have the machine, I keep the keyboard in case I sell it (not likely - it was my first IBM clone that I owned), but I bought an adapter and connected another MS Internet keyboard to it. The fancy keys are pretty much useless in DOS (without mapping them), but the keyboard is really good. One of MS' best IMHO. On my daily computers, I use Havic keyboards. I have some others in my closet, but it seems about a third have SysRq and the rest don't (probably owing to the fact nobody made use of it). I seem to have a memory of it being used when the computer was used as a terminal (additional hardware/software) on the original IBM enterprise solutions. I think for the 3270 style. I don't remember and I don't know if the system used the key for a similar thing for the 5250s. To long in the mists of time. Kind of a pity. I lived Just north of Boca Raton. Knew lots of IBM people. Maybe it never got used on PCs because of that?
    1
  101. 1
  102. 1
  103. 1
  104. 1
  105. 1
  106. 1
  107. 1
  108. 1
  109. 1
  110. 1
  111. 1
  112. The clean option has four other advantages. 1) Many people don't realize that spyware is installed and the clean install eliminates it. 2) Windows tends to carry forward "sludge" - partial installs, aborted updates, and anything that will slow operations either in files or in registry settings. 3) having the ability to separate data files offline into separate folders and onto multiple copies of media helps organize data and speed retrieval of current data. 4) Re-installation of the OS and the apps makes sure that you have the latest drivers and app versions. You may like the older versions better, but unless you have the older versions to reinstall and plan on being your own tech support for that version, understand that vendors will stop supporting that older version. Using the newer version may be undesirable, but at least you'll have support. ----------- You may also benefit in other minor ways when reinstalling. 1) It gives you a chance to reset passwords. It's a good idea to do that once in a while. I do write them down and stick them in my safe. Using a good password manager will come first, but paper in a safe is good backup. Reinstalling is a good chance to relearn keyboard shortcuts (or learn new ones). If your mouse battery fails, you should always know how to save your work from the keyboard (or vice versa). It might also be a good time to buy a cheap USB corded mouse/keyboard as an emergency backup. All that cordless stuff can fail if the charge fails, but corded stuff can sit in a box for years until needed. Keep multiple backup drives with the same backup. Drives fail. Plan ahead. Do an image backup on multiple drives and/or media. Eons ago when I just started out, I worked tech support on physical machines. First step, ALWAYS, back up the image of the HDD twice - we didn't keep it, but we gave the client the option for a copy. Few took us up on the offer. Those that did were mighty happy when down the road a few months they at least had most of their programs and data. One client went further. They had their computers fitted for automatic backup before shut down and took a copy home. One day vandals destroyed two computers. We built new duplicates the next day and their machines reimaged from the backup and were back up and running in three hours. We had that contract for over a decade. The point here is that you should use a backup image for backup. You should start anew on new hardware and sort out the mess from old setups and data. It will run faster, and you'll be more productive over the long haul. You change machines (hopefully) every three to five years. Spending maybe one/two days starting over and preventing things from breaking is better than the nightmare of trying to "transfer" everything - trust me. Every problem imaginable manifests in a "Transfer".
    1
  113. 1
  114. 1
  115. 1
  116. 1
  117. 1
  118. 1
  119. 1
  120. 1
  121. 1
  122. 1
  123. 1
  124. 1
  125. 1
  126. 1
  127. 1
  128. 1
  129. 1
  130. 1
  131. 1
  132. 1
  133. I've built 100's of computers for a business that needed custom computers. I was working on one of my own and reached up to the top where the power and USB connections are in the case. One of the wires was stuck. I managed to get it loose and yanked my hand out and cut it bad enough to spurt blood all over the inside of the case. Wrap finger/go to ER for stitches. Back when "razor" cases (bad edges everywhere) existed on cheap cases I never cut my hand like that. This case was smooth everywhere - except where it wasn't. As for screw stripping, I feel your pain. I ended up buying my own screws bolts that better fit some holes. Not as much a problem on quality parts, but it still happens. Dropping screws - I made a table out of wood with a half centimeter / quarter-inch (not exact on either) lip ostensibly to keep screws from rolling off. I found that it didn't keep me from accidentally flinging them across the room. I built two computers with RGB and now I'm sick of it - but partially for a reason that I never thought of before. I can (and did) put fans on the front and enjoy the colors. But to see colors on the inside, the machine has to be positioned at and angle where you're looking at the side. Often, I can't see it. Having mobo lighting, lighting on top of m.2, lighting for the RAM, and lighting of the CPU pump on an AIO (let alone the fans) proved frivolous. I'll never build a machine with lighted guts again. I'll just get a case with more side ventilation. Less money, less trouble, less wiring. If you like that stuff - more power to you. It's just not me.
    1
  134. 1
  135. 1
  136. -The seal is on the door frame (if it's not some cheap worthless door). -In houses over a certain size, there is always a foyer -Heating/cooling (HVAC) is common,. Old houses here (like mine) do have radiators (mine is controlled through the HVAC thermostat). There is also radiant flooring. -Those windows are available but are VERY expensive. Also, our average windows also have seals. The glass on good windows is a minimum of double thick with a vacuum gap to prevent temperature transfer. Some decent windows are designed with blinds between the glass to keep them clean (if they get dirty the seal is broken). There are also electric glass windows that can be darkened with just an electric charge (no blinds). -We have light switches that are larger also, but they aren't standard. We also have dimmers. You didn't mention that - Does Germany have those? -I get that the outlets are different, most are. What is the voltage? AC or DC? -Yeah, one of the first things Americans do is change to a different shower head. It's very easy to do. I've done it in every house I've ever lived in. -Personally I HATE single handles because when they wear out the handle it's usually more expensive to replace it. It's also easier to remember what to do to get my perfect temperature. I'm old fashioned though. I DO hate that my bathtub/shower has FOUR handles though! Darn 90 year old house... -I feel that the area you're in is really weird regarding stoves. Most stoves in every state I've lived in have had the ceramic top stoves and more are getting induction stoves. The coils went away largely because they are a fire hazard. If something drops into the drip pans or some idiot turns it on with a cover on it the results can be disastrous. Cooking geeks always want gas. Crazy people. :-) -A lot of Americans definitely want carpet. I have had both. I really prefer wood floors and although mine aren't parquet, they are that color. They need sanding and sealing to protect them when you have pets, but not real often. Laminates need sealing more frequently, but there are more options for looks. Ceramic tile needs to be sealed to prevent the grout from being damaged. -Fenced front yards are frequently illegal in the US because cities typically have right-of-way to maintain electrical, water, sewer, etc. utilities. Houses may or may not have porches - it depends on the style of architecture usually. Mine doesn't, nor do any of my neighbors, but I have seen many Victorian styled homes that do. There are other styles where it is common also. I wish mine did, especially when it's raining. Yards vary a lot on size. Mailboxes in larger cities often don't have the resident's name on them for security reasons.
    1
  137. 1
  138. 1
  139. 1
  140. 1
  141. 1
  142. 1