Papers would be good next step. The concept and the algorithms do not seem very complex. The training and fine tuning is what needs effort and infrastructure.
Hey there! No changes to the api server configuration are required. We've designed Infra around this since AKS/EKS/GKE don't expose the ability to edit api server parameters to users.
Tokens are verified by intercepting API server requests in-cluster against a central root of trust. This is similar to how OpenID tokens from identity providers such as Okta or Active Directory are verified by destination web applications. This works no matter where clusters are hosted (including GKE/AKS/EKS or self-hosted clusters).
Great question! Most managed Kubernetes services don't support OIDC (and for EKS, which does support custom OIDC providers, it requires restarting the entire control plane to edit the configuration).
Infra runs a lightweight process in-cluster that intercepts requests and verifies them - and yes, this process intercepts requests and then impersonates the correct users and groups.
I have worked at Human API as a software engineer for about 7 months now and I love it.
- Everyone is friendly and easy to work with
- The working environment is positive
- There are plenty of opportunities to branch out and take ownership over important problems
I'd be happy to answer any questions anyone has about life at Human API!
> let and const only control mutability of the reference. They say nothing of the value mutability. const then can only be a signal that you are not reassigning to the identifier.
Wouldn't this definition suggest that the value CAN be reassigned? The reference could be immutable but allow value reassignment, but is not the implementation of const.
> The reference could be immutable but allow value reassignment, but is not the implementation of const.
You can reassign values through a const reference in javascript. For example:
const x = [1]
x[0] = 2 // ok!
This just doesn't work with primitive values, because primitive values are immutable and copy-by-value. So this works with lists but not strings (because strings are a primitive and thus immutable).
Or, put in C++ friendly terms, javascript doesn't distinguish between pointer reassignment and value reassignment. It only has reassignment, which is illegal for const variables. Variables which hold non-primitives (lists, objects, etc) are actually pointers to those values. const does not affect the mutability of the value stored at the pointer.
Most industries don't have a Hacker News. In my opinion, it is coming. Tech-savvy generations will be moving into senior roles, and they will look to communicate online.
My main question is are these other industries as passionate as the tech industry? Are they as collaborative? I am from the oil and gas industry, and I can firmly say that currently the answer to those two questions for the oil industry is a hard "No". But that might change.
Couldn't one argue that the oil and gas industry is on the way out itself? I know that may come off as a bit naive. My anecdotal experience leads me to believe that the oil and gas industry isn't exactly pushing the envelope technologically. Sure there is a lot of cutting edge science and technology applied on a macro level, but for the industry to truly embrace the future would mean to become something entirely new.
I don't see this industry embracing the hyper connectivity, progressive, mind-share of the internet the same way I only see half-hearted engineers entering this field.
Your DO section starts when you have already gotten the interview...but that is the hardest part for someone who is self taught or fresh out of a bootcamp.
You need to do everything in the article just to get an interview, just to get a chance.
Getting your foot in the door is by far the hardest part of trying to make a career switch into software development. A lot of people say that you shouldn't have to eat, drink, and sleep code and self-marketing to get an interview with a non-traditional background.
My opinion is that people changing their careers into software development have it easy. Name me another engineering degree where you can teach yourself and get an interview without a degree in that field.
There is logic to minimize false positives/negatives. For example, it does a pretty good job distinguishing between (c, c++, obj-c), (java, javascript), and (react, react native).
If you type "remote" in the location textbox, it will only show submissions that are available remotely. Open to implementing other features.
it occurred to me today that rather than provide an open search box, or try to filter by specific semantic fields, it might be really interesting to just provide a view of the keywords by frequency (whether 'react' or 'boston' or 'social')
There is logic to minimize false positives/negatives. For example, it does a pretty good job distinguishing between (c, c++, obj-c), (java, javascript), and (react, react native).
If you type "remote" in the location textbox, it will only show submissions that are available remotely.
The part I'm unsure of is what next? Seems like diving into papers might be a decent leap. Who knows, maybe GPT-4 can help me bridge the gap