User:Jeffrey Fisher/2023 Feedback Session Brainstorming: Difference between revisions
(Created page with "stub") |
No edit summary |
||
| Line 1: | Line 1: | ||
== Cleaner questions == |
|||
stub |
|||
== Stream of conciousness == |
|||
* Likely will switch to Python, that sound good? |
|||
** '''Goal:''' Free up time to focus on more core software engineering stuff, by not having to spend as much time on teaching you just how to use C++. |
|||
*** e.g. would probably add stuff about automated testing, API design |
|||
*** Would still have stuff like Linux, command line, but w/ Python we can focus more time on those rather than time on how to use C++, how to use CMake. |
|||
** Want to eventually have decent support for people who have never done any coding before. Stuff like header files, annoying compilation, config files (for CMake) are really big barriers that Python doesn't have (at least at the basic level). |
|||
** For people who got to vision, they mostly ended up doing it in Python anyways. For something like AprilTag it's a C library but if there's a Python wrapper it's probably more convenient to use anyways. |
|||
** Python has less legacy/wtf stuff. No header files. Don't really have to discuss compilation (important but compilation in C/C++ is especially hard). |
|||
* What did people think of the intentional gaps? |
|||
** e.g. for PWM we just tell you the three library functions that you need, their signatures, and link to the documentation. |
|||
*** Small: Probably need to explain what the Pigpio Handle is, since it says "int", though that may go away when using Python. |
|||
* VS Code / IDE features |
|||
** Saw a lot of people trying to use the run button in VS Code. Fair enough, we recommended VS Code. Maybe should figure out the configuration for getting that to work. Probably low priority though. I don't use VS Code so it might not be easy for me to figure out, and there are many places where a terminal will be necessary, so we have to teach that anyways. |
|||
** Stuff like LSP, completion, etc. setup would be very valuable. Again, I don't use VS Code, and I don't even use LSP-like stuff that often (I probably should check it out), so it's not something I can figure out quickly. |
|||
* Good level of support/help? |
|||
** For software I was the only person there to help with onboarding. Did that work out okay? At least from my end it didn't seem too bad. Later on people seemed to be okay working mostly independently, and I had time to help people in more depth. |
|||
Revision as of 22:02, 21 December 2023
Cleaner questions
Stream of conciousness
- Likely will switch to Python, that sound good?
- Goal: Free up time to focus on more core software engineering stuff, by not having to spend as much time on teaching you just how to use C++.
- e.g. would probably add stuff about automated testing, API design
- Would still have stuff like Linux, command line, but w/ Python we can focus more time on those rather than time on how to use C++, how to use CMake.
- Want to eventually have decent support for people who have never done any coding before. Stuff like header files, annoying compilation, config files (for CMake) are really big barriers that Python doesn't have (at least at the basic level).
- For people who got to vision, they mostly ended up doing it in Python anyways. For something like AprilTag it's a C library but if there's a Python wrapper it's probably more convenient to use anyways.
- Python has less legacy/wtf stuff. No header files. Don't really have to discuss compilation (important but compilation in C/C++ is especially hard).
- Goal: Free up time to focus on more core software engineering stuff, by not having to spend as much time on teaching you just how to use C++.
- What did people think of the intentional gaps?
- e.g. for PWM we just tell you the three library functions that you need, their signatures, and link to the documentation.
- Small: Probably need to explain what the Pigpio Handle is, since it says "int", though that may go away when using Python.
- e.g. for PWM we just tell you the three library functions that you need, their signatures, and link to the documentation.
- VS Code / IDE features
- Saw a lot of people trying to use the run button in VS Code. Fair enough, we recommended VS Code. Maybe should figure out the configuration for getting that to work. Probably low priority though. I don't use VS Code so it might not be easy for me to figure out, and there are many places where a terminal will be necessary, so we have to teach that anyways.
- Stuff like LSP, completion, etc. setup would be very valuable. Again, I don't use VS Code, and I don't even use LSP-like stuff that often (I probably should check it out), so it's not something I can figure out quickly.
- Good level of support/help?
- For software I was the only person there to help with onboarding. Did that work out okay? At least from my end it didn't seem too bad. Later on people seemed to be okay working mostly independently, and I had time to help people in more depth.