Hacker Newsnew | past | comments | ask | show | jobs | submit | SSchick's commentslogin

They do as the slop king Satya guides (yes).

He wants more “diffusion”. Slopya says “diffusion” so you better “diffusion”. They need AI…

DIFFUSION


Fed *bool `json:"is_fed"` // you can never be sure

felt that part


https://github.com/python/typing/pull/2137

PR is somewhat WIP-ish but I needed some motivation to do OSS work again :)


For those interested: the results page in this PR looks like this:

https://htmlpreview.github.io/?https://github.com/SimonSchic...


Thanks.

I really need better generics support before ty becomes useful. Currently decorators just make all return types unknown. I need something this to work:

    _F = TypeVar("_F", bound=Callable[..., Any])
    def my_decorator(*args: str) -> Callable[[_F], _F]: ...
Also, I use a lot of TypedDicts and there's not much support yet.


Is it just me or are the code examples of the executors absolutely unreadable/comprehensible without reading it 5 times?

Even with different formatters I'd much prefer the tbb variant.


How about executive compensation?


That would make everything maybe 1 cent cheaper, so it's not really significant.


Yea whenever the idea of a company's profit is under a microscope, people often reflex to exec "greed" but it's typically because it's easier to blame a fictional disney villain, than it is to dig into the root of the problem.


If you can explain why anyone needs $8.469 billion of profit (2023), I'll gladly hear you out about greed. But something tells me I'm not going to get a great answer. :)


It would however have second-order effects; having less wealthy people would drive down rents/etc. If the wealthy just keep getting wealthier you'll end up in a situation where the wealthy just trade between each other out because of higher margins and the working class has nowhere to buy things.


Is this an AI generated post?


Yes, it was written by a SoTA AGI trained for more than 30 years.

I would like to add that predictable generation defeats the very purpose of generative AI, so prompt engineering in this context will never equate to what engineering means in general.


I've done a fair amount of vibe coding cleanup, ironically using a fair about of LLMs, a lot of leadership are under the false impression that more code means better product, their ignorance is my gain.


Ok, what is your counter argument?


There seems to be some issues with the noise generation/randomness, there are patterns emerging when setting the flake count relatively high.


A lot of "engineers" nowadays don't know the concept of per-user/customers configs and how to build/expose them to non-technical staff.

The main appeal of feature flags is simplicity and being a low-hanging way to apply per-customer/user configuration, few platforms allow true a/b testing (amplitude comes to mind but I'm sure there are more).


Feature flag can (usually does??) have another meaning, as a technical feature rollout mechanism, so you can roll back quickly without a deployment. A way to manage risk on teams that make hundreds of commits/deploys a week. You can then often send a certain % of traffic through the feature or not to look for early warnings.

I don't like feature flags for config. Just build a config system into the product UI - a settings page basically! That might have some bits you configure as the site owner, and some that are self-service.


Statsig and launchdarkly are the one that come to mind for me.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: