Gooey VS missing-semester

The name conflicts with a similar python module that allows one to turn any Python console program into a GUI with one line.

https://github.com/chriskiehl/Gooey

Hey! Cool project! I have a question: why do you dump out sys.argv to a local file in the CWD? [0] tmp.txt is hardly a unique name… or am I missing something and this never triggers?

[0] https://github.com/chriskiehl/Gooey/blob/be4b11b8f27f500e732...

This might be of interest to you:

> Gooey - Turn (almost) any Python 3 Console Program into a GUI application with one line

https://github.com/chriskiehl/Gooey

I love gooey: https://github.com/chriskiehl/Gooey

It allows me to quickly slap a GUI on an existing script that accepts command-line-arguments. In the end, I get the best of both world: Discoverability from the GUI, automation through the script, and automatic feature parity between the two.

Downside: Control over the GUI layout is basic, and only "standard" GUI features work, but I never felt limited when using it.

similar for local/individual usage:

https://github.com/chriskiehl/Gooey - take a python-CLI, make a TK-windows

and then probably even simple dashboarding like streamlit.

Like Gooey?

As for how I'd handle it, I would probably combine both into one command-line program, with all filepaths using pathlib and letting argparse handle the options. That way you could optionally generate a GUI with gooey with little extra effort, although this would also add a dependency.

The missing semester of your cs education

https://missing.csail.mit.edu/

You mentioned having issues with accessory concepts so perhaps this might help: https://missing.csail.mit.edu/. There's also a chapter on git

https://missing.csail.mit.edu/ is a good way to pass the Dec-Jan break if you want to prep for CS2030S + some more general stuff.

Reflecting a little bit more I don't think it was replit's fault, per-say. But that change should have been made together with a larger adjustment to the program. Like adding a class/unit in the style of [the missing semester](https://missing.csail.mit.edu/) to make sure people came away with a good range of intuitions.

From MJD's post: I think CS curricula should have a class that focuses specifically on these issues, on the matter of how do you actually write software?

But they never do.

FWIW, MIT's "The Missing Semester of Your CS Education" attempts to deal with this lack, though, even there, it's an unofficial course taught between terms, during MIT's IAP -- Independent Activities Period[1] -- and not an actual CS course.

[0] https://missing.csail.mit.edu/

[1] https://en.wikipedia.org/wiki/Traditions_and_student_activit...

Link to the "missing semester of your CS degree" course by MIT.

Rightly called The Missing Semester (of Your CS Education), this class from MIT will teach you how to use some of the tools that are fundamental to the software engineering ecosystem. From shell scripting to the fundamentals of information security—spanning around 12 lectures—you can add a bunch of practical skills to your toolbox.