Dude, Wasn't That Native Coding?

Thoughts and reflections from a programming veteran.

Browse by Tags

Tagged Content List
  • Blog Post: Agility: Automation for Better Outcomes and Feedback

    A bad habit of several developers has to do with entering in a long tunnel of coding for an application project, relegating a more or less acceptable executable for the last project stages. That has several risks: Feedback from users and customers delayed, what can carry a poor customer satisfaction...
  • Blog Post: From Classes To Components

    In n-tier, distributed applications, we have to decide which logic deploy where. Those deployments are all about installing components in specific places but, what are components exactly? What distinguishes a component with respect of a mere class? Actually, as classes do, components take ownership...
  • Blog Post: Software Architecture: Past, Present and Future

    What is exactly software architecture? Do we really need it? Why have we only recently been discussing it? Is there suddenly a contagious fever about software architecture infecting those who claim to be architects? Who are they actually: gurus, just senior developers, or maybe smooth-talkers? These...
  • Blog Post: Architecture Best Practices

    In "Last Call To Design Patterns" we described design patterns as "reusable solutions for frequent problems". It's all about thoughtful approaches to avoid common pitfalls And, actually, Patterns are just one of a set of disciplines which help us to achieve software easy to understand and maintain...
  • Blog Post: Passing Data Between Layers and/or Tiers

    While we were commenting some high-level strategies for data-access in a previous article , we mentioned a popular pattern used to interchange information between layers or tiers . We are talking about the Data Transfer Object (DTO) pattern . As the MS Patterns & Practices ' book "Enterprise Solution...
  • Blog Post: Data Access Strategies

    We have seen in the post about 3-Layer architectures , that the Data Access Layer isn't the persistence repository, but a set of strategies for accessing it The challenge you as an architect have to face when designing this layer is multiple: How much possible is the RDBMS being replaced for a...
  • Blog Post: 3-Tier, 3-Layer, MVC: a Trio of Famous Trios

    Contemporary applications are being based on three popular architectural approaches. They are 3-layered architecture 3-tier architecture Model-View-Controller architecture There exists certain degree of confusion between all the three approaches. Mostly the first two are often referred...
  • Blog Post: Layered Applications: Let's Talk About Business

    I remember a time when applications were just end to end programs, collections of lines of code with no distinction between presentation, domain logic and data access. Such kind of applications is remembered as spaghetti code Fortunately nowadays enterprise applications are made in a better organized...
  • Blog Post: Aims and Means of Asymmetric Cryptography

    Usually we tend to center the concept of Authentication to mere users, through and exhibited password as a credential But beyond the user, how to be sure about authenticity of other assets ? For example, how can we be sure about, once the user is authenticated, every received message, claiming in...
  • Blog Post: How Sure Are You About Security?

    Even though it´s surprising, an important number of architects don't worry enough about security aspects Talking with some of them, they considered that Security is a topic so complex -they are right in this appreciation- that developers don't have to care about it, just delegating its concerns to...
  • Blog Post: An Old Antipattern: "Too Much Architecture"

    At least in Software Engineering, but I guess the same applies to other sciences, there are ideas, concepts and paradigms easy to understand, but not so easy to implement in practice I remember, for instance, I understood very quickly OOP. It was pretty clear that Bird, Dog and Cat were subclasses of...
  • Blog Post: Fighting Against Coupling: a Moment for Reflection

    One of the most recurrent problems we have to face, as aspiring architects, is the problem of dealing with highly adaptable applications for different environments For instance, we need to build an application able to access a DB/2 database in one environment, an Oracle database in another one, and...
  • Blog Post: Two-Phase Commit (2PC): Coordinating Transactions in Distributed Environments

    There was a time when applications were isolated as a common issue, and having each one just one repository was usual Sometimes, we needed to update diverse records to the repository, let's say a purchase order header with its purchased items. Those times, it was necessary that all that business movement...
  • Blog Post: Starting with Model/View/Controller (MVC) Architecture Pattern

    With the massive advent of Internet, mobility and other network technologies, distributed programming is more popular than ever and it's unimaginable the idea that stand alone applications can come back They are gone So immediately a coupling crisis appeared in distributed applications: how...
  • Blog Post: Last Call to Design Patterns

    When planing the architecture of an application, the architect has a powerful set of tools available: Design Patterns Design Patterns are reusable solutions for frequent problems, upon different contexts. The more you know about them, the more self-confidence you gain while doing your architecture...
  • Blog Post: Wanna Be a Solution Architect but... Where to Start From?

    Being a developer or, even better, a senior developer, is a good starting point to become a solution architect. But, of course, the transition from dev state to arc one implies some changes in the ways of reasoning Surely a solution architect focuses more in modeling than in lines of code, and terms...
Page 1 of 1 (16 items)