I'm sure most of us have had to deal with issues reported by end users that we ourselves aren't able to reproduce This video is an extended case study going through my thought process as I tried to track down and fix a mysterious performance regression which impacted a small subset of end users I look at the impact of acquiring mutex locks across different threads, identifying hot paths by attaching to running processes, using state snapshot comparisons to avoid triggering hot paths unnecessarily, the memory implications of bounded vs unbounded channels, and much more
I updated my [NixOS on WSL starter template](https://github.com/LGUG2Z/nixos-wsl-starter) for NixOS 24.05 and created a fresh walkthrough video. WSL is how I first got started with NixOS (and now I use it to manage more servers and machines than I can keep track of!) and I'm a big proponent of being able to quickly spin up a simple flake with a relatively flat structure where people can play around with settings to come up with something they feel comfortable applying to a bare metal machine at a later point in time.
Hi friends, I develop and maintain the [komorebi tiling window manager](https://github.com/LGUG2Z/komorebi) and have been posting live coding videos documenting its development for just over a year now. I'm starting [a new mini series on building a visual debugging gui tool](https://www.youtube.com/watch?v=zZKjBMt4kZ4) to aid development on komorebi and especially to help with understanding some of the more esoteric edge cases and the interactions between the twm, user-defined rules and WinEvents. I'll be building this from scratch using egui/eframe, so if you're interested in what building a non-trivial real-world immediate-mode gui and integrating with other (Rust, in this case) processes via IPC looks like, you'll probably get something out of this series.
Sharing some numbers on what people can realistically expect with GitHub Sponsors on a moderately popular project without any external / VC / corporate backing.
LGUG2Z 6 months ago • 100%
Yeah this is usually the way to go, I think I just got unlucky that this particular service on nixos-23.11
doesn't have a package
override option (but it will have in nixos-24.x
releases!)
cross-posted from: https://lemmy.world/post/13113247 > After learning how to add an unstable overlay to nixpkgs, being able to override individual service modules from unstable was something that I still struggled with until fairly recently. Hopefully this helps someone else looking to do common-but-not-very-obvious operation.
After learning how to add an unstable overlay to nixpkgs, being able to override individual service modules from unstable was something that I still struggled with until fairly recently. Hopefully this helps someone else looking to do common-but-not-very-obvious operation.
In this video I discuss the trade-offs of building on top of unstable reverse-engineered private APIs, why I decided against it, and compare to similar software that chose to use them. A couple of people who aren't particularly interested in the software itself told me that this was an interesting and engaging video on general programming approaches when building applications for closed-source systems, so I thought I'd share it a bit more widely here.
LGUG2Z 10 months ago • 100%
Thanks for the kind words :) Sent you a message 🤞
LGUG2Z 10 months ago • 100%
Thank you! Though please keep in mind this part of the README 😅
While Satounki is currently in a functional state, there are no documented steps for deployment and I don't recommend that anyone use this software for anything mission-critical just yet.
Depending on how badly my current job search goes (lol) I'm hoping to have this in an easily deploy-able format for both NixOS and Kubernetes, but it's not too difficult to get up and deployed if you follow the development instructions and provision the credentials in the relevant places 🤞
LGUG2Z 10 months ago • 100%
tl;dr all the same caveats with self-hosted software apply; don't do anything you wouldn't do with a self hosted database or monitoring stack.
Well the actual rules — who gets access to what
The rules themselves are the same public rules in the IAM docs on AWS, GCP etc., while the collections of these public rules (eg. the storage_analytics_ro
example in the README) defined at the org level will likely be stored in two ways: 1) in a (presumably private) infra-as-code repo most probably using the Terraform provider or a future Pulumi provider, 2) the data store backing the service which I talk about more below.
"Who received access to what" is something that is tracked in the runtime logs and audit logs, but as this is a temporary elevated access management solution where anyone who is given access to the service can make a request that can be approved or denied, this is not the right place or tool for a general long-lived least-privilege mapping of "this rule => this person/this whole team".
where is that stored and how is it secured, to what standards?
This is largely up to the the team responsible for the implementation and maintenance, just like it would be for a self-hosted monitoring stack like Prom + Grafana or a self-hosted PostgreSQL instance; you can have your data exposed through public IPs, FQDNs and buckets with PostgreSQL or Prom + Grafana, or you can have them completely locked down and only available through a private network, and the same applies with Satounki.
Is there logging, audit, non-repudiation, tamper-proof, time-stamping etc.
Yes, yes, yes, yes and yes, though the degree of confidence in each of these depends to some degree on the competence of the people responsible for the implementation and the maintenance of the service as is the case with all things self-hosted.
If deployed in an organization which doesn't adhere to at least a basic least-privilege permissions approach, there is nothing stopping a bad internal actor with Administrator permissions wherever this is deployed from opening up the database directly and making whatever malicious changes they want.
LGUG2Z 10 months ago • 100%
What sort of sensitive data are you imagining in your reading of the README? It would be useful to understand to update the language appropriately 🙏
cross-posted from: https://lemmy.world/post/9143654 > Apologies in advance for sharing two link posts here two days in a row. Unemployment may be driving me a little nuts... 😅 > > I've been working on Satounki since I got laid off last month. It's the culmination of a lot of experience building similar ad-hoc internal tooling at various places throughout my professional career. > > Satounki already includes: > > * AWS support > * GCP support > * Cloudflare support > * Auto-generated Terraform providers from the Rust API > * Auto-generated Typescript client wrapper from the Rust API > * Slack bot for request notifications, approvals and rejections > * CLI for requests, approvals and rejections > * Dashboard for exploring policies, requests and stats > > The scope of this project is pretty big and I'm looking for contributors. > > The majority of the project is written in Rust, including the generated Go and TS code. The stack is pretty simple; Actix, Diesel, SQLite, Tera etc., so if you have experience with writing web apps in Rust it should feel familiar! > > Even if this is a totally new stack to you, this is a great project to develop some familiarity and experience with it, especially if you can help improve the quality of the generated Go and TS code at the same time!
cross-posted from: https://lemmy.world/post/9143654 > Apologies in advance for sharing two link posts here two days in a row. Unemployment may be driving me a little nuts... 😅 > > I've been working on Satounki since I got laid off last month. It's the culmination of a lot of experience building similar ad-hoc internal tooling at various places throughout my professional career. > > Satounki already includes: > > * AWS support > * GCP support > * Cloudflare support > * Auto-generated Terraform providers from the Rust API > * Auto-generated Typescript client wrapper from the Rust API > * Slack bot for request notifications, approvals and rejections > * CLI for requests, approvals and rejections > * Dashboard for exploring policies, requests and stats > > The scope of this project is pretty big and I'm looking for contributors. > > The majority of the project is written in Rust, including the generated Go and TS code. The stack is pretty simple; Actix, Diesel, SQLite, Tera etc., so if you have experience with writing web apps in Rust it should feel familiar! > > Even if this is a totally new stack to you, this is a great project to develop some familiarity and experience with it, especially if you can help improve the quality of the generated Go and TS code at the same time!
Apologies in advance for sharing two link posts here two days in a row. Unemployment may be driving me a little nuts... 😅 I've been working on Satounki since I got laid off last month. It's the culmination of a lot of experience building similar ad-hoc internal tooling at various places throughout my professional career. Satounki already includes: * AWS support * GCP support * Cloudflare support * Auto-generated Terraform providers from the Rust API * Auto-generated Typescript client wrapper from the Rust API * Slack bot for request notifications, approvals and rejections * CLI for requests, approvals and rejections * Dashboard for exploring policies, requests and stats The scope of this project is pretty big and I'm looking for contributors. The majority of the project is written in Rust, including the generated Go and TS code. The stack is pretty simple; Actix, Diesel, SQLite, Tera etc., so if you have experience with writing web apps in Rust it should feel familiar! Even if this is a totally new stack to you, this is a great project to develop some familiarity and experience with it, especially if you can help improve the quality of the generated Go and TS code at the same time!
LGUG2Z 10 months ago • 100%
Thanks! Turns out I have a lot more time on my hands to be found around the internet since I got laid off last month 😅
This (Windows employing different methods to prevent users from writing programs that programmatically change application focus) has been an ongoing struggle for me for the better part of 3 years. I finally made what feels like some significant progress this past week. If you've ever obsessively gone deep down into a hole trying to understand and wrangle weird OS-level behaviors before, you might enjoy this video and feel a vicarious sense of victory :)
LGUG2Z 10 months ago • 100%
This looks cool! It's not packaged on nixpkgs yet so I might package it and then try to selfhost 👀
LGUG2Z 10 months ago • 100%
I wish I had more advice, but I'm in a similar boat, just got laid off earlier this month after being with the same company from Series A in 2018 all the way until today. I'm sending job applications and trying to get interviews, but it's hard to get past the resume screening stage, even with 8+ years of experience.
I've mainly been working in DevOps/SRE/Platform Infrastructure, but I am also an accomplished developer with a pretty thick portfolio of widely used open source projects, though it doesn't seem to matter.
There are so many applicants for every single job now that it feels hopeless, and of course every single opening wants you to waste your time on multiple asinine LeetCode gotcha questions.
If I lived somewhere with a public health system I'd love to take what money I have saved up and open a traditional middle eastern bakery, but I need to do something that will bring health coverage for myself and my family. Who knows, I might just end up working at Trader Joe's. 🤷♀
I got laid off this month and have a lot of time on my hands while I'm looking for new jobs 😅 I tried making a LinkTree but the website UI for editing is so janky and frustrating, and on top of that you have to go Premium for advanced theming, again in the janky UI... I found this great Hugo theme called [Lynx](https://themes.gohugo.io/themes/lynx/) and built out [my own links webpage](https://linktree.lgug2z.com) like we did back in 90s on Geocities with Dreamweaver Some folks on Mastodon and Twitter messaged me asking for a walkthrough because there are a few rough edges that are mostly related to changes between Hugo versions and the docs on the theme, so I made this end-to-end video going from project init to deployment on Cloudflare pages with analytics enabled It's a pretty fun project and I think it can also be useful as a "portfolio links" page for people that are looking for jobs right now
LGUG2Z 10 months ago • 100%
It's not exactly a traditional RSS feed, but I run a feed of my highlights on all things related to software development, and I'm an experienced DevOps engineer so a lot of my highlights are coloured by that experience.
If you come across a highlight that is interesting you can click to go and read the whole source article or comment. You can check out a HTML version before you decide if you wanna subscribe to the RSS feed.
cross-posted from: https://lemmy.world/post/8269080 > Someone on another website asked me whether it makes sense to use `agenix` or `sops-nix` to encrypt secrets for NixOS configurations. > > I realized that I hadn't seen a good overview article of the different approaches to secret handling in NixOS and when each one is appropriate to use, so I put down all of my knowledge and opinions in this post 🤞 >
Someone on another website asked me whether it makes sense to use `agenix` or `sops-nix` to encrypt secrets for NixOS configurations. I realized that I hadn't seen a good overview article of the different approaches to secret handling in NixOS and when each one is appropriate to use, so I put down all of my knowledge and opinions in this post 🤞
It currently requires some extra steps to get Nitter up and running on NixOS as I found out yesterday. I documented the process for anyone else who might be looking to run their own Nitter instance between now and the trunk branch of Nitter being functional again.
LGUG2Z 11 months ago • 100%
I think it's a stack that really pays off in the long run for solo projects. After a long week of work the last thing I want to do is go tracking down runtime errors (undefined is not a function
, my old friend) or messing around with Docker containers and Kubernetes clusters. It also doesn't hurt that once you throw away the costly deployment abstractions, the operating expenses turn out to be a lot cheaper.
Found some time this past weekend to work on a little "passion feature" that I've been wanting to implement for a while now; sharing the technical write-up for anyone else who is interested in automating headless screenshots with these tools or with others (the knowledge is pretty transferable!)
These days I reach for [`chumsky`](https://github.com/zesterer/chumsky) pretty much any time I need to write a DSL parser. I thought it would be an interesting exercise to take a DSL parser that I've written using `chumsky` and reimplement it the "old fashioned" way.
For a while I've wanted to work through this book in Rust, and while I could find some finished (and often further refined) implementations of `lox` in Rust, I was not able to find an equivalent step-by-step snapshot of code at the end of each exercise of the book in Rust. I decided to try doing the first exercise myself and record the progress to hopefully help others in the future. The code in the video is not (intended to be) the most idiomatic Rust, as I was trying to stick as closely to the source material in Java as possible, but I think that in a way this has its own advantages for people who are interested in learning more about Rust.
I put together a proof of concept for controlling a tiling window manager using voice commands. Hopefully this can make twm workflows easier for people who suffer from RSI or for whom keyboard shortcuts are impractical. I think that this approach can be replicated for any tiling window manager that exposes a CLI interface to send interaction messages (bspwm, yabai, etc)
LGUG2Z 1 year ago • 100%
The whole point is that you can build a working container image and then ship it to a registry (including private registries) so that your other developers/users/etc don’t have to build them and can just run the existing image.
Agreed, we still do this in the areas where we use Docker at day job.
I think the mileage with this approach can vary depending on the languages in use and the velocity of feature iteration (ie. if the company is still tweaking product-market fit, pivoting to a new vertical, etc.).
I've lost count of the number of times where a team decides they need to npm install
something with a heavy node-gyp
step to build native modules which require yet another obscure system dependency that is not in the base layer. 😅
LGUG2Z 1 year ago • 100%
We all use Linux on our workstations and laptops. That might make it easier.
You are living my dream!
I think this is the key piece; the experience of Docker on Linux (including WSL if it's not hooking into Docker Desktop on Windows) and on macOS is just so wildly difference when it comes to performance, reliability and stability.
LGUG2Z 1 year ago • 100%
Thanks for sharing this! Added to my weekend inspiration/reading pile. 🙏
LGUG2Z 1 year ago • 83%
Highly recommended viewing if you'd like to learn more about the limits of reproducibility in the Docker ecosystem.
LGUG2Z 1 year ago • 71%
Tutorial != advocation. As I said, no attempt to engage in good faith.
LGUG2Z 1 year ago • 100%
I understood your point, and while there are situations where it can be optional, in a context and scale of hundreds of developers, who mostly don't have any real docker
knowledge, and who work almost exclusively on macOS, let alone enough to set up and maintain alternatives to Docker Desktop, the only practical option becomes to pay the licensing fees to enable the path of least resistance.
LGUG2Z 1 year ago • 61%
Lot's of (incorrect) assumptions here and generally a very poorly worded post that doesn't make any attempt to engage in good faith. These are the reasons for what I believe is my very first down-vote of a comment on Lemmy.
LGUG2Z 1 year ago • 100%
I believe this is the Docker Desktop license pricing.
On an individual scale and even some smaller startup scales, things are a little bit different (you qualify for the free tier, everyone you work with is able to debug off-the-beaten-path Docker errors, knowledge about fixes is quick and easy to disseminate, etc.), but the context of this article and the thread on Mastodon that spawned it was a "unicorn" company with an engineering org comprised of hundreds of developers.
LGUG2Z 1 year ago • 89%
Hi!
First I'd like to clarify that I'm not "anti-container/Docker". 😅
There is a lot of discussion on this article (with my comments!) going on over at Tildes. I don't wanna copy-paste everything from there, but I'll share the first main response I gave to someone who had very similar feedback to kick-start some discussion on those points here as well:
Some high level points on the "why":
-
Reproducibility: Docker builds are not reproducible, and especially in a company with more than a handful of developers, it's nice not to have to worry about a
docker build
command in the on-boarding docs failing inexplicably (from the POV of the regular joe developer) from one day to the next -
Cost: Docker licenses for most companies now cost $9/user/month (minimum of 5 seats required) - this is very steep for something that doesn't guarantee reproducibility and has poor performance to boot (see below)
-
Performance: Docker performance on macOS (and Windows), especially storage mount performance remains poor; this is even more acutely felt when working with languages like Node where the dependencies are file-count heavy. Sure, you could just issue everyone Linux laptops, but these days hiring is hard enough without shooting yourself in the foot by not providing a recent MBP to new devs by default
I think it's also worth drawing a line between containers as a local development tool and containers as a deployment artifact, as the above points don't really apply to the latter.
Some folks on the internet were interested in how I had managed to ditch Docker for local development. This is a slightly overdue write up on how I typically do things now with Nix, Overmind and Just.
LGUG2Z 1 year ago • 100%
I initially tried it when I first switched to Windows, but as I mentioned in another comment, it lacks the ability to automatically (re)arrange the windows on the screen in response to events like new windows opening, windows minimizing or being closed, etc.
LGUG2Z 1 year ago • 100%
The biggest difference vs. the built-in snapping is that when you move one window, all of the other windows move in relation to that window based on the layout algorithm you choose, and when you add a new window to the workspace, all of the other windows rearrange in relation to that new window, etc.
In this way, it's very similar to Linux tiling window managers like bspwm
and i3
, which allow you to arrange your desktop on-the-fly using only keyboard shortcuts.
LGUG2Z 1 year ago • 100%
If you've ever seen some of the cool window managers on communities like !unixporn@lemmy.world, you should know that you can achieve a similar workflow on Windows too!
To accompany the latest release of komorebi, I have created a brand new quickstart video! https://github.com/LGUG2Z/komorebi/releases/tag/v0.1.17
LGUG2Z 1 year ago • 100%
I actually stayed there (I'm still there); just finished taking my 2 month paid sabbatical, I now have an 8 hour time zone difference with most engineers so I get to work on my own without distractions, and I have a strong policy of not developing anything bespoke and only plugging together off-the-shelf components (I specialize in Platform and Infrastructure).
With the mindset shift, it's actually a pretty relaxing job. I make $180k, which isn't the best salary, but also far from the worst, and I have both an abundance of time and very little oversight (amplified with the timezone difference now that I'm in the US) which means that I can use that salary to pursue things that I am interested in, spend time with my family etc.
I definitely thought about quitting at the time, but visa restrictions (I had just arrived in the US on an L1-B visa which is non-transferable) meant that I couldn't. Now I'm a permanent resident, so I could leave if I wanted to, but I think that "quiet quitting" is still the right choice for where I'm at in my life.
LGUG2Z 1 year ago • 100%
A few years ago, back when I still gave a damn (and probably during my most productive quarter in my entire professional career), somebody complained that my language was too curt on Slack, and I was a denied a 20k performance bonus as a result. It was pretty easy to not care after that.
LGUG2Z 1 year ago • 100%
If you see links that you find interesting, throw them into kulli.sh, and you get back a consolidated comment feed of every Lemmy community it is being discussed in. You can take a look at the kind of comments and discussions in different communities and see if there are any that have the sort of vibe that you're looking for and then go ahead and subscribe!
So I use `komorebi` on Windows, `yabai` on macOS and `bspwm` on Linux. They are all kinda similar, but at the same time have different feature sets which make certain workflows possible on one but not the other. How do you handle this problem if you are someone regularly switches between operating systems? Personally, I've started restricting myself as much as possible to using just the features and workflows that can be reproduced across all operating systems and twms, so that when I switch, there isn't any one thing that I'm missing "too much" that the experience gets soured and my productivity tanks.
LGUG2Z 1 year ago • 100%
More and more lulls with more and more years of experience. I hit the gym more, socialize more, cook more extravagantly, take walks more often etc. The most important thing was to train myself to not give a damn when people were making stupid decisions at work that were going to bite them N months down the line during those lulls.
LGUG2Z 1 year ago • 100%
It's a piece of software which automatically arranges open windows on your desktop according to different algorithms and layouts, and allows you to switch focus them and move them around in the layout by using keyboard shortcuts. One you get in the flow, you very rarely have to use the mouse to move windows around, maximize them, minimize them, resize them etc.
If you've ever seen a post on !unixporn@lemmy.ml or similar places, the vast majority of them are using tiling window managers to get that look of clean organized windows on the desktop!
https://lemmy.world/c/tilingwindowmanagers !tilingwindowmanagers@lemmy.world [Tiling Window Managers](/c/tilingwindowmanagers@lemmy.world)
In the hope that other developers join this community, I'll get things rolling! I'm LGUG2Z and I'm the developer of `komorebi` for Windows which is heavily inspired by my experiences with `bspwm` and `yabai` 👋 ![](https://lemmy.world/pictrs/image/495b04fd-1654-4520-b165-b11470d65bf9.png)
LGUG2Z 1 year ago • 100%
It hurts economically to live here, but even with that and all the social problems, it's still the best city I've ever lived in. 🤷♀
LGUG2Z 1 year ago • 100%
I would love to see a modern version of Onimusha with Sekiro-style deflect combat
LGUG2Z 1 year ago • 100%
Do you have to subscribe to character pass to get new characters in this game? Are there no characters that get unlocked after completing the game? 👀
LGUG2Z 1 year ago • 100%
Beautiful!
LGUG2Z 1 year ago • 100%
If you're already familiar with this video, you may feel at home with us in !recovery@lemmy.world! :)
One of my most powerful morning rituals is clicking my tally counter when I wake up to count each new day of sobriety, followed by reading out a card aloud from an affirmation card set. Is there anything that you do in the mornings to celebrate a each daily reprieve?
cross-posted from: https://lemmy.world/post/1145382 > I re-watch this powerful short "illustration on addiction" every year to remind myself of the importance of waking up and choosing sobriety every day.
LGUG2Z 1 year ago • 100%
If you want an idea of what the breadth of this kind of search can look like, check out the results for the article "How to Kill a Decentralised Network" which has been making the rounds recently.
LGUG2Z 1 year ago • 100%
This is exactly what I needed for the desktop!
LGUG2Z 1 year ago • 100%
If I can even help one person avoid that same fate, it's worth it!