nkantar

While the sentiment of the piece—versatility > specialization—can certainly make sense, I can’t help but feel like it’s just a rant idealizing the type of person who invests significantly more than their workday into their craft, which I haven’t at all found to be much of a predictor of ability or even attitude. I know some great software engineers who do a ton of programming outside of work, and I know some great ones who do none.

> I don't want the GUI guys. I don't want the database guys. I don't want the middleware guys.

I don’t want a team of just a "guys", regardless of its and their abilities. Huge omission in a piece ultimately purporting to promote diversity (of thought).

> language specialist AKA snob

Those are two different things. I consider myself a Python specialist because I greatly enjoy working with the Python ecosystem (which is significantly broader than just the language itself) and thus prefer it whenever it’s a reasonable choice, but have also used other ecosystems and continue to do so, partly to learn.

That makes a lot of sense, actually.

Were download rankings combined with one-way "membership" considered? (One-way "membership": once a gem/user qualifies based on recent downloads, they're permanently required in perpetuity.)

This seems to be like it would mitigate the on/off problem of using a variable metric while also being biased to the currently relevant gems/users.

I’m guessing the parent was referencing Aaron Swartz: https://en.wikipedia.org/wiki/Aaron_Swartz

Firefox Focus has been a true revelation for me. I use it primarily as a content blocker in Firefox and Safari, but it's also a nifty way to have a quick private session with only one tab.

It doesn't do all the things, but still helps immensely.

https://www.mozilla.org/en-US/firefox/browsers/mobile/focus/

My use case is simpler than yours, as I only have one personal and one work Mac, so I can get away with a manually managed dotfiles repo[0]. My work GitHub account is a collaborator on the repo so I can edit config on both machines. The actual differences in configuration are intentionally minimal and kept in separate, unversioned, optional files. This repo is the only thing shared between my personal and work machines

[0]: https://github.com/nkantar/dotfiles

This looks fantastic. Working remotely since the start of the pandemic, these days I'd love a sustainable option like that for 3 hours at a time once or twice per week.

At first I thought it was a true static site generator, like mine: https://github.com/nkantar/sus

Interesting take!

Haha, thank you! I imagine a fair few people get it, but don't share the needs that motivated me to make and publish it.

I consider that a feature, not a bug!

Others may disagree, though. :D

Netlify redirects would work, but I wanted more portability. Hard to beat good ol' static HTML!

I'm guessing for things like package-lock.json.

Though it can certainly hide much more relevant-to-reviewers changes easily.

If you haven't seen the TV show _White Collar_, you might enjoy it.

But I somehow doubt that's the way things actually go. Given the quantities of dollars at stake, I imagine people tend to die in the process, and some of them are innocent bystanders.

sweetgreen (sweetgreen.com) | Data Engineers | Los Angeles, CA | Onsite

sweetgreen is a mission driven company looking to leverage technology to connect people with fresh, healthy food. We are currently undergoing a major technological transition to create a data-centric, technology enabled platform to accomplish our goals, and we could use some help!

We're looking for a core contributor on the data platform/infrastructure team to help evangelize data in the company by building software and creating new avenues for the rest of the company to access our data. We consider data to be our biggest asset to growth, and expect the company to heavily lean on our data platform to drive company direction and impact decision making.

We are an AWS shop, and our tech stack features a breadth of platforms that include Redshift, Spark, Kinesis, Snowflake, etc. We are big fans of AWS, and we sent one of our own to AWS Re:Invent in December to do a brief presentation of our S3 data lake topology!

Interested? Check out the link below! :)

https://grnh.se/89906e5d1

(I work on a sibling team to the one hiring, know the hiring manager well, and can share more if you're interested: nik.kantar [at] companydomain.)

Sweetgreen | Senior Data Engineer | Los Angeles, CA | Full-time, Onsite Preferred, but Open to Remote

Sweetgreen is a mission driven company looking to leverage technology to connect people with fresh, healthy food. We are currently undergoing a major technological transition to create a data-centric, technology enabled platform to accomplish our goals, and we could use some help!

We're looking for a core contributor on the data platform/infrastructure team to help evangelize data in the company by building software and creating new avenues for the rest of the company to access our data. We consider data to be our biggest asset to growth, and expect the company to heavily lean on our data platform to drive company direction and impact decision making.

We are an AWS shop, and our tech stack features a breadth of platforms that include Redshift, Spark, Kinesis, Snowflake, etc. We are big fans of AWS, and we'll be sending one of our own to AWS Re:Invent this December to do a brief presentation of our S3 data lake topology!

Interested? Check out the link below! :)

Apply here: https://boards.greenhouse.io/sweetgreen/jobs/1939889

I guess the split (on there, off home) would kinda work, but it seems like half measure when I already have a road bicycle for serious rides and a motorcycle to get around the city.

Here's a link for reference: https://goo.gl/maps/qTq3CfWFUrm (not my exact address, nearby intersection)

