2 ms·
I feel like I'm effectively writing a "no code" tool at the moment; it's a GUI whose user inputs will eventually be output as a configuration file that is fed i
by Cthulhu_ 6y ago
I feel like I'm effectively writing a "no code" tool at the moment; it's a GUI whose user inputs will eventually be output as a configuration file that is fed into our core system (mobile network signal processing, in the broadest sense of the word).
In theory, end-users and operators could work in the configuration files directly themselves (it's a combination of XML templates and files, and .ini-like config files). The GUI is there to prevent footguns and add convenience.
Anyway it's not very visual, it's a lot of forms and pop-up segments with more forms, but still, one could argue it's a no-code environment. I should look into the area.
Mind you, I'm working on a rebuild and at the current rate it'll take me years to even start thinking of doing anything more advanced than replacing the existing forms.
[personal rant[ I'm not sure if I want to spend the next years at this company either; they're doing well enough financially but it's a slow burner. They're hiring, but the wages are stagnant and dare I say below market rate. I'll have to review in 6 months or end of year.