Podcasts about testability

Hello and welcome to episode 125 of the Testing Peers podcast.This time, joining Chris, Russell and David is the returning guest host, Al Goodall.Before diving into the main topic, Al asks the group to think about book collections, a nice mix of techno-thrillers and classic prose on offer.Russell kicks off the main discussion around testability, what is it in which context?The Peers talk through implementation, pitches, prompts, value, maintainability and more.Chris also brings out the TestSphere card deck to look at the Testability Quality Aspect card.What does Testability look like in your context? Have we mastered it? What can we do better? The Testing Peers Conference is happening on the 13th March 2025.Tickets available here: https://testingpeerscon.com/ticket/If you wish to Sponsor the conference: https://testingpeerscon.com/partners/If you wish to volunteer for the event: https://testingpeerscon.com/volunpeer/contactUs@TestingPeers.comTwitter (https://twitter.com/testingpeers)LinkedIn (https://www.linkedin.com/company/testing-peers)Instagram (https://www.instagram.com/testingpeers/)Facebook (https://www.facebook.com/TestingPeers)We're also now on GoodPods, check it out via the mobile app storesIf you like what we do and are able to, please visit our Patreon to explore how you could support us going forwards: https://www.patreon.com/testingpeersThanks to our brand new sponsors – NFocus Testing.nFocus are a UK based software testing company. They've been supporting businesses for 24 years by providing services that include burst resource, accelerated test automation, performance testing and fully managed testing services. In 2021, they launched a Test Automation Academy to create amazing testers and they've now created jobs for 48 people in our industry in just under three years!nFocus were a big part of PeersCon in 2024, really grateful for all they do supporting the Testing Peers.www.nfocus.co.uk and info@nfocus.co.uk for anyone wanting to get in touch.Support the show

In this episode of Environment Variables, host Chris Adams dives into the evolving landscape of sustainable web development with Alexander Dawson and Tzviya Siegman from the World Wide Web Consortium (W3C). Dawson and Siegman discuss the W3C's efforts to develop Web Sustainability Guidelines (WSG), a comprehensive set of evidence-based practices aimed at reducing the environmental impact of web technologies. They explore the creation and potential impact of these guidelines, especially as global interest grows in embedding sustainable practices within web standards. The episode also covers the challenges of driving adoption across public and private sectors, the role of testability in sustainability guidelines, and future directions for standards that minimize digital carbon footprints. This engaging conversation provides listeners with insights into how W3C's sustainability initiatives could shape the future of the web.

Topics covered in this episode: 2024 PSF Board Election & Proposed Bylaw Change Results SATYRN: A modern Jupyter client for Mac Incident Report: Leaked GitHub Personal Access Token Extra extra extra Extras Joke Watch on YouTube About the show Sponsored by Code Comments, an original podcast from RedHat: pythonbytes.fm/code-comments Connect with the hosts Michael: @mkennedy@fosstodon.org Brian: @brianokken@fosstodon.org Show: @pythonbytes@fosstodon.org Join us on YouTube at pythonbytes.fm/live to be part of the audience. Usually Tuesdays at 10am PT. Older video versions available there too. Finally, if you want an artisanal, hand-crafted digest of every week of the show notes in email form? Add your name and email to our friends of the show list, we'll never share it. Brian #1: 2024 PSF Board Election & Proposed Bylaw Change Results New board members Tania Allard KwonHan Bae Cristián Maureira-Fredes Congrats to new board members If you want to consider becoming a board member, there are 4 seats up for vote next year. All 3 bylaw changes passed, by a wide margin. Details of changes Change 1: Merging Contributing and Managing member classes Change 2: Simplifying the voter affirmation process by treating past voting activity as intent to continue voting Change 3: Allow for removal of Fellows by a Board vote in response to Code of Conduct violations, removing the need for a vote of the membership Michael #2: SATYRN: A modern Jupyter client for Mac A Jupyter client app for macOS Comes with a command palette LLM assistance (local or cloud?) Built in Black formatter Currently in alpha Business model unknown Brian #3: Incident Report: Leaked GitHub Personal Access Token Suggested by Galen Swint See also JFrog blog: Binary secret scanning helped us prevent (what might have been) the worst supply chain attack you can imagine A GitHub access token found it's way into a .pyc file, then into a docker image. JFrog found it through some regular scans. JFrog notified PYPI security. Token was destroyed within 17 minutes. (nice turnaround) Followup scan revealed that no harm was done. Takaways (from Ee Durbin): Set aggressive expiration dates for API tokens (If you need them at all) Treat .pyc files as if they were source code Perform builds on automated systems from clean source only. Michael #4: Extra extra extra Python 3.13.0 beta 3 released Ice got a lot better I Will Piledrive You If You Say AI Again | Prime Reacts Video Follow up actions for polyfill supply chain attack Developer Ecosystem Survey 2024 Code in a Castle still has seats open Extras Brian: A new pytest course in the works Quick course focusing on core pytest features + some strategy and Design for Testability concepts Idea everyone on the team (including managers) can take the new course. 1-2 people on a team take “The Complete pytest Course” to become the teams local pytest experts. Python People is on an indefinite hold Python Test → back to Test & Code (probably) I'm planning a series (maybe a season) on TDD which will be language agnostic. Plus I still have tons of Test & Code stickers and no Python Test stickers. New episodes planned for August Joke: I need my intellisense (autocomplete)

What company just made available a free version of their AI testing software? Want to know why Testing AI Doesn't Have to be Alarming? And what performance testing tool now works with Playwright? Find out in this episode of the Automation in DevSecOps New Shows for the week of June 11th. So, grab your favorite cup of coffee or tea, and let's do this.

Watch on YouTube About the show Sponsored by InfluxDB from Influxdata. Connect with the hosts Michael: @mkennedy@fosstodon.org Brian: @brianokken@fosstodon.org Show: @pythonbytes@fosstodon.org Join us on YouTube at pythonbytes.fm/live to be part of the audience. Usually Tuesdays at 11am PT. Older video versions available there too. Michael #1: pystack PyStack is a tool that uses forbidden magic to let you inspect the stack frames of a running Python process or a Python core dump, helping you quickly and easily learn what it's doing. PyStack has the following amazing features:

show notes upload upon reciept

Can we free ourselves from stale ideas about consciousness?Looking for a link we mentioned? It's here: https://linktr.ee/philosophyforourtimesSome argue that the reality we perceive is a controlled hallucination. Others claim that science is about to crack the ancient problem of the self once and for all. Distinguished philosopher and panpsychist Philip Goff argues that neither of these are true, and explains why we need a new theory altogether.Philip Goff is a renowned philosopher of consciousness at Durham University. His unique research focuses on integrating consciousness into our scientific worldview.There are thousands of big ideas to discover at IAI.tv – videos, articles, and courses waiting for you to explore. Find out more: https://iai.tv/podcast-offers?utm_source=podcast&utm_medium=shownotes&utm_campaign=breaking-through-the-consciousness-stalemateSee Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

