This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
I’ve been having discussions with several people recently about the role of the CTO (Chief Technology Officer) in very early stage companies. In December 2007, I described how I commonly take on an Acting CTO Role in a Start-up. I used an image from Roger Smith that describes the varying roles of a CTO as the company matures.
Before the ground offensive started, Russia allegedly took steps to invade Ukraine’s digital infrastructure, with potentially catastrophic and chaotic impacts on critical systems and operations. Putin’s advisors were likely expecting this response. Tightening access to all business systems is a good place to start.
There are a ton of examples of how much software is around us: cooling systems, our cellphones, automatic doors, microphones, cars, traffic lights, etc. Fragility: the software breaks in many places due to a single change. TDD (Test Driven Development) is a way of developing software. Red/Green/Refactor is the TDD mantra.
The next step is their integration with your in-house staff and into the workflow, which includes: Giving access to systems and instruments Setting communication channels Explaining the project scope, goals, and company structure Supporting the newcomers during the first few weeks. Ensuring your systems and IT infrastructure are protected.
The next step is their integration with your in-house staff and into the workflow, which includes: Giving access to systems and instruments Setting communication channels Explaining the project scope, goals, and company structure Supporting the newcomers during the first few weeks. Ensuring your systems and IT infrastructure are protected.
We organize all of the trending information in your field so you don't have to. Join 49,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content