10 Matching Annotations
  1. Nov 2022
    1. Clean code examples (YouTube)Why Are You Still Creating CRUD APIs?Remove Your If-Else and Switch CasesWhy Cognitive and Cyclomatic Complexity Matters in Software DevelopmentWriting Cleaner Code (With Examples)Resources for the curious📚 Source Code (GitHub) by Nicklas Millard, the authorRESTful API Design by MicrosoftArchitectural Styles and the Design of Network-based Software Architectures by R.T. FieldingWhat is REST by codeacademyIs Crud Bad For Rest? by Boris LublinskyHATEOAS Driven REST APIs by restfulapi.netHATEOAS — a simple explanation by Bartosz JedrzejewskiWhy HATEOAS is useless and what it means for REST by Andreas ReiserRESTful Considered Harmful by Tomasz NurkiewiczTask-Based UI on cqrs.wordpress.comCRUD is an antipattern by Mathias VerraesWhy REST sucks by Troy A. Griffitts

      Useful links for Web & generic programming.

    2. RPC-like but still REST-full is way more preferred than those rotten CRUD designs.

  2. Dec 2021
  3. Nov 2021
    1. refactoring code

      Not much to do about refactoring, but rather about structuring your code-base.

    2. Practical rules about discovering the sweet-sport of Low Coupling vs High Cohesion - not much to do about refactoring!

    1. because commonly an API is not intended to handle high performance requirements.

      ... while microservices do (are supposed to "handle large amounts of information ... cannot accept idle services"

    1. Building resilient distributed software means APIs & data-scemas can have a frictionless evolution.

    1. positional arguments vs configuration vs builders, async vs sync, global vs local, stateful vs stateless, static vs instance, constructors vs factories, callbacks vs futures, functional vs object oriented, events vs anything and infinitely many more

      Interesting collection of programming architectural choice