nobody

1、为什么做代码检测功能 不管使用哪种语言，哪种框架，只要你编程，都会遇到些所谓的“坑”，只能靠代码检测工具自动发现这些问题，因为人脑或者是人并不总是最靠谱的。也行你已经用了阿里的检查插件P3C，或者SonarQube、JArchitect、checkstyle或者findbugs等等工具来检测来避免，现在介绍一款java的基于字节码的我们可以自定义的，比较通用的检测工具。2、ArchUnit 使用这个工具的目的，其实想利用java反射的方式，基于字节码解析...

Google首席工程师Joshua Bloch谈如何设计优秀的APIHow to Design a Good API and Why it MattersWhy is API Design Important?APIs can be among a company's greatest assets_ Customers invest

java SPI 与cooma（dubbo 微容器改良品）--2 之Cooma SPI     Cooma是一个极简、灵活的开源Java微容器（microcontainer）实现，其实现源于dubbo的spi（它来源于java spi）。让我们看一下简单的demo：概念：Extension Point，扩展点，要扩展的接口。提倡面向接口的编程，这些接口定义就变成

java设计模式之单例模式（Singleton pattern）单例模式的定义：Singleton pattern restricts the instantiation of a class and ensures that only one instance of the class exists in the java virtual machine. The singlet

REST API 设计规则URIsREST API用URI（Uniform Resource Identifiers ）来表示资源。例如： http://api.example.restapi.org/france/paris/louvre/leonardo-da-vinci/mona-lisa下面的URI就可读性很差： http://api.example.r

Effective Java1.考虑使用静态工厂方法而不是构造函数例如：Integer类中的： public static Integer valueOf(int i) { if (i >= IntegerCache.low && i <= IntegerCache.high) return IntegerCache.cache[i + (-

高效能程序员的修炼一、永远都是你的错在怨天尤人之前，我们应该自我反省、努力把自身的问题解决了。、代码产权的另一方面是代码责任。无论你的软件出现什么样的问题--甚至最开始错的地方根本就不是你的代码-你也应该总是假定问题出在你的代码里，并且根据这个假设采取行动。二、大道至简你永远都有简化的空间。作为一个软件开发者，你就是自己最大的敌人。你越早认识到这点，你的境况就会

    为了美感和欣赏！艺术家们提出了设计即化妆！为了有共同的语言交流，就制定了化妆规则！     代码记得分层，为了避免循环依赖，上层只能调用下层，严格的只能调用临近的下层，而不能跨层。如果跨层，可以用事件的方式（后门，但不能随便乱用啊）。    注：同层之间最好不要相互调用，因为也会带来循环依赖！https://msdn.microsoft.com/en-us/library/ee658109...

利用Swagger Maven Plugin生成Rest API文档Swagger Maven PluginThis plugin enables your Swagger-annotated project to generate Swagger specs and customizable, templated static documents during t

Building Maintainable Software-java篇之 Write Clean CodeWriting clean code is what you must do in order to call yourself a professional.—Robert C. MartinGuideline:• Write clean code.

Building Maintainable Software-java篇之Write Simple Units of Code  Each problem has smaller problems inside.                                                              —MartinFowlerGuide

Building Maintainable Software-java篇之Write Code OnceNumber one in the stink parade is duplicated code.—Kent Beck and Martin Fowler,Bad Smells in CodeGuideline:• Do not copy code.

Building Maintainable Software-java篇之Keep Unit Interfaces SmallBunches of data that hang around together really ought to be made into their own object.                           —Marti

Building Maintainable Software-java篇之Separate Concerns in Modules  In a system that is both complex and tightly coupled, accidents are inevitable.—Charles Perrow’s Normal Accidentstheory in

Building Maintainable Software-java篇之Couple Architecture Components LooselyThere are two ways of constructing a software design: one way is to make it so simplethat there are obviously no de

Building Maintainable Software-java篇之Keep Architecture Components BalancedBuilding encapsulation boundaries is a crucial skill in software architecture.                    —George H. F

Building Maintainable Software-java篇之Keep Your Codebase SmallProgram complexity grows until it exceeds the capability of the programmer who must maintain it.—7th Law of Computer Programming

Building Maintainable Software-java篇之Automate TestsKeep the bar green to keep the code clean.—The jUnit mottoGuideline:• Automate tests for your codebase.• Do this by writing autom

Building Maintainable Software-java篇之Write Short Units of CodeAny fool can write code that a computer can understand. Good programmers writecode that humans can understand.