jerdthenerd
Joined 3 years ago
Joined 3 years ago
You don't really want to give a LLM client code execution environment like Observable Framework does. dbt charts appear to validate the entire yaml input including the SQL being sent to the data source.
So I'm getting: a data vis layer that can be dynamically defined and rendered via LLM/MCP client without the headache of sandboxing a JS Runtime environment.
Since it's a semi-novel way for terminal multiplexing, would like to see some examples prior to installing/downloading.
And yes it was a felony to not register by, IIRC, December 31st of the same year the measure was passed or some other very accelerated timeline.
There was no email, letter, or notification received. The data collected included enough information for someone to effectively takeover my business record for my state if the government dataset ever got leaked.
I'm glad they are forcing the erasure of the data.
Any self hosted service in an enterprise means that you're dealing with all the headaches that come with that including: backups, user/role creation and mapping maintenance, infrastructure scaling needs, OTEL or other monitoring, etc.
It's an easier decision for VPs to pay GitHub anything less than the man hours required to execute the above tasks because it's a "not our problem" fee.
I work at a medium size publicly traded company and our SOX compliance controls would take literal months to generate and/or prove to auditors without our CI/CD pipelines. It's just an extract from GH Actions with a report of who modified, who approved, and who actually pushed to main. All of these actions must be siloed (if you can commit to repo, you cannot push to main)
Potentially this is a consequence of micro service infra, my team alone manages nearly 25 separate git repositories.
Sounds like a repetitive motion injury waiting to happen after you get done scanning Fountainhead.
"I want to allow customers to run scheduled reports from our portal and receive them via email."
Development then designs and executes, delivering a scheduled reporting suite for testing. Business will come back with feedback such as:
"I don't like how I have to select the time for every report. Can't you just default it?" or "Only some users from the customer's account should be able to create/edit scheduled reports. Please add this by Tuesday so I can demo." or even "This is great, but my customer has special holidays that they don't want emails to be sent on. We should have a yearly calendar that prevents reports from getting sent."
There is a large gap between feature request "requirements" and the expectations of the business. Thus, we request specific feature request requirement documents to be turned in prior to development starting work.
I have issues with business/product team even commenting on PRs because auditors have said that access to GitHub=Access to Codebase.
There are a select few people I would consider granting access to code within our product teams, but without "segregation of duties" clearly defined, I don't think it would fly.
So I give this game a 6/10 for bugginess. Would not recommend the preorder.
edit - after reading some of the comments, I realized I could change my destiny by resetting the captcha
Interests: DevOps, Entrepreneurship, Hacking, Hiking, Networking, Open Source, Programming, Remote Work, Startups, Sports, Technology
--- jerdthenerd.at.hn