Is there anything of value in the internal codebase?
So many companies internal codebases are of approximately zero value to any outsider. The code is only a small proportion of the business.
Grafana Labs internal source code accessed
11–20 of 28 posts
Re: Grafana Labs internal source code accessed
#12Re: Grafana Labs internal source code accessed
#13I was recently considering an engineering job offer at Grafana. At the end I was turned off by the amount of their AI-related mindless propaganda and demands they have put right in the job offer. (Which is by the way quite rare; it is rather untypical to state in the position description how a developer should use AI tools; even though everyone can imagine how it looks like).
Looks like they could have invested more energy in the processes and security rather than catching up "innovation" craze that much
Re: Grafana Labs internal source code accessed
#14Is there anything of value in the internal codebase? So many companies internal codebases are of approximately zero value to any outsider. The code is only a small proportion of the business.
Maybe some EE stuff like SSO and etc? Unfortunately layering that stuff on is super low effort in these LLM days.
Re: Grafana Labs internal source code accessed
#15Is there anything of value in the internal codebase? So many companies internal codebases are of approximately zero value to any outsider. The code is only a small proportion of the business.
Maybe some EE stuff like SSO and etc? Unfortunately layering that stuff on is super low effort in these LLM days.
Grafana OSS does support SSO out of the box, at least OIDC (which is a technically superior standard to SAML w.r.t. security).
The Enterprise edition seems to focus a lot on meta-information about grafana itself: the most frequently accessed dashboard, who is viewing the current dashboard etc.
Theres also group-sync, I guess, which is useful, but honestly the selling point of enterprise is the support I think.
In fact, I might buy enterprise following this, the fact that so much is in the base product gives me the warm fuzzies.
Re: Grafana Labs internal source code accessed
#16"Threat actor"… I love this "security" lingo. Threat actors, attack vectors, state actors :-)
Re: Grafana Labs internal source code accessed
#17"Threat actor"… I love this "security" lingo. Threat actors, attack vectors, state actors :-)
Let's hope they don't go kinetic.
Re: Grafana Labs internal source code accessed
#18I was recently considering an engineering job offer at Grafana. At the end I was turned off by the amount of their AI-related mindless propaganda and demands they have put right in the job offer. (Which is by the way quite rare; it is rather untypical to state in the position description how a developer should use AI tools; even though everyone can imagine how it looks like). Looks like they could have invested more…
The companies are now so often looking for "AI engineers" or "engineers with AI experience" which is crazy given how current generation of AI tools are in very early stages and spending a lot of time mastering them might be time well wasted if many of them actually believe in any further advances, much less AGI. If what AI overlords promise is to materialize, then all these primitive tools like agents, MCPs, plugins (or "marketplaces" which is crazy that LLMs couldn't help them come up with a better name) and whatnot should be just an insignificant blip in the history of AI evolution.
Re: Grafana Labs internal source code accessed
#19I was recently considering an engineering job offer at Grafana. At the end I was turned off by the amount of their AI-related mindless propaganda and demands they have put right in the job offer. (Which is by the way quite rare; it is rather untypical to state in the position description how a developer should use AI tools; even though everyone can imagine how it looks like). Looks like they could have invested more…
The companies are now so often looking for "AI engineers" or "engineers with AI experience" which is crazy given how current generation of AI tools are in very early stages and spending a lot of time mastering them might be time well wasted if many of them actually believe in any further advances, much less AGI. If what AI overlords promise is to materialize, then all these primitive tools like agents, MCPs, plugins…
Companies that care about the 3-15 months of agentic engineering experience you could possibly have (15 months if you count by the launch of Claude Code, 3 months if you count by when that term was coined) don't think about AGI. They think about immediate productivity gains and not working against company culture from the very beginning of their employment.
I remember one job interview where the team lead interviewing me and I had completely different takes on static vs. dynamic typing. It was an awkward moment when we realized we'd never agree, and attempting to cooperate would be very burdensome. Don't hire someone who thinks what you're doing is stupid. AI really divides the waters, better be up front.
Re: Grafana Labs internal source code accessed
#20I was recently considering an engineering job offer at Grafana. At the end I was turned off by the amount of their AI-related mindless propaganda and demands they have put right in the job offer. (Which is by the way quite rare; it is rather untypical to state in the position description how a developer should use AI tools; even though everyone can imagine how it looks like). Looks like they could have invested more…
Jobs are trully ridiculous in today's market. Not only you have to be "AI-native" with more years of experience with GenAI code, than the time it started getting popular, but you also get jobs that require you to know Claude Code in'n out, as if no other agent coding exists.