|
|
|
|
|
|
by mr_00ff00
104 days ago
|
|
|
Thanks for advice, and yeah that makes sense that I’ll have to learn a whole new skill set, but I enjoy learning. When talking about a feature, am I doing basically high level system design? Similar to what a senior engineer does (aka this should be a cache, it’s best to change this to streaming so let’s remove the audit db, etc) or is it even more high level than that? Also lol at the last line, never heard that but I can see why people might make the assumption. |
|
|
No, you aren't doing that kind of high-level design. For example, I was the PM for the "connect to Wi-Fi via a QR code" feature in Windows (you're welcome!). As PM, my job was to :
- demonstrate that this was "thing" people would want to do - demonstrate that it slotted into the existing feature set (the existing Windows camera already reads QR codes, so we just had to use their existing hoooks) - do a quick evaluation of the WIFI: protocol (which, BTW, sucks; it's one of the worst standards I've ever seen) - do an evaluation of the overall market (like, what do other operating systems do)
There was also some discussions with the Windows Wi-Fi team for how to store the connection data since it wasn't a perfect fit for the our existing connection store, plus a security evaluation. You won't do anything about caches or streaming except that they will naturally fall out of your spec.
You'll learn a ton about writing convincing documents, how to find users and partners, tracking schedules, and stuff