kylequest

10 ms·

31.
by kylequest 5y ago
Slim.AI | Backend Engineer | REMOTE or Seattle/Bellevue/WA | Full-time | https://github.com/slim-ai/engineering/blob/master/roles/bac... Our mission is to empower developers to create and
32.
by kylequest 5y ago
Good to see it MIT licensed... A few other options in this space including EasyHook (which is also MIT licensed)...
33.
by kylequest 6y ago
Slim.AI | REMOTE, Seattle, Bellevue | Full-time | Backend, Full Stack, Linux System and Kernel Development, DevX | https://www.slim.ai Do you like building cloud-native applications? Do you like using containers? Or better yet,
34.
by kylequest 6y ago
Golang gotchas are fun :) Some of them are for beginners while others will trip you up even when you've done a lot (e.g., variable shadowing). Here's another golang gotchas post from a while back: http://devs.cloudimmun
35.
by kylequest 6y ago
Slim.AI ( https://slim.ai ) | Frontend or Fullstack | REMOTE or Seattle | Full-time | https://github.com/slim-ai/engineering We love Vue, Nuxt and Node. Join us if you feel the same. Great if you are curiou
36.
by kylequest 6y ago
Slim.AI | REMOTE or Seattle | Full-time | Developer Experience Lead | https://github.com/slim-ai/engineering Do you enjoy working with lots of different applications stacks? Do you like helping others? Do you want to b
37.
by kylequest 6y ago
Aside from not allowing non-competes what is there to copy?
38.
by kylequest 6y ago
Slim.AI | REMOTE or Seattle | Full-time | Developer Experience Lead | https://github.com/slim-ai/engineering We are looking for someone, who will enjoy working with lots of different applications stacks helping others,
39.
by kylequest 6y ago
Slim.AI | REMOTE or Seattle | Full-time | Linux System and Kernel Developer | https://github.com/slim-ai/engineering I'm the CTO at the company and I'm looking for someone who likes exploring Linux system int
40.
by kylequest 6y ago
Our stack: * AWS (serverless, containers, EC2) * Vue.js/Nuxt.js-based frontend * Node.js-based BFF (Backend For Frontend) * Go-based platform backend. * Go-based core engine (containers and low level Linux system internals). Roles: * D
41.
by kylequest 6y ago
Slim.AI | https://github.com/slim-ai/engineering | REMOTE or Seattle | Full-time | Backend, Full Stack, Linux System Internals, DevX We are a seed stage startup in the developer tooling and DevOps space empowering deve
42.
Statically Compiling Go Programs(arp242.net)
6 points by kylequest 6y ago|0 comments
43.
Rust from Go's Perspective(youtube.com)
1 points by kylequest 7y ago|0 comments
44.
Software Is Synthetic(infoq.com)
2 points by kylequest 7y ago|0 comments
45.
by kylequest 7y ago
And with Kubernetes you can use Ephemeral Containers for that.
46.
by kylequest 7y ago
This is a great idea! Thank you for your feedback. Using native docker flags as-is will definitely reduce friction and simplify the use. Do you mind creating a Github issue if you have a specific list of flags you'd like to see support
47.
by kylequest 7y ago
docker-slim also gives you useful info about the original container image in addition to minifying your container (you can actually run it without the minification part if you want). It will "reverse engineer" the Dockerfile for y
48.
by kylequest 7y ago
Different application runtimes have interesting hidden behaviors. With Python, for example, the runtime will generate cache files from your .py files and then it'll use it instead of those .py file. However, it still checks if the orig
49.
by kylequest 7y ago
Do you mind sharing a bit of information about your container images? What's the app language for both? What kind of application is it? How do you init your apps in the containers? docker-slim is definitely not perfect and there's
50.
by kylequest 7y ago
Thank you for the your feedback! It's very important for a tool like this to be clear and transparent about what it's doing. The docs definitely need to be improved. It's already a lot for some info to be lost and not enough,
51.
by kylequest 7y ago
One of the monitors leverages FANOTIFY in Linux to determine what files your application is using. This is the same thing many AV tools use to detect malware :-) The future version will get more different runtime monitors and it will do muc
52.
by kylequest 7y ago
At this point in time the tool is mostly relying on dynamic analysis though there's a bit of static analysis too when you want to include extra artifacts. The dynamic analysis part is done using a couple of different monitors that look
53.
by kylequest 7y ago
Yes, it is a potential problem, but in most real world cases it's good enough and if you have a decent test coverage to begin with (which you should have :-)) you can run those tests when the container is minified and after to confirm
54.
by kylequest 7y ago
Yes, the coverage might not always be ideal. The tool will have additional static analysis to figure out the coverage. For now it relies on you to create custom probes to ensure better coverage if you need it...
55.
by kylequest 7y ago
The temporary containers usually don't run for too long. The probes (http, for now) are there to ensure that the app/services gets to do something useful exercising different code paths. Still, it is possible that something could
56.
by kylequest 7y ago
speaking of dive... there's a bit of overlap between docker-slim and dive. docker-slim produces similar container image reports (with more details about the layers, but no diffs, for now... the layer diff support is coming)
57.
by kylequest 7y ago
i'll be happy to answer any questions about the tool (i'm the main author) :-)
58.
by kylequest 7y ago
The main catch is that it targets application container images and not generic base images. This is the most common gotcha many people encounter. There has to be an app/service in the container that does something specific. And, of cou
59.
The Art of SLOs(landing.google.com)
2 points by kylequest 7y ago|0 comments
60.
Abusing VPC Traffic Mirroring in AWS(rhinosecuritylabs.com)
1 points by kylequest 7y ago|0 comments

More ›