Category: Uncategorised

St. John of Damascus, an influential theologian of the 8th century, held a high view of the human body, especially in the context of Christian doctrine. He emphasized the integral unity of the human person, body, and soul, arguing that both are essential to human identity and salvation.

In his most famous work, “The Fount of Knowledge,” particularly in the section known as “On the Orthodox Faith,” St. John of Damascus elaborates on the significance of the body in the Christian life. He argues that the human body is not inherently evil or something to be despised. Instead, it is created by God, and as such, it is good and worthy of respect. The body is viewed as a temple of the Holy Spirit, particularly after the Incarnation of Christ, who took on human flesh. This act of God becoming man sanctified the human body and elevated its dignity.

St. John also emphasizes that the body will be resurrected and glorified at the end of times, reflecting the belief in the resurrection of the dead. This underscores his view that the body, although it may suffer and die, is destined for eternal life in union with the soul.

Overall, St. John of Damascus promotes a holistic view of human nature, where the body is seen as a sacred and integral part of what it means to be human.

In other words, nothing of the sorts of sitting in cloud playing the harp for ever and ever 😉

Hal Abelson, a prominent computer scientist and co-author of the book *”Structure and Interpretation of Computer Programs,”* believes that “Computer Science” is a misleading name for the field. His critique stems from the idea that the discipline is not primarily about computers or science in the traditional sense.

1. Not Just About Computers: Abelson argues that the field is more about the principles of computation and the process of creating abstractions to solve problems, rather than the physical machines we call computers. The focus is on the algorithms, languages, and theories that underpin these machines, not the machines themselves.

2. Not a Traditional Science: Unlike fields like physics or chemistry, which involve the study of natural phenomena, computer science is concerned with the creation of artificial systems. It’s more akin to engineering or mathematics, where the goal is to construct models, design systems, and solve problems, rather than to discover natural laws.

Because of these reasons, Abelson suggests that a more accurate name might be something like “Informatics” or “Computational Science,” which better capture the essence of the discipline as the study of computation, information, and the processes that manipulate them.

Overview:

This book focuses on the practical aspects of visualizing, documenting, and exploring software architecture. Simon Brown emphasizes the importance of clear and effective communication among developers, stakeholders, and other team members through proper documentation and visualization techniques.

Key Concepts:

1. C4 Model:

– Context Diagram: Provides a high-level overview of the system, showing how it interacts with external users and systems.
– Container Diagram: Breaks down the system into containers (applications, services, databases, etc.) and shows their interactions.
– Component Diagram: Details the internal structure of each container, illustrating components and their relationships.
– Code Diagram: Focuses on the implementation details of individual components, typically represented by UML or other detailed design diagrams.

2. Documentation:

– Purpose and Audience: Understanding the need for different types of documentation tailored to various audiences (developers, stakeholders, operations, etc.).
– Structuring Documentation: Using templates and consistent formats to make documentation more accessible and maintainable.
– Living Documentation: Keeping documentation up-to-date with the evolving software through automation and regular updates.

3. Exploration:

– Static and Dynamic Views: Combining static structure with dynamic behavior to provide a comprehensive understanding of the system.
– Architectural Decisions: Documenting the rationale behind architectural choices, including trade-offs and alternatives considered.
– Technical Debt: Recognizing and addressing technical debt to maintain the health and sustainability of the architecture.

4. Tools and Techniques:

– Diagramming Tools: Recommendations for tools that can help create and maintain architecture diagrams (e.g., PlantUML, Structurizr).
– Code Analysis Tools: Using tools to analyze codebases and generate visualizations that reflect the current state of the architecture.
– Workshops and Reviews: Conducting architecture workshops and reviews to gather feedback and ensure alignment with business goals and technical constraints.

5. Case Studies:

– The book includes real-world case studies to illustrate how the concepts and techniques can be applied in practice. These case studies provide insights into common challenges and solutions in documenting and exploring software architectures.

Key Takeaways:

– Communication is Key: Effective communication of the architecture is crucial for collaboration and alignment within the team and with stakeholders.
– Keep it Simple: Aim for simplicity in both diagrams and documentation to avoid overwhelming or confusing the audience.
– Iterate and Improve: Treat documentation as an iterative process, continuously refining it as the system evolves.
– Use the Right Tools: Leverage appropriate tools to create and maintain accurate and useful documentation.

Simon Brown’s approach emphasizes that good software architecture documentation is not about creating perfect diagrams but about ensuring that the architecture can be easily understood, communicated, and evolved.

Overview

“Designing Data-Intensive Applications” is a comprehensive guide to building robust, scalable, and maintainable data systems. Martin Kleppmann delves into the architecture and design principles necessary for handling large volumes of data, making the book essential reading for software engineers, system architects, and data professionals.

