The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
I've quit long before that. I (and my colon) have nothing to prove.
And that's why it all gets turned into sauce. You learn it's properties of heat (starting will less, not excess) and work your way into cooking it in with just the right heat.
The super-hots (habanaero and beyond) of the Capsicum Chinense family have a better hot taste (at least to Mrs. Wife and myself) - all else being equal. The heat comes in a bit later and they are fruity. I just use (physcially) a lot less - also, less vinigar (my preservative) when you use so little and thus food isn't affected by the sour and smell.
But - paralleling the part of your post I quoted, any idiot can make food too hot - putting in the right amount to make it taste better is the key - and that does imply that the food has a taste.
I've never (knowingly) eaten one before. I've seen them in supermarkets and more so, in fruit markets - and was tempted by their interesting look - but never got around to indulging. Assuming the insects don't get there first, I'll have my chance.
Online descriptions seem to put it like it's family - a form of cabbage - apparently sweeter than others. The seeds were the surprise "free" inclusion so not much can go wrong
I decided that, instead of manually categorising a bunch of values in a spreadsheet I'd write a simple VBA method that would do the hard work for me. After all, doing it manually would take about an hour. Writing a bit of VBA couldn't take more than... well, I think I'm on hour 5 at this point.
It's been a long time since I've done VBScript, but even VBScript was generally fairly sensible.
No constructor, serious hassles passing user defined types between methods, a limit to the number of times you can use line continuation in a row, the awful experience overall.
I can't believe how much of the world lives and breathes this stuff.
(but of course I'm going to bash my way through it instead of just getting the job done the old fashioned way)
I semi-retired a few years ago but took up a job "in the business" looking after their EUC "solutions" - most of which consisted of recorded macros. Three years later and trying to introduce any form of governance is still like herding cats
Just today I was yearning for the days when I would just knock up a quick program to automate something - I sometimes even find myself wishing for VB6!
Good Tips '489 !
Writing add-ins seems to be the only way to automate Office 365. It is becoming the corporate office platform in a lot of places so indeed MS has done a Ripley on us corporate software developers.
If you do have to work in VBA -there are many toolsets to help write and maintain good code - MZ tools is my preference but Rubberduck · GitHub[^] looks good too.
Its an old but stable IDE -little Intellisense, no autocompletion - but that only helps the coding - not the thinking!
Export all your code modules, forms, spreadsheet content, formulae, formats to text files. Then you can do version control in mercurial, and inspection in Npp
Merging is an issue but you can see what changed and revert or branch.
As a fairly serious Access programmer, I feel your pain! The one complaint that I don't endorse, though, is about the limit on consecutive line continuations, which I must say I have never run into. On the whole, I feel that if you have to continue a logical line over more than a couple of printed lines, you should break up the logic, since it is likely to be difficult to understand if/when you come back to it later, let alone by anyone else!
Understandability isn't an issue, then, but I think you are right about what you should do. When I have the same sort of issue in Access VBA, I generally create a new Table (if the 'array' is likely to be needed again) or Recordset (if it isn't), which is pretty much the Access equivalent of entering the terms on the spreadsheet in Excel.