Difference between revisions of "2026"
Jump to navigation
Jump to search
m (Update SPI NOR FLASH work) |
m (Add note on Zephyr latest 4.3.x sensor documentation) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 24: | Line 24: | ||
[ ] Resurrect Kionix Zephyr driver project. | [ ] Resurrect Kionix Zephyr driver project. | ||
| + | [ ] add MIT license file | ||
| + | [ ] archive the initial work on readings conversions from count to m/s^2 | ||
| + | [ ] clean up the code including run through clang-format | ||
| + | [ ] make note of API extensions which may be added in a separate source and header file pair | ||
| + | Read thoroughly: | ||
| + | [ ] https://docs.zephyrproject.org/latest/hardware/peripherals/sensor/index.html | ||
[ ] Add getopts and better factoring to directory bookmarker shell script. | [ ] Add getopts and better factoring to directory bookmarker shell script. | ||
| + | --> | ||
| + | |||
| + | <!-- | ||
| + | Hello Adam, | ||
| + | |||
| + | For the meeting I've scheduled with you about my 2025 performance review I have a couple of questions I would like discuss. I'll share these with you here so that we may make better use of our meeting time. | ||
| + | |||
| + | In my performance reviews over the years I'm used to receiving both positive feedback and constructive criticism. While it's nice to receive recognition and hear good things I realize that the latter of these is the more important to hear and listen to. Given my work over the past year however, I was struck by how short the positive comments were in my review. You kindly remembered my staying late two or three years ago to prepare for an important demonstration. You acknowledged my more recent work on the support for Eseye and cell modem firmware updates, on-going since around last October. But there was no mention of any of things I worked on in between, even this past year. | ||
| + | |||
| + | Some key project contributions I completed include the SPI NOR driver patch, to fix a critical path fault which arose when we switch to a 32MB external flash from a 16MB one. That broke over-the-air updates entirely, and was a show stopper until resolved. Later in the year and shortly before Iomico, I was able to root cause the "hang bug" problem and develop a solution, in about three days. That issue again represented unship-able firmware. Iomico may have solved that quickly themselves, but we did not need to throw it over the wall to them. | ||
| + | |||
| + | Shortly following this work at Josh's request I took on the larger Nexus project reorg task. While this did not involve creating a lot of new code, I needed to review some three hundred project source files (some in groups, but many one by one, and some line by line) and work in three of the four or five languages which comprise our firmware and its build system. All this in preparation for starting out a with a reasonably clean slate with Iomico. | ||
| + | |||
| + | To complete these kinds of tasks requires a deeper understanding of things like debugging tools, third party driver design, and of our project itself. I am curious why none of these specific work achievements came up in my annual review? It would be a quick act to remember and acknowledge them. | ||
| + | |||
| + | The second point which caught my ear but took a while to process goes to your feedback to carry out what is asked in the pull requests, "to do what Josh says" as you said. I value and agree with this. It is also the case that I am already doing as Josh asks me to do. I respect Josh and his role as the team lead. I believe Josh is doing a good job in a high pressure position. Josh and I have discussed technical points where we have concerns and sometimes disagreement, but we have always discussed things respectfully. There is no occasion where I refused Josh or any other team member, to do what they ultimately asked and required of me. | ||
| + | |||
| + | During my time here at Cornell, I've been accustomed to talk about the pros and cons of important technical matters with all my teammates. I don't always agree with them, but I am accustomed to collaborate in the process of choosing the best solution. I discussed technical firmware choices with Jared while he was with us, and with Aaron. I did so later with Melvin while we worked with Dojofive. Last summer Josh and I were the only ones to work on firmware, and so matters naturally fell to the two of us to collaborate on those points. | ||
| + | |||
| + | I understand Josh to be in charge of delegating firmware tasks to us all. If there's a further change, one where Josh is tasked to make the technical decisions more quickly and with less input from me and others, I'm happy to change my working style. I can raise concerns less often, as seldom as necessary. I just need to know what's expected for our team interactions and day to day team dynamics. | ||
| + | |||
| + | This goes to my question, do I need to speak up less when I have a technical concern or disagreement? | ||
| + | |||
| + | It is not in my personality to refuse a task or to be uncommunicative. On the contrary, I respect my colleagues. I know they're working hard. I do my utmost to honor their dignity. If there's a time I see someone may need help, I reach out to them one on one to ask, so that it is not the case that it would appear I was trying to one up someone. I have always wanted to raise the team up, to learn and to share what I know as we work together. And I think most important, I give my teammates grace. I don't ever speak badly about my teammates, not in front of them and not outside their knowledge. | ||
| + | |||
| + | I would have been less surprised at the tenor of my review if I'd heard some of these concerns more in our one-on-one meetings in the months prior. This past year especially, but early as well I have felt pulled in some competing directions. For a long time now there is an ever present message that we're behind schedule and over-budget. I have been trying in earnest to strike a balance between working quickly to produce a good product and getting bogged down being too focused on perfection. I want us to reach a good and successful outcome on time. | ||
| + | |||
| + | My standing at work is important to me and to my family, and so it is important to me to share this feedback. | ||
| + | |||
| + | Sincerely, | ||
| + | |||
| + | - Ted | ||
--> | --> | ||
Latest revision as of 16:53, 22 January 2026
New Year