Key Concepts

1. Data Systems and Scalability

Kleppmann discusses the characteristics of modern data systems and the challenges associated with scalability, including performance bottlenecks and data distribution across multiple machines.

2. Data Models and Query Languages

The book examines different data models (relational, document, graph, etc.) and query languages (SQL, NoSQL) to help readers understand the trade-offs involved in choosing the right data model for their applications.

3. Storage and Retrieval

Detailed exploration of storage engines, covering log-structured storage, B-trees, and other data structures used for indexing and data retrieval. Kleppmann explains how these systems work under the hood to optimize performance.

4. Encoding and Evolution

Kleppmann covers data serialization formats like JSON, XML, Avro, and Protocol Buffers. He discusses how to handle schema changes and data evolution over time without disrupting applications.

5. Replication

The book explains different replication strategies, including leader-based and multi-leader replication, to ensure data availability and consistency across distributed systems.

6. Partitioning

Kleppmann addresses data partitioning (sharding) techniques to distribute data across multiple machines, ensuring scalability and fault tolerance.

7. Transactions

In-depth discussion on the principles of transactions, including ACID properties, isolation levels, and distributed transactions, and their importance in maintaining data integrity.

8. The Trouble with Distributed Systems

Kleppmann explains the challenges of building distributed systems, such as network faults, latency issues, and consensus algorithms like Paxos and Raft to achieve reliability.

9. Consistency and Consensus

The book covers different consistency models (strong, eventual, causal) and consensus protocols necessary for ensuring data correctness in distributed environments.

10. Batch Processing

An exploration of batch processing frameworks like Hadoop, focusing on how to process large volumes of data efficiently.

11. Stream Processing

Discussion on stream processing systems like Kafka and real-time data processing techniques to handle continuous data streams.

Conclusion

Kleppmann’s book is a deep dive into the principles and practices of designing robust data-intensive applications. It offers a balanced blend of theoretical concepts and practical implementations, making it a valuable resource for anyone involved in building or maintaining data systems.

Arc Browser tries to take for itself the role of the main OS where it is installed. And it does a great job!

But the thing is: the OS already deals with what Arc wants do deal with. Like window management, for example. And I just can’t deal with two actors trying to solve the same thing. Or two competing and different ways to do something.

For the Christians are distinguished from other men neither by country, nor language, nor the customs which they observe. For they neither inhabit cities of their own, nor employ a peculiar form of speech, nor lead a life which is marked out by any singularity. The course of conduct which they follow has not been devised by any speculation or deliberation of inquisitive men; nor do they, like some, proclaim themselves the advocates of any merely human doctrines. But, inhabiting Greek as well as barbarian cities, according as the lot of each of them has determined, and following the customs of the natives in respect to clothing, food, and the rest of their ordinary conduct, they display to us their wonderful and confessedly striking method of life. They dwell in their own countries, but simply as sojourners. As citizens, they share in all things with others, and yet endure all things as if foreigners. Every foreign land is to them as their native country, and every land of their birth as a land of strangers. They marry, as do all [others]; they beget children; but they do not destroy their offspring. They have a common table, but not a common bed. They are in the flesh, but they do not live after the flesh. 2 Corinthians 10:3 They pass their days on earth, but they are citizens of heaven. Philippians 3:20 They obey the prescribed laws, and at the same time surpass the laws by their lives. They love all men, and are persecuted by all. They are unknown and condemned; they are put to death, and restored to life. 2 Corinthians 6:9 They are poor, yet make many rich; 2 Corinthians 6:10 they are in lack of all things, and yet abound in all; they are dishonoured, and yet in their very dishonour are glorified. They are evil spoken of, and yet are justified; they are reviled, and bless; 2 Corinthians 4:12 they are insulted, and repay the insult with honour; they do good, yet are punished as evil-doers. When punished, they rejoice as if quickened into life; they are assailed by the Jews as foreigners, and are persecuted by the Greeks; yet those who hate them are unable to assign any reason for their hatred.