India Policy Watch #1: Silver Linings PlaybookInsights on burning policy issues in India- RSJHello Readers! We are back after a nice, little break. Things have changed a bit in the past four weeks; haven’t they? Stock markets around the world are down by 10 per cent. Central banks have hiked interest rates by 40-50 bps. Inflation in the US is running at a 40-year high of over eight per cent. Retail inflation in India at 7.79 per cent is beyond the zone of comfort for RBI. The Rupee hit an all-time low last week. Technology stocks are down all over the world and the deal pipeline in the digital startup space has all but dried up. Musk is buying Twitter or maybe he isn’t. NFTs are dead and buried and crypto valuations are in a funk (or in a death spiral as Matt Levine puts it). And no one really knows anything about the Ukraine war. It drags on like a Putin-shaped monster waddling its way through the spring rasputitsa with no hope of getting anywhere. Such then are the vagaries of the world.  Thankfully, the Indian news channels were debating more important issues during these times. Like loudspeaker bans in religious institutions. Like a videographic survey of a Varanasi mosque by a 52-member team. Or if the Taj Mahal was indeed a Shiva temple called Tejo Mahalaya before Shah Jahan, that undisputed emperor of large tracts of Hindustan in the 17th century, figured he had run out of land to build a mausoleum in memory of his late wife. Or if Sri Lanka was more in the dumps than us in these times. These things matter. So they must be investigated by the intrepid reporters sitting in the studios. We must be forever thankful for the oasis of assurance that Indian news channels offer to us in this volatile and uncertain world.Anyway, coming back to the point, things have turned for the worse since we last wrote on these pages. Yet, amidst all the talks of a recession or stagflation, I believe there’s some kind of silver lining for India if it plays this situation well. Sweet Are the Uses Of InflationFirst, let’s look at the inflation and the rising interest rate scenario. India didn’t go down the path of expanding the fisc by doling out cash incentives at the peak of Covid induced distress in the economy. Much of the “20-lakh crores package” that was announced in May 2020 was either repurposing of the existing schemes or putting a monetary value on loans, subsidies or free food that was offered to the people. So, while the RBI cut rates and increased liquidity, the supply of money in the system and the government balance sheet didn’t bloat like those in the US and other western economies. The upside of the US model was that the economy rebounded faster, it began running at almost full employment and people who got Covid relief checks started spending as the economy opened up. The downside is an overheated economy that now needs to be cooled down but that comes with its consequences. The war in Ukraine and the resultant rise in oil and commodity prices have queered the pitch. So, for the first time in a long, long time the Fed has had to raise rates while the markets are falling. In 2022, the global rich have lost over a trillion dollars already as markets have fallen while the poor have had their wage increases outpace inflation. There’s less K-shaped recovery discussions in the US happening today. Anyway, these are new scenarios for an entire generation raised on rising stocks, low inflation and low-interest rates. This will be a hard landing for them. In the model that India followed, on the other hand, there was real distress in the rural and informal economy because of the absence of a direct cash transfer scheme during the pandemic. As the economy opened up, there were supply chain disruptions that hurt multiple sectors. The rise in oil prices because of the war added to the inflation. But there is an important difference between our inflation and that of the West. It is more a supply-side issue for us. A few rate hikes, some stability in oil and commodity prices and our continued diplomatic balancing act that will help us with cheap oil from Russia should stabilise things. We could be looking at a transitory elevated inflation for a few quarters rather than something more structural. Also, we have a much greater headroom to control inflation by raising rates. The repo is at 4.4 per cent after the out-of-turn increase by RBI last week. It is useful to remember as late as mid-2018, the repo was at 6.5 per cent and that didn’t look like a very high rate at that time. So, the RBI has another 150-200 bps of flex to tame inflation without seriously hurting growth, unlike the West. And that is only if the inflation prints get into the teens. That looks unlikely. So, what’s in store for us? We will continue with the trends we have seen so far: a K-shaped recovery that will hurt the poor more, the formalisation of the economy will mean the published numbers of GST collections or income tax mop-up will be buoyant, the food subsidy and other schemes started during the pandemic will continue for foreseeable future and we might get away managing to keep inflation down without killing growth.Second, the structural inflation in the western economies will mean they will have to take a couple of long-term calls. The discussion on the first of these calls is already on with an urgency markedly different from what it was six months back. How to reduce the dependence on oil and gas that support authoritarian regimes around the world? This shift away from the middle-east and Russia for energy is now an irreversible trend. Expect a rethink on nuclear energy and acceleration on the adoption of EVs. The other call is who should we back to replace China as the source of cheap goods and services to the west? The low inflation that the west has been used to over the past two decades is in large part on account of China’s integration into global trade. Now China wants to move up the value chain. Worse, it wants to replace the US as the dominant superpower. Continuing to strengthen China economically is no longer an option. China has done its cause no favour by being a bully around its neighbourhood (we know it first hand), being a terrible friend (ask Sri Lanka) and creating an axis with Russia and other authoritarian regimes around the world. There’s no going back to a working relationship with China of the kind that was prevailing before the pandemic. It is unreliable and it won’t turn into an open, democratic society with rising prosperity as was expected. It is difficult to see beyond India in filling that China-shaped void if the west were to search for continued low costs. Vietnam, Bangladesh and others could be alternatives but they lack the scale for the kind of shift that the west wants to make. The inflation pressure means the west doesn’t have time. India has an opportunity here. And I’m more sanguine about this because even if India shoots itself in foot like it is wont to, the way the die is cast it will still get the benefits of this shift. This is a window available for India even if it were to do its best (or worst) in distracting itself with useless, self-defeating issues. Lastly, there are some unintended consequences of a moderately high single-digit inflation for India. This is a government that likes to be fiscally prudent. It didn’t go down the path of ‘printing money’ during the pandemic because it cared about the debt to GDP ratio and the likely censure and downgrades from the global rating agencies. But it is also a government that likes welfarism. Welfarism + Hindutva + Nationalism is the trident it has used to power its electoral fortunes. A rate of inflation that’s higher than government bond yields will pare down the debt to GDP ratio and allow it to fund more welfare schemes. And that’s not a bad idea too considering there’s evidence that things might not be great in the informal economy. That apart, the inflation in food prices because of supply chain disruptions, increase in MSP and the war in Ukraine is good news for the rural economy. After a long time, the WPI food inflation is trending above CPI which means farmers are getting the upside of higher food prices. I guess no one will grudge them this phase however short-lived it might be. Well, I’m not often optimistic on these pages. But the way the stars have aligned themselves, India does have an opportunity to revive its economy in a manner that can sustain itself for long. The question is will it work hard and make the most of it? Or, is it happy being lulled into false glories and imaginary victimhood from the past that its news channels peddle every day?A Framework a Week: Errors of omission and commission — how VLSI relates to subsidiesTools for thinking public policy— Pranay Kotasthane(This article is an updated version of my 2014 essay on nationalinterest.in)The fundamental idea of any testing is to prevent a faulty product from reaching the end consumer. A well-designed test is one that accurately identifies all types of defects in the product. Very often though, this is not possible as tests may not cover the exact range of defects that might actually exist. In that case, the suite of tests leads to errors of commission or omissions. The interesting question, then is — which of the two errors is acceptable?An illustrationThis second problem can be explained using a fairly simple scenario from “Design-for-Testability” theory used in all integrated chip (IC) manufacturing companies. Consider a firm that makes the processor chips going into your laptops. Every single processor chip goes through a set of tests to identify if the chip is good or bad. Four scenarios result from this exercise:The two scenarios marked in green are the best-case scenarios. In the first of these, all the designed tests are unable to find any fault with the chip. At the same time, the chip itself does not show any defects after reaching the end consumers. When such awesomely functional chips reach your laptops, the chip-making companies make profits.In the second “green” scenario, the tests indicate that there is a problem with the chip. Further debugging (which involves greater costs) concludes that this chip is actually manufactured erroneously. It is then the raison d’être of the tests to throw away these chips so that they do not reach the customers.However, when tests are unable to identify any problem with the chip even though it is bad, we end up in the second choice problem 1 scenario or the “error of commission”. This is the scenario you encounter when your laptop crashes within a few days/weeks/years (within the guarantee period) after purchase. Obviously, this makes the consumer lose trust in the product and dents the manufacturing firm’s image.On the other hand, there is the second choice problem 2, where tests are designed so thoroughly that they start eliminating chips which are actually not dysfunctional. This is the Error of Omission. The cost involved with this error is that it leads to a loss of revenue as many good chips are just thrown away based on faulty tests. It also lowers the confidence of the firm.The above illustration shows the two errors that are commonly encountered in the chip manufacturing business. Which of them is tolerable is a function of the company’s image in the market, the end application of the product and the costs involved. For example, if the chip is being manufactured for use in mission-critical automobile systems like auto-braking or fuel injection, the preferable error is the error of omission as there’s a life and personal safety at stake. On the other hand, if the end application is a low-end mobile phone, the company might settle for a higher error of commission and avoid the extra costs of rejecting lots of chips.Application — SubsidiesThe above illustration can directly be applied to a subsidy case to explain the effect of identifying beneficiaries incorrectly. Using the framework above, we can visualise a subsidy program as shown in the figure below:From the framework above, which would be your second choice? The first option would be to start with very few beneficiaries being fully aware that there will be a definite Error of Omission. The next step would be to work on reducing this error rate itself. The problem here will be that there might be some people who, even though needy are not attended to urgently.Another option would be to start with a large number of beneficiaries being aware of the errors of commission. A subsequent step would be to try and reduce this error rate. The costs involved here are that the free-riders might sideline the really needy. Such schemes will also require huge sums of capital as they will start by serving a huge number of people. This is the path that most government subsidies follow in India. A digital identity project like Aadhaar plays a role right here — it can reduce the errors of commission.If you were to design a subsidy scheme, which would be your second choice scenario? Thinking about second choices is generally useful in public policy as the first-choice option is often unavailable. The art of policymaking lies in picking a second-best option that makes most people better off. India Policy Watch #2: Samaaj Ke Dushman Insights on burning policy issues in India- RSJHere is a quote for you to ponder over:All these theoretical difficulties are avoided if one abandons the question “Who should rule?” and replaces it by the new and practical problem: how can we best avoid situations in which a bad ruler causes too much harm? When we say that the best solution known to us is a constitution that allows a majority vote to dismiss the government, then we do not say the majority vote will always be right. We do not even say that it will usually be right. We say only that this very imperfect procedure is the best so far invented. Winston Churchill once said, jokingly, that democracy is the worst form of government—with the exception of all other known forms of government.Sounds relevant to our times?Over the past month, I have been reading Karl Popper’s “Open Society and Its Enemies”. It is a wonderful book written during WW2 when open and democratic societies were facing their most difficult test yet. The key question Popper is interested in is how do we avoid democracies falling into the trap of turning themselves inwards and giving into a majoritarian system of governance. Seems like as relevant a question as it was during the time of his writing. While reading the book, I chanced upon a most amazing essay written by Popper himself about his book in The Economist in 1988. Reading it three decades later, it is remarkable how accurate he is in first framing the core question of a democracy right and then looking for solutions that can be tested with scientific rigour. I have produced excerpts from that essay below:In “The Open Society and its Enemies” I suggested that an entirely new problem should be recognised as the fundamental problem of a rational political theory. The new problem, as distinct from the old “Who should rule?”, can be formulated as follows: how is the state to be constituted so that bad rulers can be got rid of without bloodshed, without violence?This, in contrast to the old question, is a thoroughly practical, almost technical, problem. And the modern so-called democracies are all good examples of practical solutions to this problem, even though they were not consciously designed with this problem in mind. For they all adopt what is the simplest solution to the new problem—that is, the principle that the government can be dismissed by a majority vote…My theory easily avoids the paradoxes and difficulties of the old theory—for instance, such problems as “What has to be done if ever the people vote to establish a dictatorship?” Of course, this is not likely to happen if the vote is free. But it has happened. And what if it does happen? Most constitutions in fact require far more than a majority vote to amend or change constitutional provisions, and thus would demand perhaps a two-thirds or even a three-quarters (“qualified”) majority for a vote against democracy. But this demand shows that they provide for such a change; and at the same time they do not conform to the principle that the (“unqualified”) majority will is the ultimate source of power—that the people, through a majority vote, are entitled to rule.Popper’s answer is the two-party system. The Congress is busy with its chintan shivir as we speak and I read Popper with bemusement when he wrote on the merits of a two-party system.The two-party systemIn order to make a majority government probable, we need something approaching a two-party system, as in Britain and in the United States. Since the existence of the practice of proportional representation makes such a possibility hard to attain, I suggest that, in the interest of parliamentary responsibility, we should resist the perhaps-tempting idea that democracy demands proportional representation. Instead, we should strive for a two-party system, or at least for an approximation to it, for such a system encourages a continual process of self-criticism by the two parties.Such a view will, however, provoke frequently voiced objections to the two-party system that merit examination: “A two-party system represses the formation of other parties.” This is correct. But considerable changes are apparent within the two major parties in Britain as well as in the United States. So the repression need not be a denial of flexibility.The point is that in a two-party system the defeated party is liable to take an electoral defeat seriously. So it may look for an internal reform of its aims, which is an ideological reform. If the party is defeated twice in succession, or even three times, the search for new ideas may become frantic, which obviously is a healthy development. This is likely to happen, even if the loss of votes was not very great.Under a system with many parties, and with coalitions, this is not likely to happen. Especially when the loss of votes is small, both the party bosses and the electorate are inclined to take the change quietly. They regard it as part of the game—since none of the parties had clear responsibilities. A democracy needs parties that are more sensitive than that and, if possible, constantly on the alert. Only in this way can they be induced to be self-critical. As things stand, an inclination to self-criticism after an electoral defeat is far more pronounced in countries with a two-party system than in those where there are several parties. In practice, then, a two-party system is likely to be more flexible than a multi-party system, contrary to first impressions.  PolicyWTF: The Wheat Ban Photo OpThis section looks at egregious public policies. Policies that make you go: WTF, Did that really happen?— Pranay KotasthaneThe Directorate General of Foreign Trade (DGFT) has banned wheat exports from India with immediate effect. For an expert’s view on why this ban is a policyWTF, read Ashok Gulati and Sachit Gupta’s take in the Indian Express. The article lists three less-worse options that the government chose to ignore, and opted for this rather extreme step instead. From a broader public policy perspective, there are three points to learn from this PolicyWTF. One, it reflects the perilously increasing scope of what’s classified as “strategic”. Once an item gets that tag, a fundamental concept behind international trade that “only individuals trade, countries don’t”, gets defenestrated. Here’s why I think this “strategic” line of thinking is the real reason behind this policyWTF. Until 11th May, the message from the government was that it has procured sufficient stocks of wheat and that there is no plan for an outright ban on exports. The PM in his recent visit to Germany even proclaimed that Indian farmers have “stepped forward to feed the world" even as many countries grapple with wheat shortages. There were reports that the government might consider an export tax on wheat; a ban wasn’t on the cards. A May 14 Business Standard report cited an unnamed senior official thus:“We have worked on four-five policy measures to curb this unabated flow of wheat from India. A final decision on this is yet to be taken. We are waiting for approval from the Prime Minister’s Office (PMO).”So it seems that it was the PMO that opted for this extreme step. Why, you ask? The reason perhaps lies in the exceptions to the ban. The government plans to permit wheat exports bilaterally, on the request of specific countries. In one fell swoop, every bag of wheat being exported by an Indian farmer now becomes an economic diplomacy photo-op for the government. While this may seem like a masterstroke for the government, this ‘strategy-fication’ comes at the immense expense of farmers and traders. While they will not be able to cash in on the immediate opportunities, they might also receive smaller if not fewer international orders from international buyers in the future.The second lesson from this PolicyWTF is for the farmers. While this particular ban will undoubtedly hurt the farmers and traders, its origins lie in the now-normalised intervention of governments in all aspects of agriculture. In that sense, Minimum Support Prices (MSP) and the wheat ban are two sides of the same coin. A government that giveth will also taketh at whim. The push for making MSP a law is likely to invite more such export bans from the government, in the name of consumer interest. Observe the ease with which the State can take away economic freedoms in this statement by the Commerce Secretary:"So, what is the purpose of this order. What it is doing is in the name of prohibition - we are directing the wheat trade in a certain direction. We do not want the wheat to go in an irregulated manner to places where it might get just hoarded or where it may not be used to the purpose which we are hoping it would be used for”.The third policy lesson is the need to lift the bans on genetically edited crops. The ostensible reason for this ban was a decrease in production due to the heatwave in large parts of India. Assuming that climate change will lead to many more instances of crop failures, crops engineered to withstand higher temperatures are an important part of the solution. In the wake of the ongoing wheat shortage, there are signs that the regulatory environment is changing in a few countries. Australia and New Zealand approved a drought-tolerant Argentinean wheat variety for human consumption last week. Many countries now classify gene edited crops that do not use DNA from a different organism, as non-GMO. Indian regulators hopefully too will move in the same direction.HomeWorkReading and listening recommendations on public policy matters[Post] The Indian ‘sedition’ law was in the news last week. We had a conceptual take on sedition in edition #115 that puts the current events in context.[Podcast] What’s it like to grow, operate, and sell a manufacturing firm in India? That’s the theme of the latest Puliyabaazi with Hema Hattangady.[Book] Lithium batteries are all the rage. For understanding the politics and the geopolitics of these batteries, read Lukacz Bednarski’s succinct Lithium: The Global Race for Battery Dominance and the New Energy Revolution. For a short introduction to battery failure accidents in India, here’s a nice primer by Saurabh Chandra on Puliyabaazi. This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit publicpolicy.substack.com

