I don't want to defend LLM written code, but this is true regardless if code is written by a person or a machine. There are engineers that will put the time to learn and optimize their code for performance and focus on security and there are others that won't. That has nothing to do with AI writing code. There is a reason why most software is so buggy and all software has identified security vulnerabilities, regardless of who wrote it.

I remember how website security was before frameworks like Django and ROR added default security features. I think we will see something similar with coding agents, that just will run skills/checks/mcps/... that focus have performance, security, resource management, ... built in.

I have done this myself. For all apps I build I have linters, static code analyzers, etc running at the end of each session. It's cheapest default in a very strict mode. Cleans up most of the obvious stuff almost for free.

> For all apps I build I have linters, static code analyzers, etc running at the end of each session.

I think this is critically underrated. At least in the typescript world, linters are seen as kind of a joke (oh you used tabs instead of spaces) but it can definitely prevent bugs if you spend some time even vibe coding some basic code smell rules (exhaustive deps in React hooks is one such thing).

I am in SD and would love an invite. I am keep thinking about uniting more like minded people for a while. My email is r@seslu.com

Hear hear

Pex | REMOTE (Europe), FULL-TIME | https://pex.com/careers/

Pex is a digital rights technology company, enabling the fair and transparent use of copyrighted content at the speed and scale of the Internet. We serve everyone who uses the Internet to view, share or create content – from the largest platforms and rightsholders, to independent creators. Our advanced licensing infrastructure allows platforms to manage and license content before it’s published, empowering creators to upload freely while respecting copyright. In return, rightsholders are able to monitor and capitalize on the content they own.

We are hiring for Senior Reverse Engineer/Senior Data Harvesting Engineer (Europe) to help us bring our services to the masses! Reach out to jobs@pex.com.

We offer:

  - salary: $103,000 – $110,000 USD per annum
  - equity, with a 10-year exercise window
  - 30 days of paid time off + 9 local holidays + the day off on your birthday
  - generous paid parental leave
  - a fully remote work environment, supportive culture, and excellent work-life balance

To learn more about our hiring and culture, take a look in our blog posts titled:

  - Interviewing at Pex? Here's what you can expect during our hiring process [1]
  - Pex culture: Focusing on what really matters [2]

  [1] https://pex.com/blog/interviewing-at-pex-heres-what-you-can-expect-hiring-process/
  [2] https://pex.com/blog/pex-culture-focusing-on-what-really-matters/

There are 27 countries in EU with different motives, morals, interests, etc. Just because you agree with the decision of one country in one instance it doesn't mean you would agree with them all. But once you give them the powers it's impossible to take them back. It's a bad slippery slope.

Just to be clear here, your issue is with the number of member states in the EU?

In other words you would be fine with Canada arresting employees of Clearview if they tried to enter the country after Canada deemed them profiting members of an organization that was breaking the law in Canada?

The courts are altering their views on scrapping. This [0] is a good paper that explored the last 20 years of rulings (although it hasn't been updated with the most recent cases).

[0] https://papers.ssrn.com/sol3/papers.cfm?abstract_id=3221625

Quick note for the osohq team: The "Read the docs" button leads to 404

Doh, fixing now. Thank you!

Modus [himodus.com] | REMOTE (US Only) | Full-time | Staff/principal positions only | $300k + 5% stock

Modus is a continuous workforce management platform that makes headcount planning and reconciliation easy. The platform analyzes thousands of bits of data across the organization to help leaders optimize their workforce and increase forecast accuracy. With the help of AI, Modus synthesizes insights from HRIS, ATS, expense and finance systems so leaders can visualize and execute workforce plans, grow efficiently and compliantly, and unlock high performing teams in one unified workflow.

While we are just at the beginning, both founders have extensive experience in the industry. One of the co-founders was early Google engineer and built multiple companies in the past, writing significant amount of code at each company. The other cofounder has scaled from 100 to 2500+, through to IPO and beyond. Joining as our first engineer and designer means you have will have an outsized influence on the tech and design choices.

We are currently only looking for very senior colleagues to help us move much faster:

   - Staff level frontend engineer - At least 5 years of staff level frontend development experience with Svelte, React, Next.js, Vue (strong preference for Svelte)
   - Principal Product Designer - Preferably designer with strong rapid prototyping skills, 10+ years of experience with designing B2B software, especially complex dashboards with a lots of data (strong preference for either Fintech or HR tech experience)

All candidates must be physically located in the US. No exceptions. Bonus for being located in CA and even better, San Diego.

Interview process: phone call, interview with each founder separately, reference checks, and offer (can be done in less than a week).

If interested, please reach out to hire@himodus.com.

I think that's a valid criticism. What do you think would be a more ergonomic pattern?

I wrote a static config class that reads configuration for the entire app / server from a JSON or YAML file ( https://github.com/uber/zanzibar/blob/master/runtime/static_... ).

Once you've loaded it and mutated it for testing purposes or for copying from ENV vars into the config, you can then freeze it before passing it down to all your app level code.

Having this wrapper object that can be frozen and has a `get()` method to read JSON like data make it effectively not mutable.

I use similar pattern myself. Was curious if the OP is using some other, like for instance splitting the struct into two (im/mutable) and then passing them around, or what.

BTW kudos on zanzibar. Love the tech and the code).

Not the OP, but I mitigate the issue rather than use a different pattern. Like so:

type Server struct { val bool }

type Config struct { Val bool }

func NewServer(... config *Config ...) http.Handler { if config == nil { config = &Config{} } return &Server{ val: config.Val } }

It took me a long time to settle on this pattern and I admit it's tedious to copy configuration over to the server struct, but I've found that it ends up being the least verbose and maintainable long term while making sure callers can't mutate config after the fact.

I can pass nil to NewServer to say "just the usual, please", customize everything, or surgically change a single option.

It's also useful for maintaining backwards compatibility. I'm free to refactor config on my server struct and "upgrade" deprecated config arguments inside my NewServer function.

I just use a struct literal, and then I have the type define a `func (t *Thing) ready() error { ... }` method and call the ready method to check that its valid. I prefer this over self-referential options, the builder pattern, supplying a secondary config object as a parameter to a constructor, etc.