swalberg

Maybe we're thinking of different things, but isn't the backlog for Indian citizens caused by a fixed number of visas per year and per country caps? If you track the visa bulletin [0] they call out when a green card number is ready for your category, and India has its own set of dates because their country is so oversubscribed.

0 - https://travel.state.gov/content/travel/en/legal/visa-law0/v...

The Washington Post has written about this a fair bit, including an article from the editorial board. "washington post indian assassination" should give you some reading.

I have low expectation of airport food, too, but unless you get a direct flight at the right time you're going to find yourself needing to eat at an airport.

The section I was in had some automated sandwich kiosk and a burrito joint that had a huge line that wasn't moving. Walked to another section that had a Shake Shack and some kind of pizza place. Ordering at Shake Shack was fine but it took about 20 minutes to get my order. On the plus side there was an old guy who was also waiting and telling the dirtiest jokes to anyone that would listen.

Was just there at re:invent the other week, and I couldn't point to anything different about the airport WRT security and TSA. Very long lines, traffic in and out of the airport was _insane_. My last impressions of Vegas were the terrible traffic, long lines for a limited selection of airport food, but hey, if I wanted to play slots, there they were.

Yes, F1 had wrapped up the week ago, but it didn't seem like they were hurrying to take anything down.

Just bought a 2023 Forester, no problems yet but wondering if this problem is just for the Outback?

Yea, another good Scout knot. While a square knot can do the same it can capsize under tension!

Know knots or tie lots!

Knowing a few different knots for a variety of situations comes in handy. The right knot holds properly and can usually be undone when needed without having to cut it out.

If you're starting out then the square knot, two half hitches, taught line hitch, clove hitch, and bowline cover most use cases. And, yes, those are among the basic ones taught to Scouts.

There's already a category for that, the EB-5 investor visa.

If we understand the act of giving a green card to mean the US wants that person to join the society for the long term, is "taxes paid" really the best measure of desirability?

My issue with "H1B to the highest bidder" is that there's a lot of industries outside of tech that use H1Bs like healthcare, academia, skilled trades, or heck, even fashion models. I think something like that would have to be paired with quotas on the industry otherwise high tech salaries would blow away possibly-even-more-important healthcare and research spots.

As for #2, the main issue now is more of supply and demand. The US only gives out 140,000 employment based green cards a year (plus some from other unused categories), which also includes the worker's families. There are far more ways to get an employment based green card than through H1B. The problems we're hearing about are less to do with the process (which _is_ byzantine) and more to do with that there are not enough green cards to go around.

And just as an aside, there's no labor certification for an H1B, e.g. a company isn't saying they need that worker so so much. A company just wins the lottery and agrees to pay at least what the DoL says is the prevailing wage for the occupation. If they later want to get a green card for that employee, they have to redo the prevailing wage determination AND make an attempt to hire an citizen/GC before they can get the GC (or the employee has to prove they have exceptional skills that gains them international recognition, among other things which includes "being paid way more than your peers")

> you can apply for permanent residency while you have it.

Just to further complicate it, for many people _your employer_ has to apply for permanent residency on your behalf which is another 2 year ordeal and fair bit of money (that's just to get the green card priority date, not to mention waiting for the green card itself which varies by country). And that further indentures you since if you leave during that period you effectively abandon that application.

The site references the PDQ book and library. Dr. Gunther also wrote a book called Guerrilla Capacity Planning that goes into detail on the curve fitting method of analysis which is worth a read.

Both :) the standard unit Of time is a dit. A dah is 3 dits long. 1 dit between each element (so s is ... But 5 dits long because its on, space, on, space, on). 3 dits between letters. 7 dits between words.

When people make the dits too long or the dahs too short (c vs y), or run characters together (ee or i?), it gets hard to copy correctly.

> The stewardship claim bit seems maybe a bit overstated considering they weren't able to secure an object the size of a button leading to it "falling off the back of a truck"

As I understand it, this wasn't fuel, it was part of an instrument used by a mining company to measure the density of iron ore. The mining company (or a contractor depending on what you read) are the ones that lost it, the Australian government agency just came in to help find it.

RE "it's social", at least over on HF there are a lot of activities where the expectation is just a signal report and a thank you. In particular POTA/SOTA, DX'ing, contesting, and special event stations. And then there's FT8/FT4 where there's no way to have a conversation. But they're fun because it takes some skill, there's an element of chance, and there's usually some kind of goal (work 100 countries, all states, 500 parks, contact the battleship Iowa, etc)

My logbook has about 4500 QSOs and I'd be surprised if 25 of them got past the weather. But by the same token I've had some really interesting random encounters.

For me, getting my General (and then Extra) really made the hobby for me. I probably wouldn't be that into it if I was limited to talking with local people on the repeater.

Just for General. Technician changed last year.

I don't regret it. I've managed to make the time thing work, even writing a book when our first was still an infant. I've also had experiences I never otherwise would have had without kids. One of my sons wanted to learn to scuba dive so I did it with him. Also been on some cool adventures like canoeing in the boundary waters because my sons wanted to do it.

Yes, though it's not hard and fast. Many sites will teach the Koch method but often with subtly different ordering, and very different from his original ordering. CW Academy teaches based on how frequently you'll hear them on the air. Long Island CW Club has changed to another system.

Most systems these days though focus on learning a couple letters and then progressively adding more on as you improve.