In this episode we have the extraordinary theory of Biocentrism to consider: the hypothesis that the space, time and matter arose from life, and not the other way around. This theory obviously flies completely in the face of material science's Darwinian view that life and consciousness evolved slowly out of ever more complex systems of matter. Now we've heard in multiple interviews on the show so far that similar theories like Panpsychism, the hypothesis that consciousness is fundamental to the physical world, are hugely increasing in popularity and not only among philosophers but also among physicists, perhaps because many of the anomalies coming out of quantum experiments can be explained in a panpsychist model. But this is the first time as far as I know that a scientist has argued that life itself is fundamental to the physical world. Perhaps to many scientists it would sound absurd, but as the theory has been popularised by award winning Stem Cell biologist Robert Lanza, it seems important that we give this theory a closer look. Given our physics slant on Chasing Consciousness, we are extremely lucky to be speaking today with Robert Lanza's co-author on the new book about the theory “The Grand Biocentric Design, How life creates reality”, physicist and author Matej Pavšič Matej Pavšič has been a theoretical physicist at the Jožef Stefan Institute in Slovenia for over 40 years, working on Mirror Particles, Brane Spaces, and Clifford algebra and spaces among other areas. He's published more than hundred scientific papers and 3 books including "The Landscape of Theoretical Physics: A Global View" (Kluwer Academic, 2001) and "Stumbling Blocks Against Unification" (World Scientific, 2020). And the Biocentrism book mentioned above. 00:00 Intro 06:00 Niels Bohr - Measurement ‘creates ‘ the world quote 10:00 The wave particle duality - real vs perceived 15:10 The Many Worlds Interpretation of quantum mechanics 18:00 Hugh Everett - The wave function is relative to the observer 20:00 The risk of Woo when talking about Quantum Entanglement 25:30 A universe fine tuned for life - Hierarchical levels of representation and the hard problem 37:00 Mystical experiences may connect to wave function of the universe 38:31 Hawking and Wheeler - The past is not fixed until measurement 39:45 Matej's theory: The Big Bang could have been caused by a vacuum instability in the quantum field 40:30 The book has been criticised by scientists for being over-simplified for the general public 44:30 Testability of Biocentrism via Quantum Mechanics 46:00 Weak Biocentrism paper, accounting for the observer effect while keeping the physical world 49:00 Quantum Suicide and the impossibility of being dead from the first person point of view 53:00 Why is consciousness so controversial in modern physics? 55:12 Difficulty of applying different laws at the classical and quantum level References: Rupert Everett - The Many Worlds from interpretation of quantum mechanics Robert Lanza, Dmitriy Podolskiy and Andrei Barvinsky paper - reduction of quantum gravity in the presence of observers: Intro article and Paper

