aturek

Link for anyone looking for it

https://somehowmanage.com/2020/09/20/revenue-model-not-cultu...

I've learned about several frameworks that are system language + web frontend. The general approach is, ship a small binary compiled for the specific platform, and use the platform's native browser (and whatever html frontend tech you like) for frontend. The whole binary can be 1mb or less.

There's a couple of Rust libraries like this; right now I'm building an app in Tauri+Svelte.

It looks like Wails might be a similar framework in Golang.

I also prefer simple web tech, but I'm really glad you brought these points up! Ecosystems matter more than a lot of purist devs think.

Brightscript could have been worse!

And much, much better, as well

Do they just get paid out with restrictive NDAs?

Yes, that's a very common part of an exit package for executives. Speaking from some first- and second-hand experience, you can get paid a hefty sum (6-12mo of salary worth of cash) for signing an agreement that has some amount of limits on what you can say, to whom.

There's also some kind of what I think of as a LinkedIn effect - there's a disincentive to talk trash about any organization publicly, since that's now attached to your name and might make future employers/organizations leery of hiring someone who might air their dirty laundry.

From TFA:

Many CTOs, like me, have a strong engineering background, and so I will understand some of the requests you make without needing further explanation.

I see relative times (7:00pm, 12:01am, etc), but I notice there are no timezones. Is it implicitly Eastern time in the US?

In answer to (1) - I'm a bit rusty, but I believe Java allows objects of the same type to access other objects' private data. I definitely agree that it's gross, but it exists elsewhere.

Convoy | Software Engineer | Seattle | Full-time, onsite, https://convoy.com

We're optimizing trucking and logistics, an $800B industry that still runs on fax machines and phone calls. Currently backed by top tier investors. Read about us:

http://seattlebusinessmag.com/technology/convoy%E2%80%99s-de...

https://www.geekwire.com/2016/greylock-leads-16m-round-deman...

I'm employee #2, and I've been here since we were borrowing desks at a local startup incubator. We've grown a lot since then, but we still have a tight-knit, incredibly high-leverage group of engineers. Even after two years, I still love going to the office each morning. I get to work with the smartest folks I've ever met, on software that is going to modernize an industry that's fundamental to the modern world. No team I've ever been on, including at Amazon, has felt like I could have this kind of impact.

We would love more engineers, up and down the stack, and anywhere on the generalist <-> specialist spectrum. We use pretty cutting-edge tech (React, React-Native for mobile, TypeScript + Node for backend), but we're a lot more interested in engineering chops than any particular tech skills.

If you're interested in hearing more, reach out and grab coffee with me or one of our other developers. Help us grow an amazing tech team from a very early point in our company's history!

Some, but not necessarily all, of our open jobs: http://jobs.convoy.com

Whoops! email: alex@convoy.com

Convoy | Software Engineer | Seattle | Full-time, onsite, https://convoy.com

We're optimizing the trucking and logistics industry; automating what is, today, a $800B industry that still runs on fax machines and phone calls. Currently backed by top tier investors. Read about us: https://news.greylock.com/our-investment-in-convoy-changing-...

I'm employee #2, and I've been here since we were borrowing desks at a local startup incubator. We've grown a lot since then, but we still have a tight-knit, incredibly high-leverage group of engineers. Even after two years, I still love going to the office each morning. I get to work with the smartest folks I've ever met, on software that is going to modernize an industry that's fundamental to the modern world. No team I've ever been on, including at Amazon, has felt like I could have this kind of impact.

We would love more engineers, up and down the stack, and anywhere on the generalist <-> specialist spectrum. We use pretty cutting-edge tech (React, React-Native for mobile, TypeScript + Node for backend), but we're a lot more interested in engineering chops than any particular tech skills.

If you're in Seattle, in tech, and interested in the business, reach out and grab coffee with me or one of our other developers. Help us grow an amazing tech team from a very early point in our company's history!

Some, but not necessarily all, of our open jobs: http://jobs.convoy.com

Convoy | Software Engineer | Seattle | Full-time, onsite, https://convoy.com

We're optimizing the trucking and logistics industry; automating what is, today, a $800B industry that still runs on fax machines and phone calls. Currently backed by top tier investors. Read about us:

https://news.greylock.com/our-investment-in-convoy-changing-...

I'm employee #2, and I've been here since we were borrowing desks at a local startup incubator. We've grown a lot since then, but we still have a tight-knit, incredibly high-leverage engineering team. Even after two years, I still love going to the office each morning. I get to work with the smartest folks I've ever met, on software that is going to modernize a fundamental industry. No company I've ever been at, including Amazon, has felt like I could have this kind of impact.

