cbzehner

I find Rust and Typescript have a lot of helpful surface similarities that make them an easy pair of languages to switch between.

The fundamentals are very different but it’s a case of convergent evolution - and I’m happy to liberally sprinkle clone’s around my rust code

I used Fish for several years before switching over to nushell a few weeks ago.

Nushell takes the ideas behind Fish even further by incorporating types other than strings and adding more built-in functionality that’s useful for your average command-line user.

I doubt I’ll go back but both are great! Highly recommend Fish and Nushell!

Incredible!

What was the hardest part?

What did you learn that you weren’t expecting?

"What I really need is a droid that understands the binary language of moisture vaporators."

"Vaporators? Sir, my first job was programming binary loadlifters—very similar to your vaporators in most respects."

―Owen Lars and C-3PO

Please do. This has been a consistent pain point in my Rust web dev experience and even seeing some examples of how others structure solutions really helps!

If this isn't an ironic commentary on current events...

200 OK { errors: “This way lies madness” }

My understanding was that darcs fixed the model but had fundamental performance problems at _some scale_. I think pijul took the same concepts and tried to streamline them. And this rewrite does that...again?

I moved back to Austin, Texas when this all started. Family, breakfast tacos and more living space were all factors.

You've just invented shipping containers.

tl;dr

Suggested alternatives to the terminology master-slave:

Primary-secondary, Leader-follower, Active-standby, Primary-replica, Writer-reader, Coordinator-worker, Parent-helper

Suggested alternatives to the terminology whitelist-blacklist:

Blocklist-allowlist, Block-permit

I worked at a company with an engineer who had a Perl script that prompted them to record what they were doing at random intervals through out the day.

When it came time for performance reviews, not only did it make for entertaining reading but it was easy to find all the small improvements they made that normally slip through the cracks.

Thanks for sharing what you've been building. Very cool!

For maintaining eye contact during video call we need to look at camera rather than screen.

I solve this problem in most meetings by positioning the main view as a smaller window directly under my webcam. This helps put my focal point close to the speaker from their perspective.

Seems similar in aim to Gitless

[0] https://gitless.com/

Even if the target market fails, they’ve got a fallback. These things are going to be on Hollywood sci-fi sets for years to come!

Just took a look at your landing page, cool idea -- one element of your service that really stood out was down at the bottom "Free concierge onboarding".

Really interesting offer. Do you find new subscribers take you up on this a lot? Seems like a great way to improve your migration tooling!

Although it's not a "codebase" per se, Architecture of OpenSource Applications is a great way to see how lots of major applications are structured. http://aosabook.org/en/index.html

What makes this approach "modern"? What is this approach the alternative to?

As someone broadly unfamiliar with text rendering it's not clear to me. An introduction to these points would be very helpful

I've been using Hasura for several months at work and it's approach to GraphQL has nailed the level of abstraction needed for early product development.

It's a great complement to serverless and static front-ends.

Check out https://breakoutlist.com/, it's designed for answering just that question - with a bias towards Silicon Valley hype.

If you're interested in Atrium, reach out to me (see profile). We're hiring!

I have had a couple colleagues out of bootcamp programs, they all had previous careers and decided to make the leap into software.

If they're motivated and okay with the fact that they're mostly likely going to be offered an entry-level position for their first year in the field it can definitely work out for them.

I haven't read this yet, but I plan on purchasing it and working through it this weekend or next. Robin's "Road to React" really helped me cement my understanding of React and learn how to use it in a concrete way. The focus on refactoring in his previous book has been immensely helpful in my day job.

Ex-Facebook. After five years I found my pace of learning had basically plateaued. Combine with organizational politics at any large company and I started looking for something smaller.

Ended up at Atrium, a legal startup in SF. Similar to mtlynch, I didn't expect how much I'd have to hone my front-end chops on leaving a FAANG.

Getting the opportunity to learn what I hadn't been learning and shore up those weaknesses reenforce my decision to switch.

Best parts so far:

* It's 30x smaller than FB was when I joined and 300x smaller than FB was when I left.

* Great people abound. I was worried that this wouldn't be the case at a smaller company but I joined partly on the basis of how intellectually curious the engineers I met were during my interview.

* It's a non-traditional tech company. We work with attorneys and build domain expertise in the problems CEOs and VCs face every day. The hard legal problems of starting a business.

If any of that sounds interesting, we're hiring! Reach out to username at gmail or https://www.atrium.co/careers#current-openings

Don’t forget, you only need one to land.

Remember someone is paying you for your time and skill right now! If you can let the rejections go, a hard thing, you’ll end up somewhere that’s a better fit.

I recently changed roles and it took a handful of onsites to catch my stride - more than six for sure! I only ended up with two offers but they were from my top two companies.

If you’d like feedback you’re welcome to reach out (username at gmail) and I’d also suggest doing a phone screen with Triplebyte, I was really surprised by how much constructive feedback they gave although that didn’t lead to my next job.

I think startups are behind BigCo on this. This is a recent change at places like Facebook.

I recently took a new job at a startup with a 1 year cliff and 10/20/30/40 vesting schedule, so there’s still a lot of variance in the market.

I switched to Dvorak in a weekend (~8 hours) using something like https://learn.dvorak.nl/

It took me about a month to get comfortable and stop making mistakes and I switched back and forth regularly for the first two years (working in IT).

Now I mostly use Dvorak and when I switch it's not a problem but my typing speed in Qwerty is about a third slower.

Having done it, I'm happy with it but I probably would have learned Colemak instead because it's closer to Qwerty and would make those infrequent switches easier.

You should look at the articles from First Round Review[0]. I haven't read any in a while but they tend to be high quality long form write-ups from successful execs. Similar to this piece.

[0] http://firstround.com/review/

This isn't true. Very few people are bad across the board -- find your strengths (as other commenters have said) and focus on those.

It's better to be excellent in one or two areas, especially ones your passionate about than solid across the board. If you suck at something and it's causing problems, that's a different story -- but don't get stuck on comparing yourself to others.

I wish I could downvote this comment. Please ignore it.

Mullvad (https://mullvad.net/en/) is the highest rated VPN service by That One Privacy Site[0] and it's pretty easy to use.

It's what I use, check it out!

[0] https://thatoneprivacysite.net/2017/10/03/mullvad-review/