On today's ID the Future, philosopher of biology Paul Nelson discusses his chapter in a recent Harvest House anthology edited by host Casey Luskin, The Comprehensive Guide to Science and Faith. Nelson says the theory of universal common descent, a key component of modern evolutionary theory, has generated multiple predictions that have failed. The prediction he discusses here is that there would turn out to be a single universal genetic code, since that's what we should expect if all life on earth is descended from the last universal common ancestor (LUCA). Findings over the past three decades have  proven that prediction spectacularly wrong. How does the theory of universal common descent shrug off this contrary empirical finding? The trick for Read More › Source

On today's ID the Future, Casey Luskin further discusses his recent essay, “What Is Intelligent Design and How Should We Defend It,” in the new book The Comprehensive Guide to Science and Faith. In his conversation with host Eric Anderson, Luskin rebuts the claims that intelligent design isn't science (it is), doesn't produce peer-reviewed research (it does), and is just a negative argument against evolution. He also offers advice on handling personal attacks and objections that you've never encountered before. To consider supporting the work of Discovery Institute's Center for Science and Culture and its brave scientists, click here for options. Source

Join Dr Tim Scarfe, Sayak Paul, Yannic Kilcher, and Alex Stenlake have a conversation with Mr. Chai Time Data Science; Sanyam Bhutani! 00:00:00 Introduction 00:03:42 Show kick off 00:06:34 How did Sanyam get started into ML 00:07:46 Being a content creator 00:09:01 Can you be self taught without a formal education in ML? 00:22:54 Kaggle 00:33:41 H20 product / job 00:40:58 Intepretability / bias / engineering skills 00:43:22 Get that first job in DS 00:46:29 AWS ML Ops architecture / ml engineering 01:14:19 Patterns 01:18:09 Testability 01:20:54 Adversarial examples Sanyam's blog -- https://sanyambhutani.com/tag/chaitimedatascience/ Chai Time Data Science -- https://www.youtube.com/c/ChaiTimeDataScience

Felienne interviews Marco Faella about his book ‘Seriously Good Software,’ which aims to teach programmers to use six key qualities to better analyze the quality of their code bases.

Quais são as possíveis formas de injetar dependências no Swift? Nesse episódio, os hosts conversam sobre singletons, initializers e como empresas grandes usam mágicas de runtime para resolver esse assunto. Siga a gente no Twitter: twitter.com/BuildFailedCast Links mencionados no episódio: - RouterService: https://github.com/rockbruno/RouterService - Dependency Injection | Swift 4, Xcode 9: https://www.youtube.com/watch?v=sHLd1BuW0aU - Engineering for Testability: https://developer.apple.com/videos/play/wwdc2017/414/

Dave Nott nearly sells his 16" MacBook Pro and Dave Wood falls down the rabbit hole (again!) of trying to find the perfect architecture for his SwiftUI projects. Dave Wood (https://twitter.com/davidgarywood) Dave Nott (https://twitter.com/_davenott) Waiting For Review (https://twitter.com/wfrpodcast) Music by Broke For Free (http://freemusicarchive.org/music/Broke_For_Free/Something_EP/Broke_For_Free-Something_EP-_05_Something_Elated) License, CC Attribution 3 (http://creativecommons.org/licenses/by/3.0/us/)

This is the second part of my interview with Alan Richardson, better known as "Evil Tester." We discussed many topics related to software testing automation. You can also play the episode and read the full transcript here: https://bit.ly/2YPSr3r In this second half of the interview we covered: - Testability, automatability and observability - How to show ROI of automation, learning about selling - How Alan got started in software testing - The book he recommends for learning how to ask questions Side note, I'm thrilled to announce that Quality Sense was included on feedspot's list of top software testing podcasts! Thanks to all of you out there listening! https://blog.feedspot.com/software_testing_podcasts/

Rocket developers Brandon Aaskov, Dave Oelfke, Simon Ingeson, and Matt Merrill dive into the topic of clean code. When is it worth it? When is it unnecessary? Will it get you in trouble with your teammates? We also share some practical tips for walking the line between "You ain't gonna need it" and when it's worth it to spend that extra 20 minutes cleaning up code.  This podcast was inspired by the article "Goodbye Clean Code" by Dan Abramov which ignited a lot of talk in the Rocket Insights engineering slack channels! Detailed Notes: 00:00 - Intros 03:20 - Human readability is the most important thing. Are there any hard and fast rules? Cyclomatic complexity is a fancy word that's discussed 06:00 - It's hard to break out of a bad abstraction. It's hard to predict the future 11:00 - There's nothing more permanent than temporary 12:15 - Spreading out your code over lots of folders is probably not a great idea 14:30 - Flexing your muscles... Unnecessarily? 15:26 - A word from our sponsor 16:30 - Wait for the pain 19:30 - Give yourself flexibility for the future, but don't implement it right away 20:40 - How did we get to this point? A little history. Memory management wasn't always done for us 27:00 - There are no hard and fast rules. Be an adult 29:45 - The golden hour rule. Readme's are important 37:45 - Back to what makes code readable 41:00 - Testability. Using tests to learn about existing codebases 45:00 - File driven development 46:30 - Why refactor? 51:15 - The good samaritan rule 51:50 - Picks: Matt - HBO Silicon Valley Season Six Simon - 1917 (the movie)  Dave - Nest.js Brandon - Master Class 

Nesse episódio, os hosts Bruno Rocha, Bruno Ramos e Fabricio Serralvo recebem Henrique Morbin como convidado para falarem sobre testes automatizados, boas práticas e o que é esperado do assunto em 2020. Siga a gente no Twitter: twitter.com/BuildFailedCast Links mencionados no episódio: - Engineering for Testability: https://developer.apple.com/videos/play/wwdc2017/414/ - Testing Tips & Tricks: https://developer.apple.com/videos/play/wwdc2018/417 - Keeping Software Soft - Gerard Meszaros: https://www.youtube.com/watch?v=JwE2DkSGxro - iOS Unit Testing by Example: https://pragprog.com/book/jrlegios/ios-unit-testing-by-example - Practical Protocol-Oriented-Programming: https://academy.realm.io/posts/appbuilders-natasha-muraschev-practical-protocol-oriented-programming/