Having done that route in a car and on a motorcycle, I can say that Google is being a bit optimistic about the cooperation of traffic lights and the safety of traffic.

Sweating is the primary thing keeping me from riding to work. I solved that with a motorcycle, which does many things an eBike wouldn't.

Riding a purely-manual bicycle would be awesome because of the exercise, something an eBike wouldn't provide.

From my highly unscientific anecdata, that's been one of their primary use cases. The main problem I've heard reiterated is that they're not always readily available, suddenly turning a can-do trip into no-go.

This is pretty much spot on.

I live in LA and am an avid driver, motorcyclist, and bicyclist. I'm also a huge proponent of public transport, and use it whenever I can.

That last bit is often a bummer; it's very rare that I truly can use public transport to get to where I'm going.

The nearest train station is a 15-minute walk from my apartment. That gets me onto a pretty good train system that can take me to Santa Monica and Downtown Los Angeles on one train, but not many other places. Changing trains adds time, and then they also go to a limited number of places.

Buses are a bit all over the place, and victimized by the very traffic I try to avoid by using public transport.

My current office is about 9 miles from my apartment (Mar Vista to West Hollywood). This translates into 35 minutes by car, 20–25 minutes by motorcycle, and 1 hour and 20 minutes by public transit, involving at least two different methods. It would be a great 1-hour bicycle ride if I could shower at work.

I start a new job in a few weeks, and that office will be only 4 miles from my apartment. This should translate into 12 minutes by car, 10 minutes by motorcycle, and 40 minutes by public transit. It might also be a relatively sweat-free (low-sweat?) 25-minute bicycle ride.

Most people aren't as fortunate as I am.

I ride in LA and agree with you 100%. The whole city has become so much more accessible thanks to lane filtering and splitting since I started that it's hard to imagine giving it up.

I'm an avid driver who lives in LA (Westside), and this sounds pretty great, honestly. Driving in and through DTLA is a total nightmare, and public transit has a hard time covering enough of the relatively large area.

I love being able to take the Expo Line to LA Live, especially for the LA Auto Show (amusingly enough), and would welcome more of that.

What's the rationale?

I was thought quite the opposite for logos (re: colors): fewer colors is better, and the logo should be instantly recognizable in monochrome. It being something a layperson could draw reasonably well is also a good thing.

Edit: Did I just miss the sarcasm train here? It's very possible.

Thank you for the history lesson, that was thoroughly enjoyable! Bonus points for the comic book manual.

I haven't been paying any specific attention to F-35 news, but I can only ever recall reading negative press.

I know this particular project has been extra troubled, but is that the norm for new military vessels/vehicles?

I presume the commenter was asking the author of the project to fix a bug. While the submitter may not have actually been said author, it sure seems like a reasonable request.

And yes, perhaps asking the commenter to contribute is also reasonable, but the tone seems unnecessarily adversarial to me.

I used to feel this way, but then I discovered https://blog.github.com/ and no longer do.

Sure, they may not be addressing your/my specific concerns, but the product is changing.

I can see that, but I choose to remain unrealistically optimistic in the face of reality anyway. :D

There was a story somewhere (I can't find it now) about how a big part of the lack of car color options in the US is that consumers are used to buying cars directly off dealer lots.

According to the article, this makes the consumer into the customer of the dealer, and not the manufacturer. As such, the dealer is the manufacturer's true customer, and their demand is what drives production and availability.

The dealer, naturally, optimizes their inventory for the best sellers, which are generally grayscale colors, so that's what they order from the manufacturer. When the customer shows up, the limited choices often force compromises, which turn into statistics used to further optimize inventory.

The way out of this loop is for the customer to insist on the exact desired configuration.

The problem is that many (most?) people don't care enough to wait for three months instead of driving home in their new car the same day. This is further exacerbated by the dealer's willingness to offer a better deal on a car that's on the lot than one that has to be ordered.

I wouldn't be surprised if transmission availability plays into this to some extent, though probably not quite as much. After all, manuals are still generally cheaper in terms of MSRP, but dealer pricing may negate and even reverse that advantage.

"Better" is a tricky word.

I have no doubt PDK (and even far less sophisticated (semi-)automated transmissions) is _faster_ and less likely to make a mistake, but what if outright performance isn't the ultimate goal?

I had the pleasure of driving a 991.1 GT3 with PDK, and it was blisteringly fast (both the car and the transmission). But I was definitely more of a passenger than in my 2004 6-speed manual Miata, and the fact that I noticed that is pretty telling about my preferences.

In a multi-car garage I certainly wouldn't complain about a great (semi-)automated transmission in a daily driver (PDK, DSG, DCT, or even ZF's lauded 8-speed auto), but next to it would have to be a toy with a good manual.

Here's a fun short video about this: https://www.youtube.com/watch?v=oaUCdAdaaj8