We would love more engineers, up and down the stack, and anywhere on the generalist <-> specialist spectrum. We use pretty cutting-edge tech (React, React-Native for mobile, TypeScript + Node for backend), but we're a lot more interested in engineering chops than any particular tech skills.

If you're in Seattle, reach out and grab coffee with me or one of our other developers. This job’s been a wild ride, and it’s really only beginning!

Some, but not necessarily all, of our open jobs: http://jobs.convoy.com

Convoy | https://convoy.com | Software Engineer | Seattle | Full-time, onsite

We're optimizing the trucking and logistics industry; automating what is, today, a $749B industry that still runs on fax machines and phone calls. Currently backed by top tier investors. Read about us: http://fortune.com/2015/10/27/superstar-investors-back-convo....

I'm employee #2, and I've been here since we were borrowing desks at a local startup incubator. We've grown a lot since then, but we still have a tight-knit, high leverage engineering team. I love arriving at the office in the morning - I get to work with the smartest folks I've ever met. No company I've ever been at, including Amazon, has felt like this much potential for impact.

We would love more engineers, up and down the stack, and anywhere on the generalist <-> specialist spectrum. We use pretty cutting-edge tech (React, React-Native for mobile, TypeScript + Node for backend), but we're a lot more interested in engineering chops than any particular tech skills.

If you're in Seattle, reach out and grab coffee with me or one of our other developers. The last 18 months have been a wild ride, but we have years and years ahead of us to build a logistics titan!

Some, but not necessarily all, of our open jobs: http://jobs.convoy.com

What's the best one you've seen?

Convoy | Software Engineer | Seattle | https://convoy.com/

We're optimizing the trucking and logistics industry; automating what is, today, a $749B industry that still runs on fax machines and phone calls. Currently backed by top tier investors. Read about us: http://fortune.com/2015/10/27/superstar-investors-back-convo...

I'm employee #2, and I've been here since we were borrowing desks at a local startup incubator. We've grown a lot since then, but we still have a tight-knit, high leverage engineering team. I love arriving at the office in the morning - I get to work with the smartest folks I've ever met. No company I've ever been at, including Amazon, has felt like this much potential for impact.

We would love more engineers, up and down the stack, and anywhere on the generalist <-> specialist spectrum. We use pretty cutting-edge tech (React, React-Native for mobile, TypeScript + Node for backend), but we're a lot more interested in engineering chops than any particular tech skills.

If you're in Seattle, reach out and grab coffee with me or one of our other engineers. The last 18 months have been a wild ride, but we have years and years ahead of us to build a logistics titan!

Some, but not necessarily all, of our open jobs: http://jobs.convoy.com

I don't agree. I've seen some very junior people change their attitudes rapidly (for the better) when working on a team; if we wrote them off immediately we'd lose out on a lot of promising people.

I was also one of those developers and have since changed my ways :)

Better link with a more up-to-date list: http://jobs.convoy.com

Convoy | Seattle | Onsite | Full-time

We're optimizing the trucking and logistics industry; automating what is, today, a $749B industry that still runs on fax machines and phone calls. Currently backed by top tier investors. Read about us: http://fortune.com/2015/10/27/superstar-investors-back-convo...

I'm employee #2, and I've been here since we were borrowing desks at a local startup incubator. We've grown a lot since then, but we still have a tight-knit, high leverage engineering team. I love arriving at the office in the morning - I get to work with some of the smartest folks I've ever met, and not just in engineering. We also have a fantastic sales/operations/brokerage team, and we work with them constantly to build best-of-breed logistics automation.

We would love more engineers, up and down the stack, and anywhere on the generalist <-> specialist spectrum. We use pretty cutting-edge tech (React, React-Native for mobile, TypeScript + Node for backend), but we're a lot more interested in engineering chops than any particular tech skills.

If you're in Seattle, reach out and grab coffee with me or one of our other engineers. The last 18 months have been a wild ride, but we have years and years ahead of us to build a logistics titan!

All our open jobs: https://convoy.com/about.html#jobs

I'd love to hear how Github is doing ACL here. We came up with a pretty neat solution on my team, which we have not yet open-sourced, for JS. But it was a lot of first-principles design work; there don't seem to be any good examples.

This was pretty much all the documentation we had, and it's more a design analysis of edge-vs-node authorization: https://medium.com/apollo-stack/auth-in-graphql-part-2-c6441...

Edit: Our eventual solution looked a lot like

    class SomeTypeOfResolver {
      @allowIfAny(rule1, rule2, rule3)
      someProperty;

      @allowIfAll(rule4, rule5)
      otherProperty = defineRetrieverFunction();
    }

There's a lot more to a company than what it sells. Saying "I want to work here" without knowing the people there, for me, would be a non-starter.

