Other problems you fix by making it hard to happen and putting provisions in place that mitigate the problems if they do. Some problems you fix by making it so they can't happen. Your office IT personnel? Yep, they can cause you problems too. Got a shared VM infrastuture, whether in house or in the cloud? The people that administer that can cause you problems. You can't really engineer yourself out of that problem without making every team and service a silo that going from top to bottom. Turn right around and go back to making sure a team can work on this.įinally, realize that sometimes the thing only one team can break is an underlying dependency for many other things, and they may inadvertently affect those. That effectively means only a single person can fix or work on the system too, and congratulations, you've engineered yourself into a bus-factor of one. If only a single person can break the system, you've gone to far. If only the people on a specific team responsible for a system can affect the system, now you've reached fairly good point, where there's separation of concerns and you're mitigating the potential problems. If any employee that's an engineer, sysadmin or developer can break it, well now you're at least reducing the problem to a more specific set of people. Ever worked for a company with less than ten people? There's probably something any employee can break). If any employee can break it, it's probably broken (there are very small scales where even this doesn't apply. If any random person can break it, it's already broken. Again, why not just call the SME first if they knew who it was and the SME didn't create documentation because they are "too busy".Įh, that's a nice thing to say, but it only makes sense at certain scales, and no matter what, there's always a person that can break it. Well, I didn't know who the SME was and there's no documentation or list of what who is the SME for which part of the system, nor was I instructed to immediately call the SME. So, I asked how I should have handled it without any training or documentation. Why even call me if you're just going to call the SME without giving me time to look at it? I got negative feedback from my manager about the way I handled it. So I'm looking for the issue/fix for 5 minutes and they tell me they know who the SME is for the functionality, so they will call them. Before I could even get halfway through, the person called again (why not leave the voicemail on the final attempt?). I did see a voicemail, so I started listening and logging on. I got a call at 1 am, missed it, and waited one minute to see if there was a message. I was not given any procedures or trouble shooting documents. The student will work on an interdisciplinary team.I was on call as a new developer on a system. The ability to produce explanation code and documentation (Javadocs / Godocs).Working knowledge of python virtual environments, docker containers, maven, go remote, and pip packaging systems.Basic understanding of Agile software engineering principles, including sprint planning and unit testing.Understanding of microservice based architecture.A good grasp of version control systems such as “git”.Experience working JSON, RDS (Relational Database Services), NoSQL (MongoDB / DocumentDB).Language Skills – Python, Go / Java, Javascript.Assist with deploying backend AWS architecture and maintaining it.Apply data analysis and visualization techniques to various sensor related projects.Work on large scale sensor data projects, manage data and build heterogeneous data storage and ingestion pipelines.Assist in software development of microservices and custom sensor endpoints.Undergraduate student at the University of Arizona To this extend we have recently started work on a new sensor data warehousing and querying platform known as SensorFabric. Given the large amount of heterogeneous sensor data collected per project, there is an ever pressing need to create a common data store platform to store this data and make it easy to query, share and search. The Sensorlab & SensorFabric – Software Development Intern will work under the supervision of the Sensor Lab Coordinator – Gustavo Almeida, and the Director for Sensor Analytics & Smart Devices Platforms – Shravan Aras, along with University of Arizona Health Sciences (UAHS) personnel, strategic plan leaders Associate Professor Winslow Burleson and Professor Jennifer Barton in support of the development of the SensorFabric by the Sensor Analytics & Smart Devices Platforms with the collaboration of the Sensor Lab. Sensor Lab & Sensor Fabric – Software Development Intern
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |