If contractors in colder climates focus on educating their customers on what new higher-efficiency furnaces bring to the table, often times the furnaces will sell themselves.

Posted by CISA on Mar 21

Posted by CISA on Mar 23

Posted by Jason Ross via Dailydave on Jul 25

Posted by David Manouchehri via Dailydave on Jul 28

Posted by Dave Aitel via Dailydave on Sep 11

Posted by Isaac Dawson via Dailydave on Sep 12

Posted by Adrian Sanabria via Dailydave on Sep 12

Posted by Dave Aitel via Dailydave on Nov 02

In recent episodes we have discusses statically and dynamically typed languages and domain specific languages - topics that are much talked about in the community at the moment. In this episode we look at the foundation of programming languages : types. We explain what a type actually is, how type systems work and what polymorphism works.

This Episode is a round table discussion about Ultra-Large Scale Systems. In 2006, a number of authors (among them our guests Linda Northrop, Doug Schmidt, Kevin Sullivan, and Gregor Kiczales) have produced a report that addressed the following question: Given the issues with today's software engineering, how can we build the systems of the future that are likely to have billions of lines of code? In this episode, our guests discuss many of the issues that arise from this kind of system and provide an overview of the research areas that should be investigated in order to tackle the challenge. If you want to get more detailed information, you can read the ULS Report (PDF).

In this Episode we talked about the new POSA 4 book which has recently been published. We talk to two of the authors, Kevlin Henney and Frank Buschmann (the third author, Doug Schmidt was not available - and he had also been on the podcast a couple of times :-)). The book contains a pattern language for distributed systems. It contains 114 patterns that had been published before by many different other authors. The patterns have been rewritten to form a consistent language. We basically talked through the different sections of the book, which gives a really good overview over the challenges and the solutions of building distributed systems. These sections include From Mud to Structure, Distribution Infrastructure, Event Demultiplexing and Dispatching, Interface Partitioning, Component Patitioning, Application Contrl, Concurrency, Synchronization, Object Interaction, Adaptazion and Extension, Modal Behaviour, Resource Management and finally, Database Access. The book references several other previous works (as listed below). Interestingly, many of these referenced works and authors have also been discussed previously on the podcast. Here are the back references:

• Domain Driven Design, Eric Evans
• Messaging Patterns, Gregor Hohpe
• POSA 2 Patterns, Doug Schmidt
• Concurrency: Part 1, Part 2, Part 3 and the interview with Goetz and Holmes
• Remoting Patterns Part 1 and Part 2
• POSA3, Resource Management

This episode is an introduction to embedded system. It is an introduction in the sense that we cover many topics very briefly: upcoming episodes will provides details for many of these topics. We start by discussing what an embedded system is an what the important characteristics are. Among them is limited resources, concurrency, real time and hardware integration. We also discuss the range of embedded systems from small mirocontrollers to mobile phones to distributed real time embedded systems. We also cover the different business case for embedded systems (per unit cost) and some non-trivial developmental aspects (cross compilation debugging, heisenbugs). We close the episode by discussing some important architectural styles (time triggered, event-based, microkernels, state machines) as well as tools of the trade: languages, operating systems and middleware.

This episode is a conversation with Bruce Powel Douglass on real time systems. We started by discussing what real time software is, and explored the difference between hard and soft real time. We then looked at different scheduling strategies, and the meaning of terms like urgency and importance in the context of scheduling. Next was a discussion of typical architectural styles for real time systems and how architectures are described in this context. This led us to a discussion about the importance of modeling, formalisms and languages as well as the role of automatic code generation from those models. We then looked at how to model QoS aspects and the role of SysML for modeling real time systems. We then had a brief look at which programming languages are used these days for real time systems and the role of static analysis to determine various properties of those programs in advance. The last part of the discussion focused on some best practices for building real time systems, the challenges in distributed real time systems and how real time systems can be tested effectively.

In this Episode we're talking about Erlang with its creator Joe Armstrong. We started by looking at the history of the Erlang language and why it is so relevant today. We then looked at Joe's approach to Concurrency Oriented Programming and its main ingredients: share nothing, lightweight concurrency and pure message passing. We also compared this to the classic shared memory approach to concurrency. We then looked at other interesting aspects of Erlang, such as its functional nature (and why this is important to concurrency) and pattern matching. Next we discussed how to implement distribution and fault tolerance, and we took a look at OTP, the "application server" for Erlang. We concluded the conversation with a littel discussion about how Erlang was designed, it's current community as well as its future.