LDS Mormon Missionaries bring an atheist lunch before exploring how they determined that the Book of Mormon of truth. Watch video of talk here: https://youtu.be/Alm4bD5xnCg Location: San Antonio, Texas Recorded: 4 December 2019 Released: 27 December 2019 Twitter: https://twitter.com/magnabosco (follow me) YouTube: https://youtube.com/magnabosco210 (tons of videos) Facebook: https://facebook.com/magnabosco210 (like my page) Website: https://anthonymagnabosco.com (contact me, appearances) SE Resources: https://tinyurl.com/abm-se-resources SE Community: https://tinyurl.com/abm-se-community SE Discord Server: https://discord.gg/sKap3zM Skip ahead to a desired point in the talk: -- Start: 12:08 (great if pressed for time) Explaining: 12:08, 15:29 Skate or Die: 07:33, 13:15, 34:48, 57:24, 58:09 Rapport-Building: 12:43 Goal-Checking: 16:32 Morality: 21:45 Recapping: 15:47 Reassurance: 33:37 Testing: 23:38, 24:09 Clarifying: 53:11, 53:51 Interrupting: 36:32, 47:16, 49:05, 52:37, 54:41 Justification (Why): 18:16 Repeating: 19:17, 23:46, 24:51, 25:00, 26:05, 27:02, 29:25, 53:56 Challenging: 19:43, 21:46, 40:20, 41:14, 41:37 Pushback: 47:53 Resetting: 29:59, 38:20 Closing: 56:37 Outro: 58:56 -- Note: Add 35 seconds to these timestamps if listening to the podcast version of this talk. Audio correction provided by Philipp Grzemba. Waiting music is 'Trip' by KV, provided courtesy YouTube. Music provided by Jim Rhodes, with Dan Harris on lap steel. ** Add foreign language captions w/YouTube's community contributions tools ** Mistakes: Please let me know if you spot any. Recorded w/Go-Pro. Edited w/PowerDirector. The views addressed here are mine and mine alone, and are not necessarily shared by members of my family and friends.

SPaMCAST 572 features our interview with Michael Larsen.  Mr. Larsen and I battled fires, Santa Ana winds, and power cuts to have a great conversation on testability.  Anyone that has participated in delivering software EVER has wrestled with a discussion of whether a story or requirement can be proved.  Michael brings fresh and actionable insights into how to assure testability.   Michael’s bio Michael Larsen is a Senior Quality Assurance Engineer with Socialtext/PeopleFluent. Over the past two decades, he has been involved in software testing for a range of products and industries, including network routers & switches, virtual machines, capacitance touch devices, video games, and client/server, distributed database & web applications. Michael is a Black Belt in the Miagi-Do School of Software Testing, helped start and facilitate the Americas chapter of Weekend Testing, is a former Chair of the Education Special Interest Group with the Association for Software Testing (AST), a lead instructor of the Black Box Software Testing courses through AST, and former Board Member and President of AST. Michael writes the TESTHEAD blog and can be found on Twitter at @mkltesthead. A list of books, articles, papers, and presentations can be seen at http://www.linkedin.com/in/mkltesthead.  Re-Read Saturday News In this week’s installment of our re-read of Thinking, Fast and Slow Kahneman, formally introduces the Prospect Theory and talks about the difference between it and the Expected Utility Theory. When doing a little background research, Prospect Theory (part of his research on decision making under uncertainty)contributed to his winning the Nobel prize in economics.  Remember, if you do not have a favorite, dog-eared copy of Thinking, Fast and Slow, please buy a copy.  Using the links in this blog entry helps support the blog and its alter-ego, The Software Process and Measurement Cast. Buy a copy on Amazon,  It’s time to get reading! The current installment of Re-read Saturday  Chapter 26 - Prospect Theory -http://bit.ly/2Nx3tWI   Next SPaMCAST SPaMCAST 573 will feature our essay on a workflow to prioritize a backlog.  Items on any backlog proliferate. Product backlogs used in agile and lean development approaches are no different.  Many outsiders have the mistaken notion that once on the list that that is the end of the story - this is far from the truth! We will also have the return of Gen Hughson with an entry in his column, Form Follows Function.

In this rant I go off about the importance of critical thinking, and include examples from the martial arts, business and life.  Somehow I try to wrap things up by bringing the Heaven's Gate cult and the biggest mass suicide on US soil into the discussion.  Let me know if this podcast worked on you on Twitter (where I'm @stephankesting), OK?

Kenneth, Kevin and Len are joined by Rebecca Franks to discuss the world of mobile development for Android, Google's developer platform and her recent Google Developer Expert accolade. We take a dive into all things Android, starting with the Play Store and the impact that's made on the app ecosystem before going into the more technical details of building and testing Android apps and the tooling behind it. We speak through some of the nuances of building against Android's APIs and look at alternatives to Java and the ability to interop with native code through Android's NDK. Follow Rebecca online: Twitter: https://twitter.com/riggaroo Blog: http://riggaroo.co.za/ Android Studio - http://developer.android.com/sdk/index.html Google Play Store - https://play.google.com/store Apple App Store - https://itunes.apple.com/za/genre/ios/id36 A/B testing in the Google Play Store - http://bit.ly/1MYZJJx Bookdash - Rebecca's App - https://play.google.com/store/apps/details?id=org.bookdash.android Android API levels - http://developer.android.com/guide/topics/manifest/uses-sdk-element.html Android Support Repository - http://developer.android.com/tools/support-library/setup.html Browserstack - https://www.browserstack.com Genymotion - https://www.genymotion.com/ Google test lab - https://developers.google.com/cloud-test-lab/ Espresso - https://google.github.io/android-testing-support-library/docs/espresso/ Mockito - http://mockito.org/ Android Marshmallow permissions - http://developer.android.com/training/permissions/requesting.html Understanding Battery Usage in your Android App - http://riggaroo.co.za/understanding-battery-usage-android-app/ IntelliJ - https://www.jetbrains.com/idea/ Dalvik - https://en.wikipedia.org/wiki/Dalvik_(software) Kotlin - https://kotlinlang.org/ Gradle - http://gradle.org/ Xtend - http://www.eclipse.org/xtend/ Xtendroid - https://github.com/tobykurien/Xtendroid Cordova - https://cordova.apache.org/ React Native - https://facebook.github.io/react-native/ Android NDK - http://developer.android.com/tools/sdk/ndk Google Developer Expert - https://developers.google.com/experts/ Local Android developer spots: GDG Cape Town - http://www.meetup.com/Google-Developer-Group-Cape-Town-Meetup/ GDG Pretoria - https://developers.google.com/groups/chapter/117599647232533838312/ GDG Johannesburg - https://developers.google.com/groups/chapter/102185667048205980695/ Johannesburg Android Usergroup - http://www.meetup.com/androidug-joburg/ Picks Kenneth: AfrikaBurn - http://www.afrikaburn.com Len: Durable Queue - https://github.com/Factual/durable-queue Rebecca: Android Weekly - http://androidweekly.net/ Riggaroo blog - http://riggaroo.co.za/ Kevin: Evening of Mastery - http://stream.drivenalliance.com/events/AnEveningOfMastery/ Clean Code - http://www.amazon.com/Clean-Code-Handbook-Software-Craftsmanship/dp/0132350882 The Clean Coder - http://www.amazon.com/Clean-Coder-Conduct-Professional-Programmers/dp/0137081073 Working Effectively with Legacy Code - http://www.amazon.com/Working-Effectively-Legacy-Michael-Feathers/dp/0131177052 Refactoring - http://www.amazon.com/Refactoring-Improving-Design-Existing-Code/dp/0201485672 The Deep Synergy between Testability and Good Design - https://www.youtube.com/watch?v=4cVZvoFGJTU Thanks for listening! Stay in touch: * Socialize - https://twitter.com/zadevchat & http://facebook.com/ZADevChat/ * Suggestions and feedback - https://github.com/zadevchat/ping * Subscribe and rate in iTunes - http://bit.ly/zadevchat-itunes

In the third part of their discussion, Mario Livio and Joe Silk ask: could our theories exceed our ability to test them? Have they already? This discussion was conducted at Trinity College, Oxford, on February 12, 2016.

