I started off on mailing lists (openldap was a big one for me). And my first pleas for help were often met with some pretty brutal scathing replies. I learned to really write up the problem, reduce it to its point. Go back to it so I could find the most concrete path to either reproduce it, or isolate it. This often led to the solution, or it led to getting some confirmation of bugs. Granted I definitely ended up making some verbose emails and then I would get frustrated with people asking me to try things I detailed in my email.
But that was my "rubber duck debugging". Start by writing an email to to an imagined hostile support group. In the process of explaining the problem, it turns into a research project where I have to defend my claims. The sheer act of writing it out forces me to isolate the issue and keep troubleshooting. I can anticipate the bulk of the things they would have me try and I'd try them ahead of time.
People encountered similiar pushback with stack overflow, but I think the stack sites were much more lenient than some of those early mailing lists were.
I did this with nreal air glasses (now xreal air), specifically for coding. Most uses cases for these type of glasses is around media consumption, so I was taking a bit of a leap when doing it for coding/heavy text usage.
There are two modes. One is fixed so that the virtual monitor stays in one spot on the lenses. The single virtual monitor stays directly in front of you. The other is floating, which basically keeps the virtual monitor in one spot and you can turn your head to look away. This mode also lets you set up 3 virtual monitors side by side so you can turn to look at them. It uses head tracking to basically shift the image in the opposite direction you turn your head.
In both cases, the screen does move, and this is super relevant when looking at text and down at status bars. The fixed one is better because it moves relative to your head, but both cases have some amount of jitter. I found the best case coding scenario is the fixed monitor (no head tracking), and being in a seat wth head rest and you can press your head back into it. This minimizes your head movement, which minimizes how much the text moves about. The downside is that we're used to looking up and down at the screen, so you want to set the monitor at a proper distance so you can look up and down with just your eyes. You really want to shrink the monitor to a size close to that of a laptop.
I ultimately ended up not liking the experience very much. No matter what, you're gonna end up with some amount of text movement. There is also a bit of light saturation bleed through (old CRT style). Putting the blackout blinders on helps a lot, but the projected nature remains an issue. Essentially only usable long term in a recliner or a car seat with headrest. Unlike the author, I am using a work provided laptop and I have that with me anyways. There was coolness to leaving the laptop in my backpack and just bringing the glasses up via wire - but to actually do anything, I need a keyboard. Which means taking along a Lenovo's thinkpoint trackpad keyboard (really great backpack keyboard); or pulling out the laptop.
The newer ones, like Xreal One from the article might be a better experience. A coworker had the air 2 pros and used them for travel. He said he didn't really notice the things I did, so maybe it was a improved experience even with that version. But he mostly worked in office documents and only occasional terminal work. When traveling and using the glasses, it was almost all "office docs", and only for short periods of time. For me - I am going to wait and be a slow adopter to move to a new version.
Just sit right back and you'll hear a tale, A tale of a fateful trip
That started from this tropic port. Aboard this tiny ship. They got lost but they called for help, and now they're totally fine. And now they're totally fine.
I think they're mixing the GH web ui with the syntax. You can paste an image right into the editor and it does a really good job of inserting it right where you need to. It is really good UX that I miss when editing markdown locally. Obsidian also does a decent job, but not quite as smooth.
So I also do use gitlab quite a bit, but not as much recently. I went to compare. Gitlab actually does have a similiar ux experience, though I'd give the Github one just a bit of an edge. It looks like the key difference is that github converts a pasted image to an html image tag, while gitlab uses markdown with the width/height brackets that the end.
Honestly, I think using an html image tag is the right way to go. I type in markdown all the time, and I have no problem making links. But markdown image syntax I have to double check each time or let the editor figure it out. HTML image tags, I find easier to remember and read than a markdown one. (But maybe that's because I learned HTML before markdown).
Glad to see this on here. I've been using this for 3 years now with my club to track race course participants for a 50K. Radio operators at each station call in bib numbers, and we drag their bib from their last waypoint to the new one. There is a laptop in the van mirrored to a TV outside the van. Friends and family can then check on their particpant.
I basically modified the CSS a bit so you can fit multiple cards in a row. nullboard as a board import/export feature to a simple json file. I have small python script that generates the columns (way-points) and cards (bib numbers). Then I can import that json to start that years race. While I would like more features (time tracking), it's a rather simple tool that can be easily operated offline and requires no resources other than a web browser.
When I did more field work, I would use a tool called Look@Lan. This would scan the network and detect common open ports. Similar functionality to nmap, but in a nice gui so you ended up with an interactive list of results.
The ability with look@lan to connect into a client's network and quickly a list of everything reachable on the network was incredible. All the desktops, laptops, printers, etc. When I was doing WISP work, I could quickly see how many clients were online without logging into the far end (nowadays though, most WISPs will enable client isolation, but still good to see the APs and gateways).
Eventually look@lan was discontinued and then they released a tool called Fing, which also worked on mobile. But that turned into a subscription service. I did like the ability of fing to work from a phone, but the earlier Look@Lan was much more useful. I recently helped out a local non-profit who's network was all over the place, split up between two separate access points, each with their own subnet and they were having trouble reaching printers. Nmap helped out, but couldn't find a comparable tool to look@lan to help.
WatchYourLan looks like it will be a good substitute. I know it's primarily designed to run on one network and track changes to said network. And I will probably use it that way at home and a few other places (for the few customers I still maintain, if they permit, I will drop a small Pi/N100 box on their network for remote access and monitoring). But for dropping into a new ___location, I could see spinning this container up. I could do it in ephemeral mode or setup a data directory per "site" I visit.
There's a few tweaks I could see to make this more "mobile". such as adding a network or "site name" to the DB that you can config and filter on.
Another feature I'd be interested in would be fleshing out the port scanning a bit. Look@Lan and nmap scans for some common ports automatically. WatchYourLan has a port scanner, but you lose the information if you navigate away. At table for port scan results and an option to pre-scan specific ports. This would be good even for the permanent install - some might configure a set of default ports to scan on all the hosts in network, or they might customize for individual hosts.
But those are just my thoughts comparing it to tools I've used in the past. It's already a satisfying tool that's going to be added to my "toolbox". And since I also am a go dev, I might even be able to make some of those a reality.
> Also, the supply constraint seems to be the injector pens, not the drug itself. Personally, I think the scarcity is intentional, or we'd be getting this stuff in vials and using regular syringes. Unless I'm misinformed, I don't think there's any bottleneck in the manufacture of semaglutide itself.
Almost certainly the case. I get semaglutide in a monthly vial for $250/month (off insurance). They provide regular syringes & wipes, but also recommend you order some spare in case any of the needles break (they are super thin). I know someone else getting Wegovy on insurance, and it's all pre-drawn injectors.
> The starter doses are hard to find. The larger doses are not.
My friend's experience was the opposite. When she moved to the higher doses, CVS was often unable to get it in, and she's had to ask her provider put in orders for the lower doses a few times because that was what they could get. I don't know specifically what does she's on though (I swear she said 7.5 once, which is close to the 8 you mention).
> My friend's experience was the opposite. When she moved to the higher doses, CVS was often unable to get it in, and she's had to ask her provider put in orders for the lower doses a few times because that was what they could get. I don't know specifically what does she's on though (I swear she said 7.5 once, which is close to the 8 you mention).
Ah that's unfortunate. I guess I shouldn't have concluded my experience was true everywhere. My insurance (PPO from a tech co) doesn't cover Wegovy even with approval (my PPO from a prior tech co did), so my doctor suggested that since I'm going out of pocket and I'm not at the max dose, going with the Ozempic 8mg pens but dialing less than the max would let me stretch it out further. If she's on Wegovy and paying out of pocket, you might pass along this info regarding Ozempic. This assumes she's not at the max dose, though. If she is, it's not cheaper.
As others replied, compounding pharmacies. I'm using orderlymeds, but there's a number of different ones. There's no "generic" version of Wegovy, but compounding pharmacies can read the ingredients and make it themselves, at least while the FDA lists it as being in short supply.
You do need to research though (dropping two articles below). Orderly uses Hallandale pharmacy out of Florida., in fact a lot of the online clinics do. As an example, several clinics (such as Henry Meds) was selling "sodium semaglutide" (aka salt semaglutide) ordered through Hallandale that didn't really work for lots of people and there's lots of mix reviews based around that - not everyone was aware of what version they were getting. Also - not everyone is going to properly measure their dosage, which is why the pre-filled injectors the Novo brand provides is important.
You can't order from the pharmacy directly, you need to go through a clinic to get a prescription and have it ordered, but this is the price the clinics pay, before they add their services on top of it.
There's actually quite a collection of heated clothing, which is much easier to make. Milwaukee, Dewalt (and probably all the big power tool makers) make heated jackets and vests.
Datacenters I've been in that were built with "no raised floors" and flooding in mind do have a "raised floor", but it just happens to be solid concrete. This is very much the same as a warehouse or factory floor. It's built several feet higher than the surrounding parking lot, so that everything is level with loading docks.
If you're talking in-building flooding, not much going on there other than the racks themselves keep the equipment off the floor. All power is ran from overhead. A lot of modern "rack groups" (OCS, TSCIF, etc) have water limited water protection in mind.
But that was my "rubber duck debugging". Start by writing an email to to an imagined hostile support group. In the process of explaining the problem, it turns into a research project where I have to defend my claims. The sheer act of writing it out forces me to isolate the issue and keep troubleshooting. I can anticipate the bulk of the things they would have me try and I'd try them ahead of time.
People encountered similiar pushback with stack overflow, but I think the stack sites were much more lenient than some of those early mailing lists were.
reply