Readit NewsI didn't quite get if Automatic TLS (https://developers.cloudflare.com/ssl/origin-configuration/s...) could use plain transfers.
So:
* Is it insecure by default or you have to be intentionally insecure?
* Why would anyone pick the flexible/potentially-insecure option?
Would be good if the downgraders left a comment explaining.
Note: I am not a job poster and not affiliated with any hiring posts here
Technology is too fragmented - day to day many of us depend on a ton of tools to go by our (work)days even for simple stuff. Log into console of X, Y & Z platform or tools (say X = Jira, Y = AWS, Z = repo) to introduce a new change/feature/bugfix whatever. Then switch to IDE of choice to eval code, then browser to read the docs, then Google/Claude to ask questions, and then be interrupted by a meeting, take notes, ... and on and on
I see an opportunity here using something like this to unify your entire workflows/data-from-tools/tools into a uniform system you can query to get answers without having to jump through hoops (and give up). It appears investing time in building a repertoire of tools with something of this sort helps one automate or quicken chores (at work or at home even?)
What else could you do with this apart from what's in the demos? Some "can it do this?" questions if anyone who has used this could helpfully answer are:
* organise meeting notes across various topics and auto-compile a searchable "decision log" that you can drill in to dive into the context at a future date?
* connect requirements (specified in excel) to JIRA tickets and Code? so you can jump back and forth in a single GUI
* Log hours you have worked on something
* create up to date management process reference / checklist along with escalation contacts, response templates, ability to engage others on roster, and later bring together all the information into a automated PIR timeline and other details
* display system metrics of deployed services in AWS based on complex rules and provide local alert
* maintain a schedule of your kid's swimming lessons
* Notion like "verification expired" notifications
* Live tables (say of stock market tickers)
It's quite versatile. I had never considered this angle of using it to manage and sync with something external like Kubernetes here and love it.
I wish someone also solved the issue with excel around refactoring though - esp when cells are being used in formulas, if there was a "Find All References" or Cmd+SHIFT+F (global find) of elements used in formula (not their values) - it would step it up even more towards maintainability.
(I understand it buckles under huge datasets, but I believe that's really over-use of the tool)
My blub was recently challenged when I recently learned about FreeBSD.
Here's a few comparisons off the top (WW=WoodWorking, Soft=Software Dev/Engr):
* WW: must plan well. If you're working on a provided plank of wood, you can't "uncut" if you cut something shorter than should for example, Soft: iterative - and figure things out after some or none initial planning, and easily fix things later
* WW: higher risk of fatality/injury, Soft: relatively very low risk. Low liability for artifacts produced - but could serious affect users (e.g. cybersec).
* WW: expensive, non-scalable, Soft: scalable, non-expensive (unless u want expensive hardware)
* WW: visceral/earthy experience almost always - even on failed pieces, Soft: depends on what you produce
* WW: Tangible, Soft: Intangible
* WW: Can be repetitive - planing, jointing, routing, Soft: less repetitive
* WW: Creative, Soft: Creative
This might also be a new vehicle to mask any space warfare technology deployments.