HN user

throwiforgtnlzy

62 karma
Posts1
Comments73
View on HN

While I nuked my LinkedIn about 8 years ago because I was 1-2 from 96% of Silicon Valley and spammed by un-targeted recruiters incessantly... more importantly, my contacts and I didn't talk so keeping it was meaningless performative business theater.

MAANG companies (excluding N) are requiring relocation and RTO (hybrid, near an office). Also, their tone has shifted to where their recruiters feel like they hold a monopoly on in the business relationship power dynamic.

Perhaps shrinking corporate real estate holdings of properties and lease should be prioritized over burdening employees with additional relocation, commuting, and housing costs.

Around 1981-1985, smog was quite bad in the SF Bay Area. It was a horrible brown-yellow.

I don't think most people appreciate how far away it is to reach Mt. Hamilton or how precarious the road up it is. Took a couple of gfs on drives up there.

I used to bike up Hicks Road near Mt. Umunhum.

Other good vantage points: the top of The Dish route behind Stanford and the observation deck of the de Young Museum.

Yep. While startup salaries are, and have always been, a joke, it's corporate cost of living adjustments (COLAs) that are a worsening joke when they fail to account for true COL differences. If a megacorp insists on relocating you from Austin, TX to Menlo Park, CA it should include a 75% TC raise or it would be a pay cut and wouldn't make economic sense. It's imperative that rational employees hold corporations accountable and refuse to be underpaid because not doing so hurts everyone else in the industry.

Update for 2024:

Step 0. Don't bother with obsolete Cat 6 or lower cable because it's just not worth the effort over Wi-Fi. If you're going to do it, buy a 1000' spool of CMP Cat 8 UPoE-rated premise wire (~$1000-$1500 USD), punch down tool, J boxes, punch down receptacles, semi-flexible plenum large conduit that doesn't have ridges, cable fish tape, wall-mounted quarter 19" rack, 90 degree drill and hole saw with various lengths of extensions (usually from about 1' to 10' or longer for tall walls), and a punch down patch panel.

Step 1. Run conduit and J boxes first to a central closet or to a garage in most instances. This is the labor-intensive, hard part but it makes running multiple cables through it much easier. Larger homes may need a second closet or second conduit hub area and more conduit to a main patch panel.

Step 2. Easily slide wire in using a fish tape, 1 to 4 cables per box depending on the location. It's so much easier with semi-flexible conduit.

Step 3. Test each cable using iperf3 with an RPi and laptop, or borrow a commercial 10GbE cable tester like a DSX2-8000.

Step 4. Drop in a 10 GbE U/POE++ switch that doesn't sound like a jet engine.

Option: Instead of, or in addition to, Cat 8 wiring, run fiber.

A retail Windows license isn't the same as an enterprise Windows license. Retails Windows licenses started with ads for OneDrive and Office in Settings, but now that they're reverting to their old, shameless ways, they're putting ads everywhere else too for retail users.

With a Windows Enterprise license, all of the ads can be turned off, or at least that was the practice.

It depends. It's better than nothing that can be ^C'ed.

Here's a naive, partial implementation that runs in <500 ms so long as there's an existing dnf cache:

   command_not_found_handle() {
    local pkgs
    readarray pkgs < <(dnf rq --whatprovides "$1" -C --qf '%{name}\n' 2>/dev/null | sed '/^$/d' | sort -uVr)
    if (( ! "${#pkgs[@]}" )); then
      echo >&2 'Command not found and no package provides it according to the dnf cache'
      return
    fi
    echo >&2 'Command not found, but offered via the following command(s):'
    pkgs=("${pkgs[@]/#/    dnf install }")
    echo >&2 " ${pkgs[@]}"
  }

FYI: Meta is de-facto insisting on RTO and not offering a remote option for new employees.

This trend has nothing to do with productivity and is all about the egos of control-freak managers "maintaining control" over employees in a way that wastes employees' time and money and harms the company's reputation.

Platform-based, such as Squeak and Etoys (not eToys) or like with VMs such as JVM or BEAM.

The problem you describe is solved by introducing capabilities such as in seL4. Without beginning with a capability, something cannot do something else.

Yes, that would be a good idea™ but I don't think that's conflict. Apple had uses all sorts of excuses and technical limitations to prevent repairs including parts pairing.

The solution is there need to be parts available for reasonable prices in the first place. There are no reasonably priced parts for iPhone Pro 13 and onwards. My friend's cell phone repair chain has lost a lot of business because they can't fix many types of Google Pixel, Samsung, or Apple devices for reasonable prices.

