captaincaveman

Looks like a useful and fun side project, just wish I had time to play with it!

> the only real hope of change is that a higher power takes more control

Odin?

Useful for refreshing concepts I'd learnt/coded at Uni, 20 years ago and not used since ... which isn't as snarky as it sounds.

Basically with a bit of drilling, a competent programmer should be able to get the hang of those questions, and maybe the fact you can get competent at doing tricky, niche things is a useful indicator.

I wouldn't say doing leetcode would in anyway make you better at writing clean, well structured code, which is what we typically interview for in non FAANG. Probably does help sharpen your cracking out gnarly inner loop type coding skills i.e. better at writing a difficult function, doesn't do anything for how you would write the rest of the program.

You could arguably better correlate that with teenagers gaining access to personal image sharing devices .. i.e. camera phones, and publishing platforms i.e. they can share photos/videos ... systemically the issue is self worth being largely wrapped up in how pretty you are perceived to be, which is a social/cultural problem.

Nicely done sir!

Spot on, its often middle management not really understanding engineering, and think they can do better by just have someone else do it for them, but total lack of foresight on the consequences, which to be fair they probably won't have to deal with before they switch jobs.

Very much this, a few places out sourced their IT on the cheap to ACN during financial crisis, the problem then is clawing it back years later, when actually it now costs lots to support a terrible mess and is a drag on the company.

If FLoC is opt out by default as many here claim, is this news saying that Github did nothing?

Also if it is opt-out by default I guess it will be simple to see who has opted-in, a nice list of shame.

Does this circumvent the EU cookie laws?

So only if the publisher opts-in (sort of), and what about the user, if this is all done client side surely I should be opt out by default too?

I assume I can set my browser to opt out easily?

Hmm what about Murdoch in News TV?

As a tip, don't try an learn every minute detail, think 20% gets you 80% of the way, the rest is probably not worth it for you, and if it is useful to clarify your own thinking that's good, but probably lost on anyone you want to communicate it with.

I find this kind of comment ironic (your not the only one to make it), its this kind of thinking which lead to UML becoming a complex over detailed beast, rather than be a tool to consistently model intentions.

If you model at the correct level of detail, you don't have pain keeping them in sync, one you start to model the implementation details you need to adding more complexity to your model to be able to sync the model :)

When useful:

Component diagrams, what is connected to what?

Activity diagrams, what are the activities that happen, and have they got names?

Sequence diagrams, so microservices on top of microservices, hmm please show me how you get item x?

State Diagram, are you sure you have got all the possible state transitions?

ERD diagram, Chen style, I don't like it when the look like SQL tables (maybe we don't have/want/need a relational database, so lets not start shaping it like one at the concept stage). The physical/logical models I don't see much value diagramming.

BPMN can be useful alternative to Activity diagrams sometimes.

edit: left off Use Case diagram, so simple yet seen teams struggle so many times to articulate this.

A key thing about doing a diagram or document is that they force you to clarify your understanding. Another rule of thumb is if you are struggling to keep you docs/diagram in sync with your implementation, you have likely made you docs too detailed, its a high level map to guide not a detailed set of instructions on how to construct.

It has mostly died with the current generation of engineers, due to a common problem.

We tend to go to either extreme, UML all the things (model driven design), massively over specify things before you write code. Then react by saying, this thing doesn't work when you try to do non sensible tings with it, its terrible, anyone who uses it doesn't get it.

The next gen of devs come along and thing its just for old folk who aren't down with the times.

Meanwhile, some people who never never fell into the trap of the extremes carry on to use it when useful and in a sensible way. Perhaps even try to show some newer devs the benefits, but have to now get past these preconceptions, even though the newer guys haven't any experience. These people are now often leading large engineering groups, and often want a basic overview of designs (not to the minuet detail), and really don't care about your classes, but please give me a sequence diagram so I can see how this microservice it actually going to fit in, and show me you have thought through the state transitions of the data.