Profile cover photo
Profile photo
Jay Fields
Jay's posts

Post has attachment
Curious Customer
I currently work on a pretty small team, 4 devs (including myself). We have no one dedicated strictly to QA. A few years ago we ran into a few unexpected issues with our software. I hesitate to call them bugs, because they only appeared when you did things ...

Post has attachment
Maintainability and Expect Literals
Recently, Stephen Schaub asked the following on the wewut group : Several of the unit test examples in the book verify the construction of both HTML and plain text strings. Jay recommends using literal strings in the assertions. However, this strikes me as ...

Post has attachment
Drop Books
The vast majority of books I purchase are for my own enjoyment, but not all of them. There are a few books that I buy over and over, and drop on the desks of friends and colleagues. These books, all technical, are books that I think most programmers will be...

Post has attachment
Unit Testing Points of View, Probably
Michael Feathers , Brian Marick , and I are collaborating to create a new book: Unit Testing Points of View ... probably. Origin In 2014 Martin Fowler provided Technical Review for Working Effectively with Unit Tests . As part of his feedback he said someth...

Post has attachment
My Answers for Microservices Awkward Questions
Earlier this year, Ade published Awkward questions for those boarding the microservices bandwagon . I think the list is pretty solid, and (with a small push from Ade) I decided to write concise details on my experience. I think it's reasonable to start with...

Post has shared content
Slides and video recording (Spanish) for my "Elegant?? Unit Testing" talk from #freakend15 are now available.

Video (Spanish):

Big thanks to +Jay Fields for writing #wewut

#androiddev #unittesting

Post has attachment
Experience Report: Weak Code Ownership
In 2006 Martin Fowler wrote about Code Ownership . It's a quick read, I'd recommend checking it out if you've never seen it. At the time I was working at ThoughtWorks; I remember thinking "Clearly Strong makes no sense and I have no idea what scenario would...

Post has attachment
Preview Arbitrary HTML
I'm a big fan of for sharing code. It's fantastic for quickly putting something online to talk over with someone else. I've often found myself wishing for something that allowed me to share rendered HTML in the same way. For example...

Post has attachment
LTR Org Chart
Most traditional organizations have an Org Chart that looks similar to the following: Org Charts displayed in this way emphasize the chain of command. A quick look at a node in this Org Chart will let you know who someone reports to and who reports to them....

Post has attachment
Jay Fields commented on a post on Blogger.
1. It is, also.
2. Why can't it be both? All of mine are.
3. A web UI moves the files, cron starts and stops
4. A jar
5. A little of both
6. Yes
7. Yes
8. A can use team B's if they want to keep up with the API or B can run their own copy of the service if they want to stick with a specific API
9. Consumer's responsibility
10. Conventions.
11. Team discussion when deviating from established conventions
12. Outside of code, they're not. Within code, the conventions span the existing services, so there's plenty of reference code.
13. Code review for all code submitted by team members that have been on the team less than 6 months
14. Discussion and an open mind
15. Yes
16. Custom monitoring code that constantly evolves. Monitoring code is as valuable (if not more) than the business logic, and is treated as such.
17. Logging. More aggressive approaches were originally implemented, and never used. I'm still somewhat surprised by that.
18. A running process that provides value and introduces no more risk than the team is comfortable with.
19. A running process that interacts via some type of socket and processes data in some interesting way.

This approach likely does not scale.
Wait while more posts are being loaded