DNS over Wikipedia 2 years ago

Begs the Q: Why is someone using Google when DDG and Startpage exist?

Can't someone !w piratebay and click the link?

Yes. 15+ year zsh user here. When dealing with bash, try to sneak in PackageKit-command-not-found and bash-completion.

And when running a shell, do it like this:

    docker run user/image:tag -it --rm bash -li
Also, zshdb, bashdb, and shellcheck are good stuff™ too.

My mantra is all programs and widely-used company tools should have current man pages and shell completions. The whole "Go look at a web page" for "help" is slow, distracting, and lazy.

While I don't use the ecosystem, I like the way Go approaches it with interfaces by being minimal, expressive, and flexible. It something works like something else according to a minimal specification, it's the same. There's no sealing off things or top-down mandates that require changes to other people's code. Rust traits aren't exactly the same because they require changes to everyone's code to follow an exact model that cannot be retrofitted to existing code without additional work. One downside (it may not be the case today) with the Go model is requiring a type to fulfill one or more interfaces requires additional hoops such as no-op init() interface assertions.

Alexa's platform is really, really bad in 4 dimensions: it's antiquated with limited fixed action patterns, it just doesn't work correctly, its skills aren't adequately maintained, and it's developer hostile.

On the first part, if a skill doesn't support a precise sentence structure, it becomes difficult to use or simply doesn't support features users expect to use using natural language.

On the second point, not all Alexa devices work with IPv6. I have an Echo Show 15 here that simply refuses to play BBC News and other "Flash Briefing" items when IPv6 is enabled. Really? It's 2024 now. Did the whole factory reset, reboot, and so forth dances.

An LLM startup with enough partner biz dev/sales talent could combine IoT API integrations from enough manufacturers to side-step the boring and limited Apple Siri, Google Hello, and Amazon Alexa oligopoly hegemonies and self-destructive platforms like IFTTT to execute on a compelling, competing replacement making good on all 4 points. However, I don't think giving away computing resources for free is necessarily a scalable business model but it's fair to charge a reasonable micropayment subscription to host and run your code and data.

Sorry, it's a been feature in a number of languages for decades. Perl has it at least as early as 5.005 in 1998. So naturally, Ruby had it since at least before 1.6 / 2002. Java added it in 2011. It didn't work with Python 2.1 from 2001, but I found it was added relatively late in PEP 515 in 2016 with Python 3.6.

As a latecomer, C23 went with ' just like C++ did almost 10 years earlier with C++14.

Tried crystal several times over the years. Each time, I encountered Crystal bugs, surprises, oddities, and missing pieces such that there was no viable path forward to adopt it for anything serious. Elixir + Rust with rustler is pretty compelling as a scalable, viable alternative.

* Unless they happen to be scholarship students. Scholarship students traditionally have to work harder than everyone else because they can't afford to buy homework or tests, or to pay people to take tests for them. One potential mark against them is the possibility of grade inflation endemic to the institution, but this maybe more or less variable in a particular STEM discipline.

Also, state research universities didn't/don't have as much grade inflation because they're intent on "competing" in the ranks without having the legacy, endowment, or name branding that Ivy's and Pac-NN's, so typically all they have (outside of NCAA sports $$$). University academic department staff are worried about bolstering their public image and of winning the approval of accreditation organizations.

Frame of reference: Most all of my college-prep public high school friends went to Harvard, MIT, Stanford, or CalTech while fewer, like me, went to University of California universities (UCs) like Berkeley or UC{LA,SD,SB,D}. I'm only certain of a few certain universities of that era were more or less more rigorous by comparing notes on specific courses and how team participation was regulated fairly or not. In 2001, we had a intro networking course requiring creating a forked caching HTTP/0.9-1.0 network web proxy server as one project of many.

Stanford, for many years, was allowed to run a similar brand of narrow width imported trucks that fit between bollards around campus because they are/were their own municipality (and own ZIP code) on their own property. As such, I don't think they had State of CA license plates, had to pass Smog Check emissions tests, or had any sort of formal homologation.

In general, accepting random vehicles without proper homologation review by the DOT is an unwise and dangerous process. On the other hand, small and limited use vehicles for explicit use not on public roadways should also be possible.

The US is a corrupt, dysfunctional civilization that won't even do anything to stop mass shootings, so it certainly won't stop speeding or ensure corners don't get cut in the design or manufacturing of passenger transportation machines. The authoritarian-inspired consequences you suggest won't be applied fairly or properly, a priori.