0 Members and 187 Guests are viewing this topic.
Quote from: tautech on June 19, 2019, 11:10:14 pmMomentary Lapse of Reason in the background as we speak ! I have those all the time.
Momentary Lapse of Reason in the background as we speak !
Quote from: med6753 on June 19, 2019, 10:44:17 pmWith copious amounts of volume...
If I had hi-fi like that SWMBO would be mega pissed and I'd be sleeping with the neighbours dog
This is great until you want to actually get something done working with other people. THEN the agreed-upon construct becomes VERY important; you can either take the time to become conversant in one of the popular programming constructs, or be ready to teach everybody you work with how to program in YOURS.
Quote from: mnementh on June 19, 2019, 10:46:22 pmThis is great until you want to actually get something done working with other people. THEN the agreed-upon construct becomes VERY important; you can either take the time to become conversant in one of the popular programming constructs, or be ready to teach everybody you work with how to program in YOURS.That's why an IDE's "auto format" operations are so valuable: you can convert other people's stuff into stuff you can read. Some languages make that easier and more complete, others less so.But the important point is the extent to which the syntax allows the tools to catch or highlight errors.
Quote from: tggzzz on June 20, 2019, 07:32:58 amQuote from: mnementh on June 19, 2019, 10:46:22 pmThis is great until you want to actually get something done working with other people. THEN the agreed-upon construct becomes VERY important; you can either take the time to become conversant in one of the popular programming constructs, or be ready to teach everybody you work with how to program in YOURS.That's why an IDE's "auto format" operations are so valuable: you can convert other people's stuff into stuff you can read. Some languages make that easier and more complete, others less so.But the important point is the extent to which the syntax allows the tools to catch or highlight errors.Not forgetting that you yourself will be 'other people' when you come to look at your code in a few month's time...
Quote from: nfmax on June 20, 2019, 07:38:42 amQuote from: tggzzz on June 20, 2019, 07:32:58 amQuote from: mnementh on June 19, 2019, 10:46:22 pmThis is great until you want to actually get something done working with other people. THEN the agreed-upon construct becomes VERY important; you can either take the time to become conversant in one of the popular programming constructs, or be ready to teach everybody you work with how to program in YOURS.That's why an IDE's "auto format" operations are so valuable: you can convert other people's stuff into stuff you can read. Some languages make that easier and more complete, others less so.But the important point is the extent to which the syntax allows the tools to catch or highlight errors.Not forgetting that you yourself will be 'other people' when you come to look at your code in a few month's time...In most respects, yes - but not in this respect. I always format and save my code in The One True Way, and that hasn't changed in decades
Quote from: tggzzz on June 20, 2019, 07:52:09 amQuote from: nfmax on June 20, 2019, 07:38:42 amQuote from: tggzzz on June 20, 2019, 07:32:58 amQuote from: mnementh on June 19, 2019, 10:46:22 pmThis is great until you want to actually get something done working with other people. THEN the agreed-upon construct becomes VERY important; you can either take the time to become conversant in one of the popular programming constructs, or be ready to teach everybody you work with how to program in YOURS.That's why an IDE's "auto format" operations are so valuable: you can convert other people's stuff into stuff you can read. Some languages make that easier and more complete, others less so.But the important point is the extent to which the syntax allows the tools to catch or highlight errors.Not forgetting that you yourself will be 'other people' when you come to look at your code in a few month's time...In most respects, yes - but not in this respect. I always format and save my code in The One True Way, and that hasn't changed in decades Apart from my early Apple Basic when I hit Uni you learned structure and formatting or your Fortran and Pascal programming got belted for marks when submitted. Not to mention it was always easier to help others with finding how they put a loop into the code that brought the HP9000 'regularly' to a standstill in particular the night before assignments were due Even simple micro stuff I still format even though no one else sees it.
That's a pet hate of mine. ARRL are the worst:
... but I've seen even worse A thoughtfully-drawn schematic makes me think the developer knows what they are doing. A poorly drawn schematic makes me think the developer is using voodoo or cargo-cult design.Maybe somebody should startup a "WTF schematic" thread or website.
Quote from: kj7e on June 19, 2019, 11:13:00 pmQuote from: tautech on June 19, 2019, 11:10:14 pmMomentary Lapse of Reason in the background as we speak ! I have those all the time.Isn't that exactly the reason for this thread ?
Yup.Regrettably there is an electronics equivalent to strangely formatted code: schematics that don't use common conventions for how sub-circuits are layed out.Classic examples are signal flow from right to leftopamp circuits with the ancillary components in strange positionsdigital circuits where the components aren't connected by wires, just by named stubstransistors in strange orientationsschematics drawn like PCB layouts
That's a pet hate of mine. ARRL are the worst:The 4.7/47k are the bias divider for the damn thing, Cf is bypassing the 4.7k resistor, C2 is resonant with T1. Who would have guessed? It gets even worse when you look at phasing on some of their transformers as they've drawn one tap upside down to bring the power from the South and then drawn phasing dots to correct it?!!??
Quote from: mnementh on June 19, 2019, 02:34:45 pmQuote from: tggzzz on June 19, 2019, 07:45:53 am(SNIP)Nonetheless, all techniques and technologies can be and are misused. Good taste is important, and rare. Some people should never be let near a keyboard.Hey... I resemble that remark!!! I wasn't thinking of you in that respect. But in true post-modern-lit-crit style, now you've made me think...Worth speed-reading, from http://www.fudco.com/chip/deconstr.html :QuoteHow To Deconstruct Almost AnythingMy Postmodern Adventureby Chip MorningstarJune 1993"Academics get paid for being clever, not for being right."-- Donald NormanThis is the story of one computer professional's explorations in the world of postmodern literary criticism. I'm a working software engineer, not a student nor an academic nor a person with any real background in the humanities. Consequently, I've approached the whole subject with a somewhat different frame of mind than perhaps people in the field are accustomed to. Being a vulgar engineer I'm allowed to break a lot of the rules that people in the humanities usually have to play by, since nobody expects an engineer to be literate. Ha. Anyway, here is my tale.....
Quote from: tggzzz on June 19, 2019, 07:45:53 am(SNIP)Nonetheless, all techniques and technologies can be and are misused. Good taste is important, and rare. Some people should never be let near a keyboard.Hey... I resemble that remark!!!
(SNIP)Nonetheless, all techniques and technologies can be and are misused. Good taste is important, and rare. Some people should never be let near a keyboard.
How To Deconstruct Almost AnythingMy Postmodern Adventureby Chip MorningstarJune 1993"Academics get paid for being clever, not for being right."-- Donald NormanThis is the story of one computer professional's explorations in the world of postmodern literary criticism. I'm a working software engineer, not a student nor an academic nor a person with any real background in the humanities. Consequently, I've approached the whole subject with a somewhat different frame of mind than perhaps people in the field are accustomed to. Being a vulgar engineer I'm allowed to break a lot of the rules that people in the humanities usually have to play by, since nobody expects an engineer to be literate. Ha. Anyway, here is my tale.....
You are on the lucky side of the fence. The entire field is a throbbing soul consuming mental disorder on wheels. You’re not dumb; we are. You’re the clever one not prostituting your mind out!
Quote from: med6753 on June 19, 2019, 07:59:11 pmI'm sitting here watching this discussion whiz by WAY over my head. You guys have a habit of making me feel dumb sometimes. +1 You're not alone med.
I'm sitting here watching this discussion whiz by WAY over my head. You guys have a habit of making me feel dumb sometimes.
It has been an extremely frustrating day but at least now I know what I'm up against. Been working on the 7904 all day. I mentioned the other day that it started going into intermittent "tick" mode on the power supply. Well it finally died completely. Won't power up at all and the supply is ticking like mad. The parts to recap the preregulator in the supply finally showed up this afternoon so I completed the recap. Put it all back together and the damn thing still won't power up. None of the supply voltages show any shorts. Just for giggles disconnected the HV anode lead from the supply to the CRT. Aw shit....the scope powers up. All the DC supply voltages are in spec. We have a problem in the HV area, probably a FUBAR tripler. But at least now I know where the trouble is. Right where I DON'T want to screw around but I guess I have no choice. Oh well. I'll pick back up on the mess tomorrow. And to add to today's fun and games found several instances where the scope no match the manual. That leads you down the wrong path for a while.
Quote from: med6753 on June 20, 2019, 08:49:53 pmIt has been an extremely frustrating day but at least now I know what I'm up against. Been working on the 7904 all day. I mentioned the other day that it started going into intermittent "tick" mode on the power supply. Well it finally died completely. Won't power up at all and the supply is ticking like mad. The parts to recap the preregulator in the supply finally showed up this afternoon so I completed the recap. Put it all back together and the damn thing still won't power up. None of the supply voltages show any shorts. Just for giggles disconnected the HV anode lead from the supply to the CRT. Aw shit....the scope powers up. All the DC supply voltages are in spec. We have a problem in the HV area, probably a FUBAR tripler. But at least now I know where the trouble is. Right where I DON'T want to screw around but I guess I have no choice. Oh well. I'll pick back up on the mess tomorrow. And to add to today's fun and games found several instances where the scope no match the manual. That leads you down the wrong path for a while. Here's some guidance for ya:https://www.eevblog.com/forum/repair/tek-7704-pops-and-clicks-image-compressing-for-a-moment/msg940524/#msg940524Follow all the links.
@med I remember when Corona also meant a fizzy drink and they used deliver it round the estates like a milkman.