-
Recent Posts
- Chapter 5: Unit Testing the Logger and Client
- Chapter 4: Logger and Server Enhancements
- Chapter 3: Enhancing Logging Code
- Chapter 2: Starting a Simple Logging Application
- Chapter 1: “Hello World” with ZeroMQ
- Intro: Messaging for Raspberry Pi
- Linux Sockets: Which process listens to a port?
- Our Confusion with Software
- Thinking in Code
- Code Reviews: A Discussion
- Easy Py Messaging
- Functional Refactoring for JavaScript
- The Actual Cost of Duplicated Code
- Complexity for JavaScript
- A Basis for Clean Code: Magic 7 +/- 2
- Test Driven Development
- Duplicated Code
- Duplicated Code: What to do?
- Introduction
Recent Comments
Microservice Catalog… on The Actual Cost of Duplicated… archer920gmailcom on Linux Sockets: Which process l… Dave Crenshaw on A Basis for Clean Code: Magic… Archives
Categories
- 0MQ
- analysis
- arduino
- clone
- code reading
- code review
- distributed systems
- functional
- interview
- IoT
- java
- javascript
- linux
- messaging
- networking
- node.js
- problems
- psychology
- python
- raspberry pi
- RaspberryPi
- raspbian
- readings
- refactor
- software
- software development
- stories
- techniques
- test
- testing
- therapy
- Uncategorized
- unittest
- zeromq
- zmq
Meta
-
Recent Posts
Monthly Archives: May 2017
Linux Sockets: Which process listens to a port?
Developing software using sockets almost always involves starting, stopping, debugging multiple processes, opening and closing sockets. The processes may or may not work properly as differing stages of development creates “interesting” problems. To complicate matters, multiple systems frequently add to … Continue reading
Posted in linux, problems, python, software, software development, techniques, therapy, Uncategorized
1 Comment