What you're recommending (doing the background research on companies) is useful, but the worst jobs I've had have been the ones where I didn't do a good job interviewing my coworkers, and was just excited about the product, or the theoretical culture.

Great reminder to cull the backlog of my personal todo list!

Convoy

Software Engineers / Designers / Sales / Operations

Downtown Seattle, WA

We're optimizing the trucking and logistics industry; automating what is, today, a $749B industry that still relies on phone calls and paper.

Some of our open engineering positions:

- Front-end engineer - Live and breathe JavaScript, HTML, and CSS? Come work on our single-page app using React and redux!

- Mobile engineer - We have Android and iOS apps, and we’re interested in people competent in either native or react-native mobile development (both is a huge plus). These are beautiful, bulletproof apps that solve real-world problems for truck drivers and carriers.

- Back-end engineer - We’ve got some fun CS problems to solve around route optimization and market making, plus working on the API that connects all these clients.

If you’re a high-performing engineer but don’t have one of these specific tools on your belt, we’d still love to talk. We trust awesome people to learn the tech!

We're a small, close-knit team that hails from both startups and large tech companies, backed by some big names. Jeff Bezos, Pierre Omidyar and Drew Houston are all investors.

I'm one of our full-stack software engineers (employee #2). I've worked at several software companies large and small, but this one feels like a rocket ship. I'm working with some of the smartest people I've ever met, both engineering and business, we're building a great product at an incredible pace, and growing our business like crazy. I'm excited to go to work every day.

We just exited stealth mode a month ago:

http://fortune.com/2015/10/27/superstar-investors-back-convo...

If you're in Seattle (or willing to relocate) and looking to be on a small team where you can have a huge impact, email me at alex@convoy.com or check out our jobs page https://convoy.com/about.html#jobs

In case anyone else is puzzled: DALY = "Disability-adjuseted life year", i.e. a year you're alive and not disabled.

At my company, over the last 6 months we've tried Trello, Pivotal, and Sprintly. At past companies I've used Trac, Jira, and Asana. And for the last 7 years I've kept a daily todo.txt, where I append today's date and the 1-2 things I want to try to get done, adding detail as I figure out plans. (This is the only task tracking tool I've recommended that coworkers adopt and are actually using years later)

I've come to conclude that no tool for this will ever satisfy everybody's needs perfectly. Part of that is that everyone has different priorities for their task tracking tool. And frankly, some of those priorities are directly contradictory. What's trackable and detailed to a project manager who lives in the task tracker is heavyweight and clunky to an engineer who sees it as a bookkeeping annoyance. My personal todo.txt is exactly me-focused and only changes when I want it to, but it scales to exactly one engineer.

I think you just have to pick something and use it. Changing tools just adds friction and costs you familiarity. Ideally, the people who have to interact with it the most choose the best tool for them.

What's an example of something you suddenly understood?

I think people, including Amazon employees, try to put things down to some difference between AWS and retail. With the amount of cross-pollination between those two giant sides of Amazon, I doubt there's any significant macro difference in culture.

I know people who have been dissatisfied on both sides.

I worked at Amazon for three years, 2010-2013. My experience was better than most of my coworkers', but I watched a lot of people including some friends go through exactly what is described in the NYTimes article. There's an old team that I'll see about once a year at somebody's house. People tell me that our conversations sound like we all have PTSD from our time there.

I have a friend still at Amazon, on a particular Kindle team. I got him an interview there, and felt a lot of guilt about that for awhile. I've been relieved (and quite surprised) that he's still happy there; the team he describes is quite different from any team I worked on or saw first-hand.

You can find a place in the company that isn't totally insane. But most of the many Amazon folks I keep in contact with are either looking outside for different jobs, or switching teams rapidly to try to find something better.

My wife ran a food cart for ~18 months in Seattle. There are a lot of regulations around where you can set up food carts/trucks; most people end up renting spots (for ~$100/day near Amazon) or buying a license for a specific street spot from the city for ~$1100/year.

You consider "not maintainable" to be an acceptable downside to _anything_ you're doing with your software? What?

This is a great rule of thumb for employees and managers both: neither side should ever be too surprised. Whether it's performance evaluations or firing/quitting decisions, let the other side know if you're unhappy, and talk about it regularly (at least, one-on-one). Every time I haven't talked to managers about this sort of thing, I've regretted it.

If you're leaving a company, you might not have told the manager that you were interviewing around, but you certainly should have talked to them about being unhappy.

If you're firing an employee, they should have known (almost as long as you've known) that there was some culture mismatch, or that their performance wasn't meeting expectations, or whatever.

There are of course always exceptions, where you think someone is crazy or an asshole, but most people are reasonable and can handle hearing that things aren't great.