Skip to main content

Home/ Coders/ Group items tagged software

Rss Feed Group items tagged

Fabien Cadet

2000: Things You Should Never Do, Part I - Joel on Software - 1 views

    "There's a subtle reason that programmers always want to throw away the code and start over. The reason is that they think the old code is a mess. And here is the interesting observation: they are probably wrong. The reason that they think the old code is a mess is because of a cardinal, fundamental law of programming:

    It's harder to read code than to write it.

Alvar Laigna

OpenAI - 7 views

    Discovering and enacting the path to safe artificial general intelligence.
Fabien Cadet

Service Oriented Agony | 8th Light, 2012-02-01 by Bob Martin - 7 views

  • The structure seems obvious to system designers who have grown tired of single monolithic systems and want to break those systems up into components and services. What could be more natural than to break the system along the lines of data base managment?
  • Unfortunately this is a huge violation of the Single Responsibility Principle — or its big brother the Common Closure Principle.
  • These principles tell us to group together things that change together, and keep apart things that change for different reasons.
  • ...6 more annotations...
  • When you separate things that change for the same reasons, you have to make changes in many different places in the system.
  • So it’s a lot of work just to get anything working.
  • Moreover, when you group together things that change for different reasons, you expose the components of the system to collateral damage, thrashing, CM collisions, and a whole host of other problems.
  • So what’s the solution? First of all, I question whether the system needed to be partitioned into services.
  • Services are expensive and complicated, you should only create them if you absolutely need to. It’s always easier to live in a single process. Remember Martin Fowler’s first law of distributed objects: Don’t distribute your objects.
  • Many systems could be streamlined, and development made much faster, if the system designers paid more attention to the Single Responsibility Principle.
Fabien Cadet

Building Real Software: Lessons in Software Reliability, 2009-08-30 by Jim Bird - 11 views

    « It's unfortunate that few developers are familiar with The MITRE Corporation's Common Weakness Enumeration list of common software problems. [...] »
Fabien Cadet

[video] InfoQ: Development at the Speed and Scale of Google, 2010-12-13 by Ashish Kumar - 4 views

    « Ashish Kumar presents how Google manages to keep the source code of all its projects, over 2000, in a single code trunk containing hundreds of millions of code lines, with more than 5,000 developers accessing the same repository. »
Fabien Cadet

Software Development is not Just Coding « CodeDependents, 2011-06-06 by Benja... - 15 views

  • Many developers approach any sort of planning with apprehension if not outright disgust.
  • Whatever it might be we need to move beyond the “all process is evil” mentality. Yes there will be meetings but you will shock yourself at how much faster you are in the end.
    If you want a quality seo service please click here. Many people said about seo. But do not understand about seo itself. I will help you. Please contact me on yahoo messenger .. or
Fabien Cadet

« Big Ball of Mud » (aka. Spaghetti Code) , by Brian Foote and Joseph Yoder (... - 3 views

  • The class of systems that we can build at all may be larger than the class of systems we can build elegantly, at least at first.
    « While much attention has been focused on high-level software architectural patterns, what is, in effect, the de-facto standard software architecture is seldom discussed. This paper examines this most frequently deployed of software architectures: the BIG BALL OF MUD. A BIG BALL OF MUD is a casually, even haphazardly, structured system. Its organization, if one can call it that, is dictated more by expediency than design. Yet, its enduring popularity cannot merely be indicative of a general disregard for architecture. »
Fabien Cadet

Deployment pipeline anti-patterns | Continuous Delivery - 6 views

    "So when he found a bug and it was fixed by a developer, he had to wait ages before he could deploy the build with the fix into his testing environment to check it.
    This problem results from a combination of two anti-patterns that are common when creating a deployment pipeline:
    * insufficient parallelization,
    * and over-constraining your pipeline workflow.
Fabien Cadet

Your Architecture Sucks and I Don't Care, by Ryan, 2011-01-03 | Friendly Dingo Blog - 10 views

    "Besides, who am I to say your architecture sucks? And why don't I care? Because I am your users, and I don't care what your codebase looks like, I don't care what it's called, and I don't care what language it's written in. I care that it solves my problem in the simplest and fastest way possible."
1 - 20 of 45 Next › Last »
Showing 20 items per page