Yes we can! (Maybe?) Want to come work with me? We're hiring a junior tester! Leading on from the Science! bit, I want to talk about testability. So testability is how testable a product or system is by a given person, in a given context. Having software that’s testable makes testing quicker, because not only can we test quicker, we can also be confident that our testing has been effective. Testability requires certain things: We need to have a definition of right or correct behaviour, so we can form a test plan or strategy. If we don’t know how the system is meant to work, we can’t ensure it’s working as expected. We need to put some work into defining features separately, so each can be discussed in isolation (or as much as is possible). This iterative process means testing can happen as early as possible, otherwise we’re in a position when all we can test is all of it in one go, which makes it harder to test. There are some things that are only really testable in certain circumstances - whether that be a quirk of the system that means we can only monitor the results when live, or features that have an effect over a long period of time. I recently had a feature that tracked results over 7 days, and it wouldn’t be feasible for us to leave off deploying to the test environment for 7 days to see if that works, so there was some hackery involved so I can ensure that it removed data from older than 7 days as expected, things like that. It wasn’t ideal, but it was good enough. And this is an issue that I run into occasionally. Where possible we try to figure out a way to test it as close to reality as possible, and put those frameworks or systems in place. Linked to this is being taught how a feature works. Sometimes devs will put notes on a ticket to point me in the right direction, and then will provide release notes for the client. One lead dev recently asked whether we would be worth putting the notes they’d pass onto the client on the ticket when passing the story for testing, so I can both test the feature and the release notes. Now, this is an idea I want to implement, because again, the devs know how to use the feature, so the instructions may be either too broad, or use terminology that’s not well known to the client (referencing entities, MIME types, etc). I prefer just having an idea of what the feature should do or should allow me to do, so I can see how intuitive the feature is, and make sure I’m not following the smooth path and looking for edge cases. If it’s a complex piece of back end functionality that we would provide instructions for, then I’ll use those to see if they work as expected. This way, I’m testing both the instructions and the feature at the same time. There’s more to testability than usability though. The definition is testing by a given person in a given context. Everyone tests differently, and everyone uses different tools to do so. Testability in this sense can be raised by someone helping out with testing, or by a test strategy, product, system, or domain knowledge; anything that means the tester can test more, or feel more comfortable and confident testing increases testability. And gaining knowledge of the product and the client will give greater understanding of risk, both to the specific product and to the system you use more broadly. For example, I generally speaking, test Drupal sites. Drupal does categorisation in the form of taxonomies and vocabularies out of the box. Specific categories have to be set up, but the framework is there. That takes roughly two minutes for me to look over while I’m testing something else because I know that it doesn’t need testing, really. I feel comfortable taking that risk. And managing risk, and reducing the distance between what we currently know and what we need to know is really the cornerstone of testing. Footnotes http://www.infoq.com/news/2016/02/testability-teams-faster https://www.testingcircus.com/lessons-usability/ http://www.satisfice.com/tools/testable.pdf

In this episode, Adam talks to J.B. Rainsberger about how to keep your adapter layer thin, designing unit testable code, and the importance of paying attention to how your code is changing vs. how your code looks today. This episode is brought to you by Laracasts. Links: J.B.'s Blog Integrated Tests are a Scam Mock Roles, not Objects The Four Elements of Simple Design Ask J.B. a question J.B.'s Intro to TDD Course Sponsored by Laracasts

Check out JS Remote Conf and All Remote Confs!   02:32 - Brad Urani Introduction Twitter GitHub Blog Procore 04:01 - Immutable/Persistent Data Structures; Advantages Changing the Unchangeable: The Hows and Whys of Immutable Data Structures @ RubyConf 2015 hamster 07:30 - Tools for Debugging 08:23 - Why do Rubyists care about things like Elm? 09:39 - Persistent Data Structure Use Cases; Functional Programming 12:07 - Testability 13:51 - Where does “functional play a role in a typical CRUD app? Active Record, The Single Responsibility Principle (SRP) Callbacks Object-oriented Programming (OOP) “Nouns are objects; verbs are methods” - Corey Haines 22:49 - Coworker Receptiveness of Ruby + JavaScript Style of Programming Codebase Inconsistency? “Merit” 26:41 - Service-oriented Architecture (SOA) vs Monolithic Applications Remote Procedure Calls (RPC) Representational State Transfer (REST) 30:21 - Monoliths as a Necessary Stage in the Development of a Mature Application Elixir The Phoenix Framework ecto 33:23 - The Repository Pattern; Terminology & Naming Patterns of Enterprise Application Architecture by Martin Fowler 37:40 - Structured Query Language (SQL) Avdi Grimm: The Soul of Software @ RubyConf Portugal '15 The Sapir Whorf Hypothesis' Picks Dan Carlin's Hardcore History (Coraline) Stuff You Missed in History Class (Coraline) Buffer (Avdi) New Belgium Brewing Accumulation White IPA (Avdi) Saramonic SmartMixer Professional Recording Stereo Microphone Rig (Chuck) LaunchCode (Brad) Turing's Cathedral: The Origins of the Digital Universe by George Dyson (Coraline) VAT19 (Brad)

Check out JS Remote Conf and All Remote Confs!   02:32 - Brad Urani Introduction Twitter GitHub Blog Procore 04:01 - Immutable/Persistent Data Structures; Advantages Changing the Unchangeable: The Hows and Whys of Immutable Data Structures @ RubyConf 2015 hamster 07:30 - Tools for Debugging 08:23 - Why do Rubyists care about things like Elm? 09:39 - Persistent Data Structure Use Cases; Functional Programming 12:07 - Testability 13:51 - Where does “functional play a role in a typical CRUD app? Active Record, The Single Responsibility Principle (SRP) Callbacks Object-oriented Programming (OOP) “Nouns are objects; verbs are methods” - Corey Haines 22:49 - Coworker Receptiveness of Ruby + JavaScript Style of Programming Codebase Inconsistency? “Merit” 26:41 - Service-oriented Architecture (SOA) vs Monolithic Applications Remote Procedure Calls (RPC) Representational State Transfer (REST) 30:21 - Monoliths as a Necessary Stage in the Development of a Mature Application Elixir The Phoenix Framework ecto 33:23 - The Repository Pattern; Terminology & Naming Patterns of Enterprise Application Architecture by Martin Fowler 37:40 - Structured Query Language (SQL) Avdi Grimm: The Soul of Software @ RubyConf Portugal '15 The Sapir Whorf Hypothesis' Picks Dan Carlin's Hardcore History (Coraline) Stuff You Missed in History Class (Coraline) Buffer (Avdi) New Belgium Brewing Accumulation White IPA (Avdi) Saramonic SmartMixer Professional Recording Stereo Microphone Rig (Chuck) LaunchCode (Brad) Turing's Cathedral: The Origins of the Digital Universe by George Dyson (Coraline) VAT19 (Brad)

Check out JS Remote Conf and All Remote Confs!   02:32 - Brad Urani Introduction Twitter GitHub Blog Procore 04:01 - Immutable/Persistent Data Structures; Advantages Changing the Unchangeable: The Hows and Whys of Immutable Data Structures @ RubyConf 2015 hamster 07:30 - Tools for Debugging 08:23 - Why do Rubyists care about things like Elm? 09:39 - Persistent Data Structure Use Cases; Functional Programming 12:07 - Testability 13:51 - Where does “functional play a role in a typical CRUD app? Active Record, The Single Responsibility Principle (SRP) Callbacks Object-oriented Programming (OOP) “Nouns are objects; verbs are methods” - Corey Haines 22:49 - Coworker Receptiveness of Ruby + JavaScript Style of Programming Codebase Inconsistency? “Merit” 26:41 - Service-oriented Architecture (SOA) vs Monolithic Applications Remote Procedure Calls (RPC) Representational State Transfer (REST) 30:21 - Monoliths as a Necessary Stage in the Development of a Mature Application Elixir The Phoenix Framework ecto 33:23 - The Repository Pattern; Terminology & Naming Patterns of Enterprise Application Architecture by Martin Fowler 37:40 - Structured Query Language (SQL) Avdi Grimm: The Soul of Software @ RubyConf Portugal '15 The Sapir Whorf Hypothesis' Picks Dan Carlin's Hardcore History (Coraline) Stuff You Missed in History Class (Coraline) Buffer (Avdi) New Belgium Brewing Accumulation White IPA (Avdi) Saramonic SmartMixer Professional Recording Stereo Microphone Rig (Chuck) LaunchCode (Brad) Turing's Cathedral: The Origins of the Digital Universe by George Dyson (Coraline) VAT19 (Brad)

