tag:blogger.com,1999:blog-13465266.post1589483465209772964..comments2018-03-17T02:33:01.899-06:00Comments on Ten Ways to Sunday: Don't Repeat Yourself... Really!Nathan Allanhttp://www.blogger.com/profile/16536035662769805976noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-13465266.post-29467797725880359852018-03-17T02:33:01.899-06:002018-03-17T02:33:01.899-06:00when we will use the idempotent concept in program...when we will use the idempotent concept in programming , in which way it benefit program in any manner , and please give me some real world use of idempotence .Thanks<br /><br />Shea butter soap benefitshttp://mydinnerideas.com/shea-butter-soap-benefits/noreply@blogger.comtag:blogger.com,1999:blog-13465266.post-49774236808304357342018-01-05T12:11:24.838-07:002018-01-05T12:11:24.838-07:00I'm a bit sceptical about this hour of code mo...I'm a bit sceptical about this hour of code movement. Sure it's great to code and all but you need to give people an understanding of what they're working with. The language for example hasn't been defined yet, so for all I know this could be any language until someone tells me what exactly what it is I'm working with. I think that we shouldn't tell people that anyone can do it, I think that we should instead say many can do it but with proper background knowledge. Also another problem arises from this movement which is that if everyone knows how to code in say Java for example, the actual people who have been in the field for a long time will start to make less since knowing Java is less of a rarity. I feel like this is the start of something bad, but I have no way of knowing the future. I just hope that this movement doesn't inspire too many people otherwise finding a job is going to be harder for me and others who have been studying different languages before it was cool. (I'm trying my hardest not to sound like a hipster right now)<br />eu4 console commandshttp://eu4consolecommands.com/noreply@blogger.comtag:blogger.com,1999:blog-13465266.post-58586460592556249062018-01-02T07:19:40.212-07:002018-01-02T07:19:40.212-07:00If you want to see some god-awful WET code, look a...If you want to see some god-awful WET code, look at some Teradyne TestStation In-circuit test programs (.tpg) files. Test generators generate this text file which contains code blocks (tests instructions) for each individual component on a circuit board. If you have 10 identical circuits, with 10 identical IC's, you get 10 identical tests (except for the node names or node numbers). The translator would not compile any function that accepted a node name or node number as an argument. There was no way to assign a node-name or node-number to a variable or pass it to the function used to set relays in the tester, so all connection information had to be hard-coded (almost always by the test generator software). This allows individual tests to be modified or debugged if needed without affecting other "working" tests, but it was a major pain. That was some of the ugliest code I've ever seen. It's sad that most ICT development relies on core software that was first developed in the 1980s and early 90s. They just redesign the interface about every 15 years, but they are still locked into using the same old software with all its inherent problems. In-circuit board testing is a dying industry. As boards become smaller and smaller, there is no room for enough testpoints for a bed-of-nails fixture. Plus, nobody wants to pay $10k for fixture and ICT program to test a $65 board, that will be obsolete in 3 years anyway. Electronics manufacturing is shifting to a production model where the few defective boards they build are just thrown away if they don't pass a functional test. You don't need good test technicians, rework technicians, or anyone who can troubleshoot (along with their higher salaries). That's progress for ya.<br />Read more<br /><br /><br /><br />ark creature id listhttp://arkconsolecommands.com/noreply@blogger.com