To sum up all in one word — what the soul is in the body, Christians are in the world. The soul is dispersed through all the members of the body, and Christians are scattered through all the cities of the world. The soul dwells in the body, yet is not of the body; and Christians dwell in the world, yet are not of the world. The invisible soul is guarded by the visible body, and Christians are known indeed to be in the world, but their godliness remains invisible. The flesh hates the soul, and wars against it, 1 Peter 2:11 though itself suffering no injury, because it is prevented from enjoying pleasures; the world also hates the Christians, though in nowise injured, because they abjure pleasures. The soul loves the flesh that hates it, and [loves also] the members; Christians likewise love those that hate them. The soul is imprisoned in the body, yet keeps together that very body; and Christians are confined in the world as in a prison, and yet they keep together the world. The immortal soul dwells in a mortal tabernacle; and Christians dwell as sojourners in corruptible [bodies], looking for an incorruptible dwelling in the heavens. The soul, when but ill-provided with food and drink, becomes better; in like manner, the Christians, though subjected day by day to punishment, increase the more in number. God has assigned them this illustrious position, which it were unlawful for them to forsake.

If I were the devil… If I were the Prince of Darkness, I’d want to engulf the whole world in darkness. And I’d have a third of its real estate, and four-fifths of its population, but I wouldn’t be happy until I had seized the ripest apple on the tree — Thee. So I’d set about however necessary to take over the United States. I’d subvert the churches first — I’d begin with a campaign of whispers. With the wisdom of a serpent, I would whisper to you as I whispered to Eve: ‘Do as you please.

To the young, I would whisper that ‘The Bible is a myth.’ I would convince them that man created God instead of the other way around. I would confide that what’s bad is good, and what’s good is ‘square.’ And the old, I would teach to pray, after me, ‘Our Father, which art in Washington…

And then I’d get organized. I’d educate authors in how to make lurid literature exciting, so that anything else would appear dull and uninteresting. I’d threaten TV with dirtier movies and vice versa. I’d pedal narcotics to whom I could. I’d sell alcohol to ladies and gentlemen of distinction. I’d tranquilize the rest with pills.

If I were the devil I’d soon have families at war with themselves, churches at war with themselves, and nations at war with themselves; until each in its turn was consumed. And with promises of higher ratings I’d have mesmerizing media fanning the flames. If I were the devil I would encourage schools to refine young intellects, but neglect to discipline emotions — just let those run wild, until before you knew it, you’d have to have drug sniffing dogs and metal detectors at every schoolhouse door.

Within a decade I’d have prisons overflowing, I’d have judges promoting pornography — soon I could evict God from the courthouse, then from the schoolhouse, and then from the houses of Congress. And in His own churches I would substitute psychology for religion, and deify science. I would lure priests and pastors into misusing boys and girls, and church money. If I were the devil I’d make the symbols of Easter an egg and the symbol of Christmas a bottle.

If I were the devil I’d take from those who have, and give to those who want until I had killed the incentive of the ambitious.

And what do you bet I could get whole states to promote gambling as the way to get rich? I would caution against extremes and hard work in Patriotism, in moral conduct. I would convince the young that marriage is old-fashioned, that swinging is more fun, that what you see on the TV is the way to be. And thus, I could undress you in public, and I could lure you into bed with diseases for which there is no cure. In other words, if I were the devil I’d just keep right on doing what he’s doing.

– Paul Harvey, good day.

To find out how much thought has gone into an opinion, ask the following questions:

1. What evidence would prove X wrong?
2. If you were a lawyer representing the other side, what’d your argument be?
3. What do you want to be true?
4. What’s the best critique of X you’ve come across?
5. Who’s the smartest person who disagrees with X?
6. Where doesn’t X apply?
7. What are the tradeoffs?
8. If X turned out not to be true, what do you think is the next best hypothesis?

Source: unknown

• Longevity: Software should be written as robustly as possible to maximize longevity. Consider edge cases, test comprehensively, and use statically typed languages. Avoid dependencies that are complex or brittle.
• Maintainability: Use frameworks that will make software easily maintainable by developers who come after you. Development should only require a minimal toolchain, and one that’s demonstrated a good history of stability and support.
• Transparency: Write code simply and elegantly. Use abstractions, but don’t abstract so heavily as to obfuscate. It should be obvious how code works not only to you, but for any others who might read it in the future.
• Evolvability: It should be possible to improve software over time. A good compiler and test suite should let future developers who aren’t deeply familiar with the existing code make those improvements safely.
• Scalability: To ensure that production software will work properly, write an extensive test suite and deploy the prototype in high-fidelity pre-production environments before taking it live.

Source: brandur.org/10000-years

• Longevity: The clock should be accurate even after 10,000 years, and must not contain valuable parts (such as jewels, expensive metals, or special alloys) that might be looted.
• Maintainability: Future generations should be able to keep the clock working, if necessary, with nothing more advanced than Bronze Age tools and materials.
• Transparency: The clock should be understandable without stopping or disassembling it; no functionality should be opaque.
• Evolvability: It should be possible to improve the clock over time.
• Scalability: It should be possible to build working models of the clock from table-top to monumental size using the same design.

Source: brandur.org/10000-years