Somewhat. There's a skill to the timing that needs to be picked up in addition to the patterns you learn when learning to copy. Ideally, you're also practicing sending with some kind of local oscillator or your radio set to monitor mode. One reinforces the other.

It is more power efficient than voice. You put the same power into roughly 50Hz of bandwidth vs 2.2k for voice, so you can work the world on a modest station. Its also easier to pick out in the noise than voice.

Amateur radio is more than just "have a conversation with a random person". There are contests, challenges where you try and contact some number of states, countries, etc, and events.

One popular event is Parks on the Air where people go to a designated park and set up a temporary station then try and make contacts. It has a sibling event called summits on the Air where you do the same thing on top of a summit. Using CW lets you do that with less gear and in more adverse conditions.

Finally, its a brain workout. If you like the feeling of being " in the zone" then getting into a Morse conversation or participating in a contest is just the ticket.

If you like documentaries about the space race, the Washington Post has a fantastic podcast series called "Moonrise" (https://www.washingtonpost.com/podcasts/).

I was wondering the same. The picture accompanying that text was a plate from a Vibroplex Bug, a semiautomatic telegraph key.

https://infostory.com/2013/08/27/debugging-the-origin-of-the... talks a bit more about the bug trap and the false signals.

I'll have to remember the "tie them in bed" thing. I tell scouts that their basic knots should be known "cold, wet, and blind" for the same reasons.

If we're doing knot relays, I'll also have them do it with gloves, or eyes closed, or tie the knot behind their back. Also gives a great sense of accomplishment when they finish.

I was canoeing in Minnesota two weeks ago as part of a Boy Scout camp and they offered a patch if we came back with several readings. The boys were interested and looked forward to taking the measurements.

Didn't realize the device was named after someone, we were told it was an acronym and the name morphed a bit to sound like a "sucky" disk.

You're not the only one. Minuet was what I used.

Only been a Ham for 2 years, but the etiquette I've observed falls along the lines of "don't do things that make it hard for other people to have fun". Like checking to see if the frequency is in use before sending, and not blasting out a wide signal when a narrow one will do. Respecting band plans, both formal and informal, especially digital people sticking around established watering holes and not splattering the CW areas. Don't tune up (sending a tone to configure your antenna tuner) on someone's frequency.

Another part is "let people do their thing". Like if someone's in a special activity and managing a pileup (lots of people trying to call), just give them the exchange and move on.

Due to the asymmetric nature of propagation, stuff happens. You may not hear anyone using the frequency but they hear you just fine. If band conditions take a turn for the worse, politely tell the other person you're losing them and thanks for the conversation.

Anonymity is banned; FCC part 97 says you have to use your call sign every 10 minutes and at the end of the transmission.

Ultimately the FCC is responsible for enforcing these but of course don't have the time. People can report people to the FCC and they _may_ open an investigation depending on that nature of it. There's also the ARRL volunteer monitoring program where participants listen on the air and, through the program, send out notices of good and bad behavior, optionally referring cases to the FCC. It's usually stuff like "guy constantly being a jackass on a repeater and ruining it for others", with a good bit of "sending outside your privileges" and "not identifying yourself".

That said we've all accidentally sent outside our privileges, we've all stepped on people. It happens.

As amateurs we know that if we don't do a good job of operating we'll lose the spectrum, so it's usually not a huge problem. There are jerks, there are also people that don't know they're being jerks.

I picked CW up as a pandemic thing and its a blast. Its probably the majority of my on air time now. Never would have thought, since Morse was originally what kept me from the hobby as a kid. Give it a go! 73 DE KN4ZMA

Posting because I saw that someone removed references to sexual assault as ways to remember the resistor color codes, and 2 minutes later it was reverted in the name of that being censorship.

For me the biggest problem with documentation has been keeping it up to date, aka "Documentation is a future lie". This seems to produce nice looking documentation but puts updating it in a separate workflow from changes in the code. Will it do anything to help people make sure that the contents stay relevant?

I brought Chef into the online side of the NFL several years ago. We still use it, though less and less as we get more things into containers. I've got my gripes with it, but I'd never second guess my decision to use Chef, or trade it for anything else.

Those problems sound like people aren't taking the same care in their cookbooks that they are in their regular software. If you write bad cookbooks and don't at least give a cursory review of the community cookbooks you use, you'll end up with a mess. If you treat it like the customer facing software it is, I find it a pleasure to work with.

Our cookbooks have CI pipelines that run some basic tests and we have automation around rolling out changes. We rely on a lot of conventions to avoid storing state, but we still have nodes auto provisioning their own storage and load balancers where necessary. It's let us stand up a ton of infrastructure and make changes safely and quickly. That's not to say we couldn't have made Puppet/Ansible/etc work, because IMHO it's more about your development practices than anything else.

edit: we only use Chef Infra and some Inspec. Not talking about Habitat.

Sorry, I don't have any specific places to recommend since it's going to be very regional and vertical specific. I don't know those two particular pieces of software, but try to sell yourself less as a "neoxam expert" and more "expert in solving the business problem that Neoxam does", and focus on your accomplishments there.

I have a dim view of any "best place to work" rankings ever since I worked at one and realized that people generally pay to be on those and the numbers are juiced when HR sends emails out suggesting everyone give the company a glowing review.

And don't forget to enjoy parenthood. There are hard times, and there are great times (often concurrently). You've got a limited amount of time to enjoy the experience and to guide them to be the people this world needs. Good luck!