In this episode we talk with Jeff McAffer about building platforms. We start with a brief discussion about what a platform is in contrast to a framework or an application. Drawing from his experiences working on the Eclipse platform for years, Jeff talks with us about how to develop platforms, why developing a platform is different from developing an application, what makes a good platform great, and why API design becomes so extremely important for platforms. He provides us with some insights on how the development process and the client collaboration for platform development could look like and what has and has not worked in the past.

The majority of hacker attacks (70 %) are directed at weaknesses that are the result of problems in the implementation and/or architecture of the application. This session shows how you can protect your web applications (J2EE or .NET) against these attacks. The session covers lots of practical examples and techniques for attack. Furthermore, it shows strategies for defense, including a "Secure Software Development Lifecycle". A "Live Hacking" demo rounds it out. This is a session recorded live at OOP 2009. SE Radio thanks Bruce, SIGS Datacom and the programme chair, Frances Paulisch, for their great support!

This episode is a conversation with Jan Bosch about product line engineering (PLE). Jan has worked in various roles and industries and academia in the context of product lines. In this episode we look at Jan's view of what is next for product lines: software ecosystems. What is their relationship to PLE and how should PLE change to remain relevant?

Recording Venue: WebEx Guest: Wil van der Aalst Robert Blumen interviews Professor Wil van der Aalst of the Technical University of Eindhoven, one of the world’s leading researchers in business process management and workflow systems. Professor van der Aalst leads off with an overview of the main concepts in the field business processes, business process […]

Leslie Lamport won a Turing Award in 2013 for his work in distributed and concurrent systems. He also designed the document preparation tool LaTex. Leslie is employed by Microsoft Research, and has recently been working with TLA+, a language that is useful for specifying concurrent systems from a high level. The interview begins with a […]

Senior performance architect and author of *Systems Performance* Brendan Gregg talks with Robert Blumen about systems performance: how the hardware and OS layers affect application behavior. The discussion covers the scope of systems performance, systems performance in the software life cycle, the role of performance analysis in architecture, methodologies for solving performance problems, dynamic tracing and tracing tools such as DTrace, the disk and file subsystems, the CPU and memory subsystems, and the challenges virtualization poses for performance analysts.

Stefan Tilkov talks to Camille Fournier about the challenges developers face when building distributed systems, whether the can avoid building them at all, and what changes occur once they do.

Donny Nadolny of PagerDuty joins Robert Blumen to tell the story of debugging an issue that PagerDuty encountered when they set up a Zookeeper cluster that spanned across two geographically separated datacenters in different regions.

Edaena Salinas talks with Nicole Hubbard at KubeCon 2017. They discuss why WP engine is migrating from VMs to Kubernetes and how the migration is structured. Nicole explained the VM infrastructure at WP Engine and why there was a need to move...

Dr. Andrii Gakhov, author of the book Probabilistic Data Structures and Algorithms for Big Data Applications talks about probabilistic data structures and their application to the big data domain with host Robert Blumen.

The use of distributed and remote software teams have grown dramatically in the past five years, presenting new challenges for managers and engineers alike. Bryan Helmig talks about the best practices his company, Zapier, uses to manage remote software...

Learn how to simplify your application architecture with the introduction of a messaging system. You'll hear how different messaging patterns can make your application more flexible, easier to maintain, and improve its performance.

Bob Kepford discusses Decoupled CMS. Many CMS practitioners are adopting a decoupled approach to improve scale, allow for more specialized roles, and to separate data collection from delivery. Host Jeff Doolittle spoke with Kepford about what makes a Decoupled CMS different.

Sven Schleier and Jeroen Willemsen from the OWASP Mobile Application Security Verification Standard and Testing Guide project discuss mobile application security and how the verification standard and testing guide can be used to improve your app’s...

Dr. Daniel Zingaro and Dr. Leo Porter, co-authors of the book Learn AI-Assisted Python Programming, speak with host Jeremy Jung about teaching programming with the aid of large language models (LLMs). They discuss writing a book to use in Leo's introductory CS class and explore how GitHub Copilot de-emphasizes syntax errors, reduces the need to memorize APIs, and why they want students to write manual test cases. They also discuss possible ethical concerns of relying on commercial tools, their impact on coursework, and why they aren't worried about students cheating with LLMs.

Andreas Møller, founder of Toddle, a no-code tool for building scalable performant web applications, speaks with SE Radio's Brijesh Ammanath about no-code platforms. They discuss the role of developers in a no-code ecosystem and explore scalability and performance considerations, as well as enterprise adoption of no-code tools. Andreas also expands on why he built Toddle.dev and its unique features. Brought to you by IEEE Computer Society and IEEE Software.

