Martin Fowler
E175369
Martin Fowler is a prominent software engineer and author known for his influential work on software design, refactoring, and agile methodologies.
All labels observed (1)
| Label | Occurrences |
|---|---|
| Martin Fowler canonical | 5 |
Statements (50)
| Predicate | Object |
|---|---|
| instanceOf |
author
ⓘ
blogger ⓘ software engineer ⓘ speaker ⓘ |
| associatedWith |
Agile Manifesto
ⓘ
Extreme Programming (XP) ⓘ
surface form:
Extreme Programming
|
| authorOf |
Analysis Patterns: Reusable Object Models
ⓘ
Continuous Integration (contributor) ⓘ Domain-Specific Languages ⓘ NoSQL Distilled ⓘ Patterns of Enterprise Application Architecture ⓘ Refactoring: Improving the Design of Existing Code ⓘ
surface form:
Refactoring (2nd Edition, with Kent Beck and others)
Refactoring: Improving the Design of Existing Code ⓘ UML Distilled ⓘ |
| birthYear | 1963 ⓘ |
| blog | https://martinfowler.com ⓘ |
| contributedTo |
definition of enterprise application patterns
ⓘ
popularization of agile practices ⓘ popularization of refactoring ⓘ |
| education |
University of Sheffield
ⓘ
surface form:
University of Sheffield (attended)
|
| employer | Thoughtworks ⓘ |
| field | software engineering ⓘ |
| hasConcept |
Continuous Integration practices
ⓘ
Microservices trade-offs ⓘ Refactoring code smells ⓘ Strangler Fig pattern ⓘ |
| influencedBy |
Kent Beck
ⓘ
Ward Cunningham ⓘ |
| jobTitle | Chief Scientist at Thoughtworks ⓘ |
| knownFor |
agile methodologies
ⓘ
enterprise application architecture ⓘ refactoring ⓘ software design ⓘ |
| language | English ⓘ |
| name | Martin Fowler self-link ⓘ |
| nationality | British ⓘ |
| residence |
United States of America
ⓘ
surface form:
United States
|
| signatoryOf | Agile Manifesto ⓘ |
| specializesIn |
agile software development
ⓘ
domain-specific languages ⓘ enterprise software architecture ⓘ object-oriented design ⓘ refactoring techniques ⓘ |
| website | https://martinfowler.com ⓘ |
| writesAbout |
continuous delivery
ⓘ
continuous integration ⓘ evolutionary architecture ⓘ microservices ⓘ software architecture ⓘ testing strategies ⓘ |
Referenced by (5)
Full triples — surface form annotated when it differs from this entity's canonical label.