I am working on adding functionality in my app and it appears that we are unable to add a name to a bookmark. This is not sustainable if you’re working on more than a few upgrades at the same time. It might also be efficient to be able to type a name into a text box and land right at the targeted bookmark.
Anyways. Please consider upvoting on Issues. I don’t know how hard it would be to add on a name to each bookmark…
While developing in Xojo, I put some comments starting with //! or //? in places that need some kind of attention and those comments are temporary
break //! fix this bug before release
And remove them when I’m done
Sometimes I make them emphatic as break //!!!!!!!!! fix this bug before release
My bookmarks have temporary comments too.
When I complete some large work, before release, I search the code looking for //? and //! to make sure I did not forget some pendency.
Sometimes I put just some lazy //??????? near to some obvious pendency, or something critical going on, or the last place I were with something incomplete (probably I’ll add some comment as //???????? finish the whatever if I intend to make a large pause)
That’s just my personal style. You won’t see such thing being “taught” at the university.
Off topic, (apologies), but when I was at Uni, I was genuinely advised by one lecturer to hard-code values like VAT rates into software , with the explanation “This means they will have to pay you to change the software every time the government changes the rate of VAT”
Usually tech people don’t talk much about “business”, just tech problems, not to mention things near to ethical subjects.
Maybe something from another era when people were looking for ways to solve the monetization problem of their work (hello shareware), but today we solve with things like a support contract that if broken could lead to problems to them, it could be just a parameter you could send in an email to your paying clients, for example, but encoded in a way that only your app know how to handle and apply, and a warning about problems to those suspended (like "You need to update your VAT, please reinstate you support plan if you need help) BUT all your clients known that since the contract. There are several ways, but needing to change an entire program because you hardcoded a parameter currently is not considered a good design.
When we had lots of people with backgrounds based on COBOL / FORTRAN ( and ALGOL if a researcher ) I would bet no more than 1986, and that’s 40 years ago.
In the range 1986-1996 (30+) We would see Pascal (Turbo Pascal started to invade microcomputers in 1983 and Delphi took its place in 1995), lots o BASIC (any homecomputer had one interpreter), some resilient COBOL/FORTRAN.