02:25 - Neal Ford Introduction Twitter GitHub Blog ThoughtWorks iPhreaks Show Episode #084: Building Your Technology Radar with Neal Ford Freelancers' Show Episode 145: Life as a Traveling Consultant with Neal Ford RailsConf 2010: Neal Ford "Creativity & Constraint"    02:20 - The Thoughtworks Technology Radar Rebecca Parsons 06:28 - Quadrants Techniques Tools Languages & Frameworks Platforms 07:01 - Categories (Rings) Hold Assess Trial Adopt 09:23 - Adopting New Technologies William Gibson: “The future is already here, it’s just not evenly distributed.” Cycle Time Neal Ford: Build Your Own Technology Radar [YouTube] Neal Ford: Build Your Own Technology Radar 14:42 - Providing Familiarity Resources 15:24 - Radars as Resources and Lifecycle Assessment Tools Intentional Software Radar A-Z 18:36 - Themes 22:17 - Making Decisions Diversify Testability 27:40 - Jamming Radars 31:53 - Hireability? Paying Developers to Learn 36:54 - Financial Portfolios and Planning Your Career Specialization vs Generalization 42:03 - Software Architecture & Engineering Practices Microservices 43:57 - Functional Programming Functional Thinking: Paradigm Over Syntax by Neal Ford Clojure 44:16 - Estimation 46:03 - Creating Your Own Radar Brett Dargan: bdargan/techradar Blip Placement Neal Ford: Build Your Own Technology Radar Picks All Watched Over by Machines of Loving Grace (Avdi) The Project Euler Sprint (Coraline) Gloom (Coraline) The Bad Plus: Inevitable Western (Jessica) tmate (Jessica) Screenhero (Chuck) Slack (Chuck) DevOps Bookmarks (Neal) Elvis has left the ivory tower by Neal Ford (Neal) Culture Series (Neal)

02:25 - Neal Ford Introduction Twitter GitHub Blog ThoughtWorks iPhreaks Show Episode #084: Building Your Technology Radar with Neal Ford Freelancers' Show Episode 145: Life as a Traveling Consultant with Neal Ford RailsConf 2010: Neal Ford "Creativity & Constraint"    02:20 - The Thoughtworks Technology Radar Rebecca Parsons 06:28 - Quadrants Techniques Tools Languages & Frameworks Platforms 07:01 - Categories (Rings) Hold Assess Trial Adopt 09:23 - Adopting New Technologies William Gibson: “The future is already here, it’s just not evenly distributed.” Cycle Time Neal Ford: Build Your Own Technology Radar [YouTube] Neal Ford: Build Your Own Technology Radar 14:42 - Providing Familiarity Resources 15:24 - Radars as Resources and Lifecycle Assessment Tools Intentional Software Radar A-Z 18:36 - Themes 22:17 - Making Decisions Diversify Testability 27:40 - Jamming Radars 31:53 - Hireability? Paying Developers to Learn 36:54 - Financial Portfolios and Planning Your Career Specialization vs Generalization 42:03 - Software Architecture & Engineering Practices Microservices 43:57 - Functional Programming Functional Thinking: Paradigm Over Syntax by Neal Ford Clojure 44:16 - Estimation 46:03 - Creating Your Own Radar Brett Dargan: bdargan/techradar Blip Placement Neal Ford: Build Your Own Technology Radar Picks All Watched Over by Machines of Loving Grace (Avdi) The Project Euler Sprint (Coraline) Gloom (Coraline) The Bad Plus: Inevitable Western (Jessica) tmate (Jessica) Screenhero (Chuck) Slack (Chuck) DevOps Bookmarks (Neal) Elvis has left the ivory tower by Neal Ford (Neal) Culture Series (Neal)

02:25 - Neal Ford Introduction Twitter GitHub Blog ThoughtWorks iPhreaks Show Episode #084: Building Your Technology Radar with Neal Ford Freelancers' Show Episode 145: Life as a Traveling Consultant with Neal Ford RailsConf 2010: Neal Ford "Creativity & Constraint"    02:20 - The Thoughtworks Technology Radar Rebecca Parsons 06:28 - Quadrants Techniques Tools Languages & Frameworks Platforms 07:01 - Categories (Rings) Hold Assess Trial Adopt 09:23 - Adopting New Technologies William Gibson: “The future is already here, it’s just not evenly distributed.” Cycle Time Neal Ford: Build Your Own Technology Radar [YouTube] Neal Ford: Build Your Own Technology Radar 14:42 - Providing Familiarity Resources 15:24 - Radars as Resources and Lifecycle Assessment Tools Intentional Software Radar A-Z 18:36 - Themes 22:17 - Making Decisions Diversify Testability 27:40 - Jamming Radars 31:53 - Hireability? Paying Developers to Learn 36:54 - Financial Portfolios and Planning Your Career Specialization vs Generalization 42:03 - Software Architecture & Engineering Practices Microservices 43:57 - Functional Programming Functional Thinking: Paradigm Over Syntax by Neal Ford Clojure 44:16 - Estimation 46:03 - Creating Your Own Radar Brett Dargan: bdargan/techradar Blip Placement Neal Ford: Build Your Own Technology Radar Picks All Watched Over by Machines of Loving Grace (Avdi) The Project Euler Sprint (Coraline) Gloom (Coraline) The Bad Plus: Inevitable Western (Jessica) tmate (Jessica) Screenhero (Chuck) Slack (Chuck) DevOps Bookmarks (Neal) Elvis has left the ivory tower by Neal Ford (Neal) Culture Series (Neal)

A hypothesis should be testable, including "God exists." How honestly do Christians follow the evidence? And have they made their hypothesis unfalsifiable? (For the podcast transcript, search for the title at www.Patheos.com/Blogs/CrossExamined)

Panel Misko Hevery (twitter github blog) Igor Minar (twitter github blog) Jamison Dance (twitter github blog) Joe Eames (twitter github blog) Tim Caswell (twitter github howtonode.org) AJ O’Neal (twitter github blog) Discussion 01:33 - Angular.js (twitter github blog) 02:33 - Angular.js compared to other frameworks 04:03 - How does it work? 05:22 - Cost 06:06 - HTML Compiler 07:02 - Directives 10:31 - Working with browsers in the future 12:07 - Dependency injection 16:50 - Main method 18:48 - Using require.js 20:53 - How would you build a TreeView widget in Angular? 24:07 - Where data is stored 24:42 - Scope 29:47 - Syncing to servers RESTClient 31:34 - Testability & Services in Angular 39:04 - Benefits of Angular Dependency injection Directives Picks The Arrow (Joe) Font Awesome (Tim) Testacular (Igor) Plunker (Igor) The Better Angels of our Nature: Steven Pinker (Misko) XCOM (Jamison) The Foundation Series: Isaac Asimov (Jamison) Influencer: The Power to Change Anything (AJ) Transcript [This episode is sponsored by ComponentOne, makers of Wijmo. If you need stunning UI elements or awesome graphs and charts, then go to wijmo.com and check them out.] [Hosting and bandwidth provided by the Blue Box Group. Check them out at bluebox.net] JAMISON: Hi everybody and welcome to episode 32 of the JavaScript Jabber podcast. I'm not your host Charles Max Wood, I'm Jamison Dance. Chuck is at a conference this week. So, he is not here. We have with us Joe Eames. JOE: Hey everybody! JAMISON: Tim Caswell. TIM: Hello. JAMISON: And we have two special guests. I'm going to mangle your names, so I'm sorry. It’s Misko Hevery. MISKO: Misko Hevery. Yeah, thank you. JAMISON: Misko Hevery and Igor Minar? IGOR: Minar. Yeah. JAMISON: Great. You guys wanna introduce yourself really quick? MISKO: Sure. So, this is Misko Hevery, original creator of Angular.js. IGOR: Hi everybody! I'm Igor. I joined Misko about 2 years ago on this venture of creating better browser and better environment for creating client-side applications. JAMISON: And if you can’t tell, we are going to talk about Angular.js this week. So, I know it is kind of a Google project now. Did it start out that way? MISKO: It started out with something I was working on and eventually I've open sourced it at a product with Google internal application and just gotten such a rave reviews and new features that people actually says, “Hey why don’t you work on this full time and turn in on to a real product?” So, that's how it’s started. JAMISON: Oh, wow. So, there’s actually a team in Google who are working on Angular as their job? MISKO: Yeah. IGOR: Yes. JAMISON: That's awesome. IGOR: It’s just two of us here now, but we have a bunch of other people working full time on Angular.js and also main contributors-- JAMISON: Oh, go ahead sorry. IGOR: There is a team behind Angular.js. JAMISON: Do you think you can give an overview and kind of a comparison to contrast Angular to some of the other MVC frameworks that people like before you? I mean, Backbone I guess is what most people know.  So, what makes Angular different from Backbone? How does it work? MISKO: So, I have never used Backbone besides it’s framework. But, my understanding is that Backbone is basically you have declare model and then launch on changes on its mode. And the way it does so is that there is a model class object. And whenever you modify the models that use special getters and setters methods, the Backbone know about the changes. So, this is pretty different from Angular because we don’t require you to inherit from anything. We have special getters and setters. Basically, any JavaScript object can be a model. So, that’s one big difference. JAMISON: But you can still observe the changes on objects like that? MISKO: Right.

