Whether or not we trust a source of information depends to a large extent on the source of that information. If the source of information is trusted, then we trust if it isn’t then we don’t. In other words, trust is a personal thing based on who the consumer of data have decided are their ultimate sources of trust. Trust then flows out from those sources through a graph of connections to the media item currently being consumed.
Leaders of engineering organizations must design their organization in such a way that the recruiters and those involved in the hiring process have a vested interest in the success of the organizations they support. At the moment, leaders seem to ignore the recruitment and intake process, leaving it up to HR. These leaders neglect that part of the business because they don’t realize how critical it is to the success of the enterprise. That is an insane approach that directly comprises the ability of the organization to do business.
Startups in Peru are struggling due to a lack of available investment, a lack of available software engineers, and a tech/business relationship that is inimical to the success of a software-based technology startup.
Mocking is evil. At the very notion of that, all the citizens of Nounlandia, are screaming for my blood, shouting ‘Heresy! Heresy!’. I think I can hear the sound of sharpening stones on pitchfork tines even as I write this. Mocking is fundamentally evil. It encourages you to write bad, poorly factored code, not-very-functional code. It encourages you to avoid standing up as much of your system as possible during integration testing. Finally, all too often at the end of all that mocking all you end up with are some really well tested Mocks nested N! levels. In other words, mocking produces a bunch of useless code that costs money and time to maintain.
This article is an update and refinement of my ‘Team Development with Git’ of last year. It changes the model to take into account the strengths and weaknesses of Github’s PR process.