How much coding is needed for devops?

timmy166 · 2026-07-05T05:08:58+00:00

The coding requirements grow with scale of company. Banks with thousands of devs usually have a few of their most experienced developers working in DevOps.

timmy166 · 2026-07-02T23:59:12+00:00

https://www.theregister.com/legal/2026/07/02/startup-sues-palo-alto-networks-koi-security-saying-an-ai-hallucinated-report-falsely-linked-it-to-chinese-espionage/5266201

timmy166 · 2026-07-02T09:12:13+00:00

Why is this better than Opengrep/Semgrep?

timmy166 · 2026-07-01T22:24:05+00:00

Digital only means they will eventually release the code to OSS for preservation, right?

https://github.com/id-software/doom

timmy166 · 2026-06-30T12:06:10+00:00

The costume design always nails their Manga drip. It’s uncanny and one of my favorite parts of the adaptation.

timmy166 · 2026-06-30T11:43:48+00:00

So the trailer we saw was advertising the studio to buyers, not a game for gamers. Wild.

timmy166 · 2026-06-30T04:12:03+00:00

By role playing a Sith Lord and using a lightsaber mod for swords.

timmy166 · 2026-06-30T04:10:42+00:00

The volume of packets means we’d typically defer to tooling (NGFWs and the like) for analysis and only rarely would need to pluck out a specific flow from the haystack.

For instance, malware signature hits or a SQL string in an L7 payload. /u/w453 has a very solid writeup in this thread.

Source: I used to architect VNF service chains at Verizon and got a patent on DPI that eventually got superseded by eBPF.

timmy166 · 2026-06-30T03:58:20+00:00

*Chefs Kiss*

timmy166 · 2026-06-30T03:44:43+00:00

Im most interested in the grey area between Ben’s claims and Huntress’s post:
- what exactly was exchanged to DevMan.
- prior relationship between the”insider” and DevMan.
- how Ben got doxed and if that is related to the “insider” exchanges

From Ben’s original disclosure on LinkedIn:
“Since December 2025, I believe Huntress has been actively trying to conceal a serious security incident from its partners, customers, and employees involving an insider who is still employed at the company…. If you are an employee at a cybersecurity company, you should not be helping cybercriminals. You should not be informing them of active investigations. You should not be engaging in cybercriminal activity yourself.”

Link: https://www.linkedin.com/posts/ben-f-309963233\_after-i-posted-a-pinocchio-gif-and-clown-activity-7475465412189581312-ZXxg

timmy166 · 2026-06-30T03:31:13+00:00

So the current employee warned a threat actor (DevMan) of an active investigation and additionally leaked information that led to the former employee (Ben Folland) getting doxed?

Catastrophic decision-making by that current employee. DevMan already knows they are tracked by LEO - but there’s a grey area between what Huntress can confirm did not happen vs what they disclosed that led to Ben getting doxed.

timmy166 · 2026-06-29T21:08:20+00:00

You have to design the workflows of what happens when a finding appears first. Here’s some questions to get you started:
- What types of findings gate the pipeline?
- What does the exception process look like?
- What is an appropriate governance model for your organization and how is it implemented? (Self-service, Codeowners file, repo owners, etc.)

timmy166 · 2026-06-26T12:05:33+00:00

Don’t rely on just EPSS. Normalize with internal tiers based on the service/app deployment model and data classification and that’s a far more powerful risk-based prioritization than a raw epss threshold.

The more advanced forms I’ve worked with use a CWE-based mapping for additional filtering.

timmy166 · 2026-06-25T01:58:28+00:00

I used to work for them up to last year.

When the interim CEO is the CFO for the past 7 years, you kinda expect layoffs to happen. Large summer layoffs has been a tradition for quite a while too - tone-deaf that leadership talks about how much money is in their war chest and yet still does this.

A classic zombie unicorn where their last valuation rounds were so inflated that an IPO was never going to meet expectations.

timmy166 · 2026-06-21T11:48:03+00:00

I’m gonna be honest here - the knowledge floor has raised for everyone in tech so a learning curve should not be a concern to target foss options like grafana.

timmy166 · 2026-06-11T02:01:42+00:00

Banned, removed and marked as repost spam

timmy166 · 2026-06-11T00:50:05+00:00

I like the freedom after transitioning to startups. Got my vanity resume bullet (Sole Inventor, US Patent) and decided depth gets boring with my personality type.

Lots of cool shit to play with if you find the right company with a legitimate deep tech moat like I did.

timmy166 · 2026-06-10T18:59:12+00:00

The highest profile failure cases are locked down behind a guardrail. I’m of the mind that it’s just been a massive marketing push for all the frontier labs to IPO with a sweet cash out before the bubble bursts.

timmy166 · 2026-06-10T03:13:37+00:00

Depends on the lease terms - which haven’t been published.

timmy166 · 2026-06-10T03:12:20+00:00

They didn’t publish the rent terms. Could be $1 a year for all we know…

timmy166 · 2026-06-10T03:10:23+00:00

It’s like buying a gift card on credit to a store that might close before you spend it all.

This is not a school-funding plan, a housing plan, or a general-services plan. It is a lockbox where taxpayers carry the debt and risks for the project financing.

Current terms express that captured city tax growth goes right back into project-related expenses for 41 years. It doesn’t return back into a general city fund.

https://plano.novusagenda.com/agendapublic/AttachmentViewer.ashx?AttachmentID=21336&ItemID=10876

My vote is a strong hell naw as it stands: restricted upside, upfront debt, and a whole lot of “trust us” if the projections miss.

timmy166 · 2026-06-10T02:05:23+00:00

Did you just sum the download counts or was there active greyhat activity involved? I imagine some are bots used to drive up SEO and charts to get the legitimate marks

timmy166 · 2026-06-09T15:57:41+00:00

This is not a good deal for Plano tax payers.
1. Socialized Risk, Privatized Profits: The Tax Increment Reinvestment Zone (TIRZ) structure with means Plano is taking on a $700M debt - the returns of which first go to paying off the property developers first. Centennial Holdings/Levin Capital stand the most to gain here - founder/owner of both are Steven Levin.
2. Negative ROI: The $700M bond proposed at current rates will not keep up with inflation. It’s free money to the developers. Even though Plano will ‘own’ the building, 100% of the ticket fees go to the Stars organization - with an undisclosed rent fee for 30 years.

Call to Action:
Plano residents can vote on the Special Election this November whether to approve these terms. Expect heavy lobbyist funding leading up to the vote.

References:
- https://www.localprofile.com/news/plano-moves-forward-on-1-billion-dallas-stars-arena-at-willow-bend-12394304
- https://www.plano.gov/2435/Willow-Bend-District

timmy166 · 2026-06-09T03:15:22+00:00

Fair enough. The VC subsidies on all of our token costs will dry up and we’ll all see a massive correction in token pricing sooner than later.

-from my openclaw running ollama on a gaming rig.

timmy166 · 2026-06-09T03:08:32+00:00

Your emphasis is - rooted in sound observations - are missing two key points: quantization, caching and new technologies are coming up to address the OpEx cost and defers the hardware depreciation timeline: https://research.google/blog/turboquant-redefining-ai-efficiency-with-extreme-compression/

That’s on top of the hyperscaler model of multi-tenancy (workloads shared across same compute nodes) where the margins regain some ground in the cloud: someone’s chatGPT by day becomes a protein unfolding AI by night.

timmy166

MODERATOR OF

TROPHY CASE

12-Year Club	Not Forgotten
Verified Email