Panel Misko Hevery (twitter github blog) Igor Minar (twitter github blog) Jamison Dance (twitter github blog) Joe Eames (twitter github blog) Tim Caswell (twitter github howtonode.org) AJ O’Neal (twitter github blog) Discussion 01:33 - Angular.js (twitter github blog) 02:33 - Angular.js compared to other frameworks 04:03 - How does it work? 05:22 - Cost 06:06 - HTML Compiler 07:02 - Directives 10:31 - Working with browsers in the future 12:07 - Dependency injection 16:50 - Main method 18:48 - Using require.js 20:53 - How would you build a TreeView widget in Angular? 24:07 - Where data is stored 24:42 - Scope 29:47 - Syncing to servers RESTClient 31:34 - Testability & Services in Angular 39:04 - Benefits of Angular Dependency injection Directives Picks The Arrow (Joe) Font Awesome (Tim) Testacular (Igor) Plunker (Igor) The Better Angels of our Nature: Steven Pinker (Misko) XCOM (Jamison) The Foundation Series: Isaac Asimov (Jamison) Influencer: The Power to Change Anything (AJ) Transcript [This episode is sponsored by ComponentOne, makers of Wijmo. If you need stunning UI elements or awesome graphs and charts, then go to wijmo.com and check them out.] [Hosting and bandwidth provided by the Blue Box Group. Check them out at bluebox.net] JAMISON: Hi everybody and welcome to episode 32 of the JavaScript Jabber podcast. I'm not your host Charles Max Wood, I'm Jamison Dance. Chuck is at a conference this week. So, he is not here. We have with us Joe Eames. JOE: Hey everybody! JAMISON: Tim Caswell. TIM: Hello. JAMISON: And we have two special guests. I'm going to mangle your names, so I'm sorry. It’s Misko Hevery. MISKO: Misko Hevery. Yeah, thank you. JAMISON: Misko Hevery and Igor Minar? IGOR: Minar. Yeah. JAMISON: Great. You guys wanna introduce yourself really quick? MISKO: Sure. So, this is Misko Hevery, original creator of Angular.js. IGOR: Hi everybody! I'm Igor. I joined Misko about 2 years ago on this venture of creating better browser and better environment for creating client-side applications. JAMISON: And if you can’t tell, we are going to talk about Angular.js this week. So, I know it is kind of a Google project now. Did it start out that way? MISKO: It started out with something I was working on and eventually I've open sourced it at a product with Google internal application and just gotten such a rave reviews and new features that people actually says, “Hey why don’t you work on this full time and turn in on to a real product?” So, that's how it’s started. JAMISON: Oh, wow. So, there’s actually a team in Google who are working on Angular as their job? MISKO: Yeah. IGOR: Yes. JAMISON: That's awesome. IGOR: It’s just two of us here now, but we have a bunch of other people working full time on Angular.js and also main contributors-- JAMISON: Oh, go ahead sorry. IGOR: There is a team behind Angular.js. JAMISON: Do you think you can give an overview and kind of a comparison to contrast Angular to some of the other MVC frameworks that people like before you? I mean, Backbone I guess is what most people know.  So, what makes Angular different from Backbone? How does it work? MISKO: So, I have never used Backbone besides it’s framework. But, my understanding is that Backbone is basically you have declare model and then launch on changes on its mode. And the way it does so is that there is a model class object. And whenever you modify the models that use special getters and setters methods, the Backbone know about the changes. So, this is pretty different from Angular because we don’t require you to inherit from anything. We have special getters and setters. Basically, any JavaScript object can be a model. So, that’s one big difference. JAMISON: But you can still observe the changes on objects like that? MISKO: Right.

Panel Misko Hevery (twitter github blog) Igor Minar (twitter github blog) Jamison Dance (twitter github blog) Joe Eames (twitter github blog) Tim Caswell (twitter github howtonode.org) AJ O’Neal (twitter github blog) Discussion 01:33 - Angular.js (twitter github blog) 02:33 - Angular.js compared to other frameworks 04:03 - How does it work? 05:22 - Cost 06:06 - HTML Compiler 07:02 - Directives 10:31 - Working with browsers in the future 12:07 - Dependency injection 16:50 - Main method 18:48 - Using require.js 20:53 - How would you build a TreeView widget in Angular? 24:07 - Where data is stored 24:42 - Scope 29:47 - Syncing to servers RESTClient 31:34 - Testability & Services in Angular 39:04 - Benefits of Angular Dependency injection Directives Picks The Arrow (Joe) Font Awesome (Tim) Testacular (Igor) Plunker (Igor) The Better Angels of our Nature: Steven Pinker (Misko) XCOM (Jamison) The Foundation Series: Isaac Asimov (Jamison) Influencer: The Power to Change Anything (AJ) Transcript [This episode is sponsored by ComponentOne, makers of Wijmo. If you need stunning UI elements or awesome graphs and charts, then go to wijmo.com and check them out.] [Hosting and bandwidth provided by the Blue Box Group. Check them out at bluebox.net] JAMISON: Hi everybody and welcome to episode 32 of the JavaScript Jabber podcast. I'm not your host Charles Max Wood, I'm Jamison Dance. Chuck is at a conference this week. So, he is not here. We have with us Joe Eames. JOE: Hey everybody! JAMISON: Tim Caswell. TIM: Hello. JAMISON: And we have two special guests. I'm going to mangle your names, so I'm sorry. It’s Misko Hevery. MISKO: Misko Hevery. Yeah, thank you. JAMISON: Misko Hevery and Igor Minar? IGOR: Minar. Yeah. JAMISON: Great. You guys wanna introduce yourself really quick? MISKO: Sure. So, this is Misko Hevery, original creator of Angular.js. IGOR: Hi everybody! I'm Igor. I joined Misko about 2 years ago on this venture of creating better browser and better environment for creating client-side applications. JAMISON: And if you can’t tell, we are going to talk about Angular.js this week. So, I know it is kind of a Google project now. Did it start out that way? MISKO: It started out with something I was working on and eventually I've open sourced it at a product with Google internal application and just gotten such a rave reviews and new features that people actually says, “Hey why don’t you work on this full time and turn in on to a real product?” So, that's how it’s started. JAMISON: Oh, wow. So, there’s actually a team in Google who are working on Angular as their job? MISKO: Yeah. IGOR: Yes. JAMISON: That's awesome. IGOR: It’s just two of us here now, but we have a bunch of other people working full time on Angular.js and also main contributors-- JAMISON: Oh, go ahead sorry. IGOR: There is a team behind Angular.js. JAMISON: Do you think you can give an overview and kind of a comparison to contrast Angular to some of the other MVC frameworks that people like before you? I mean, Backbone I guess is what most people know.  So, what makes Angular different from Backbone? How does it work? MISKO: So, I have never used Backbone besides it’s framework. But, my understanding is that Backbone is basically you have declare model and then launch on changes on its mode. And the way it does so is that there is a model class object. And whenever you modify the models that use special getters and setters methods, the Backbone know about the changes. So, this is pretty different from Angular because we don’t require you to inherit from anything. We have special getters and setters. Basically, any JavaScript object can be a model. So, that’s one big difference. JAMISON: But you can still observe the changes on objects like that? MISKO: Right.

Writing Code is the Easy Part is the new slogan for the website. It basically boils down to the fact that putting up syntacticly correct code is the simplest part of coding. More difficult is solving problems and all of the other things that come with having a job or working for clients. Here are some of the things that I listed as the harder parts of coding: Legacy Code Readability Testability Best Practices Writing Tests Team Dynamics Customer Communication Translating Behavior into Code Data Integrity Security Maintainability Systems Integration Server Technologies Databases Finding a Job Hiring and Firing Working on Boring stuff Job Fulfillment Here are affiliate links to some of the books that I mentioned: Refactoring: Improving the Design of Existing Code Design Patterns: Elements of Reusable Object-Oriented Software Code Complete: A Practical Handbook of Software Construction The Pragmatic Programmer: From Journeyman to Master The Passionate Programmer: Creating a Remarkable Career in Software Development (Pragmatic Life) Here are the links to the podcast episodes by: Chad Fowler (Part 1, Part 2) Dave Thomas (Part 1, Part 2) Finally, I would really appreciate a $5 donation to help me get to RubyConf. Download this Episode

Thu, 1 Jan 1987 12:00:00 +0100 http://epub.ub.uni-muenchen.de/5037/ http://epub.ub.uni-muenchen.de/5037/1/5037.pdf Gabriel, Wilfried Möller, Dietmar P. F. (Hrsg.) (1987): The use of computer simulation to evaluate the testability of a new fitness concept. 2. Erwin-Riesch-Arbeitstagung , Februar 1986, Münster-Ebernburg.