_{-- Delivered by Feed43 service}

MSI puts its usual GAMING X and TWIN FROZR 7 magic on AMD's new mid-range Radeon RX 5500 XT. Check out our full review here."... [PCSTATS]

Brent Simmons, the developer of the NetNewsWire RSS reader, is questioning his decision to put an unread count next to each feed, reasoning that it encourages people to be too obsessive about reading every item:

Instead of a dozen bookmarks, people had a hundred feeds. Or two hundred. Or two thousand.

And there was a tyranny behind keeping track of unread items and showing an unread count. People reacted in different ways, but many people felt like they always had to go through everything.

Including me. To this day.

I did not know this was going to happen. That was not the idea: it was a side effect of reasonable (at the time) choices.

I like seeing these counts on feeds where I need to read all items that are posted, but that's only a small percentage of the 100-120 feeds I follow. It would be nice to turn that off for others I read more casually.

Feedly presents unread counts on each feed and folder of feeds. There's a Mark As Read button to clear a count, but when you click it, the confirmation dialog acts like it's an extremely consequential decision: "Are you sure you want to mark this entire source as read? This operation cannot be undone."

I've posed a question on the RSS-Public mailing list: Do you think feed readers should count unread items?

As Disney celebrates its 100th birthday, how much can you remember about its films?

In this video, Noam Chomsky talks about language at Google as part of the Authors@Google series.

In this question and answer session he discusses a number of topics, but the first is about universal grammar in which he provides an in-depth description of how his ideas on universal grammar have evolved over time.

Another interesting question he answers at the end of the session relates to the effect of email, instant messaging and the like on syntax and grammar (TXT Speak). Hear Chomsky's views on whether this is just a natural part of the evolution of language and how it's affecting our minds.

Nowadays, it seems that everything we do tends to be somehow automated. The very same is happening in electrical distribution systems. The distribution system at the medium voltage (MV) or low voltage (LV) levels is designed using different structures such... Read more

The post The essentials of automation applied to distribution systems via PLCs, SCADA, IEDs, and RTUs appeared first on EEP - Electrical Engineering Portal.

Communication systems of electric utilities have become increasingly critical to electric system protection, operation, and maintenance. For fast tripping and clearing of system faults, communication-aided relaying has become a common protection scheme, particularly in line protection. Control centers depend on... Read more

The post Schematics and docs needed for communication systems of substation protective relaying system appeared first on EEP - Electrical Engineering Portal.

Electrical distribution systems comprise a large number of remote applications and locations, and it has traditionally been challenging to monitor and regulate these remote applications and sites. Utility companies have been installing remote terminal/telemetry units, often known as RTUs, at... Read more

The post Three most common SCADA applications in MV/LV distribution systems you SHOULD know appeared first on EEP - Electrical Engineering Portal.

Title: Idioms- Body 3
Topic: Idioms
Level: Advanced
Information: Choose the correct answer.
Link: https://www.usingenglish.com/quizzes/569.html

Title: Idioms- Animals 2
Topic: Idioms
Level: Advanced
Information: Choose the correct answer.
Link: https://www.usingenglish.com/quizzes/573.html

Title: Idioms- Furniture and Household Fittings
Topic: Idioms
Level: Advanced
Information: Choose the correct answer.
Link: https://www.usingenglish.com/quizzes/576.html

Title: Idioms- Sport 2
Topic: Idioms
Level: Advanced
Information: Choose the correct answer.
Link: https://www.usingenglish.com/quizzes/583.html

Title: Idioms- Work
Topic: Idioms
Level: Advanced
Information: Choose the correct answer.
Link: https://www.usingenglish.com/quizzes/584.html

Title: Mr. Mrs. Miss Ms
Topic: Vocabulary
Level: Beginner
Information: Select whether the full name in each statement below should include Mr, Miss, Mrs or Ms.
Link: https://www.usingenglish.com/quizzes/612.html

A voltage drop is the total amount of voltage loss that happens through all or part of an electric circuit due to impedance and other factors. The more the voltage drops in the system, the more negative impacts will likely... Read more

The post Voltage Drop Analysis and Calculation Essentials (MS Excel Sheet Bonus) appeared first on EEP - Electrical Engineering Portal.

GE and EDF signed an exclusive agreement for EDF to acquire part of GE Steam Power’s nuclear power business.

The utility's five-year capital plan totals $63 billion, 80% of which will support investments in grid modernization and zero or lower-carbon emitting generation.