Why are you all talking about the "reject option", which implicitly considers the opt-in to be the default? The default MUST be the opt-out (for non-essential cookies), hence there is no "reject" because there must be the "accept".
(author here) Very good point(s) and thank you for the input! Treenee is indeed very minimal and it's supposed to be working basically "out-of-the-box". This also means that some features are obviously missing at the moment.
I use Treenee internally (even though I wanted to keep it on m y own name, not the company's) and I decided to put it out there as soon as it was "complete". I will add more examples and use cases in the near future (also screenshots, but I am a bit ashamed of the scarce "design").
Do you mind expanding a bit on what you would like "logging" to be?
I agree that this heavily opinionated "starter kit" might be not what you want to give to a beginner (also it feels quite obsolete nowadays), but I quite disagree that create-react-app is a better choice.
I think that CRA is either useless as it is too simple and confusing (in its first run, before you "eject"... what are those react scripts, for example?) or too far away down the road of "choose what technique is best for your project" once you "eject".
I rather consider using a "true" starter kit, with no helpers and not many applied opinions to it (like, no redux for example and/or no decision on how to handle CSS). With this principle in mind, I wrote my starter kit https://github.com/claudioc/react-with-typescript-starterkit (yes, there are many of them already, but I try for it to be a middle ground between something that you want to use to bootstrap an real new app and something you study to learn the _what_ you need to start and begin by yourself).
I am a 48 full-stack developer and I (still?) get at least a couple of job interview offers a week. I am at an interesting point in my career, though, where the company I work for decided for me to try a more managerial role (not because of age or technical impairments... it's more complicated than that).
I've accepted the new role, just because I'd like to take a step back (as in "looking at the forest and not at the trees"), manage and mentor people and – why not – step out of the f*cking comfort zone. You should do that, right?
Anyway, now I am very puzzled about how to present myself in the near future: a 48 "rookie" manager (who needs to prove himself on the ground) or a seasoned, bad-ass developer with 25+ year experience on any software tier you can mention? I can sell myself very easily as the latter, while the former... I don't know.
Luckily I am not losing ground on the technical side, which means that I can easily switch back to a more technical role (architect would be awesome)... but this bound me to _this_ company, which provides me the luxury of this choice in the near future.
Interesting times ahead... you'll never get old unless you want to :)
There are so many things to say about this context, but maybe the most interesting story is the one of Potsdamer Platz. How it was before, how it was during the wall, how it was (horribly and wrongly) rebuilt...