text stringlengths 0 1.36k |
|---|
\[35:57\] If I were writing code every day, it would have definitely paid off within a few hours. I do think that even as more open source projects start adopting all this tooling, they become less new contribution-friendly, and I think that's the only problem I have with it. |
**Alex Sexton:** Yeah, I agree. I think it should be a goal of any popular project, or of any project, but it becomes a higher priority goal of any popular project to have a "Run these exact things and we promise it will work and you don't have to know about the build chain" and "Separate the concerns of building and a... |
I understand that in order to get it running on your machine, that kind of sucks, but the actual reading of the code shouldn't have necessarily been affected, other than you might see some type definitions here or there. Does that make sense? |
I feel like the "npm run configure" or whatever would be a really nice thing to maybe standardize or become more of a popular thing, to where it's like a one-click install type of things. But honestly, it really feels like npm install does most of that already. |
**Mikeal Rogers:** StandardJS does a very good job of this, right? You can run it as a command line thing, it just works; it just works in whatever linter that you're plugging it into... If you have some giant toolchain, you just kind of plug it into one of those places. It doesn't really have an opinion about how you ... |
**Juan Pablo Buritica:** I really like that one. |
**Alex Sexton:** That's Feross', right? |
**Mikeal Rogers:** Yeah. I wanted to come back to the thing you said about Create React App, and generally there is some kind of bootstrap Get Started thing. Every new framework and every new library, or every new big piece of software that comes out has one of these, and they tend to actually define the standard workf... |
There continues to be this argument, like every time that they put a new version of Create React App or something similar, people complain about the size of the dependencies that are included in it, and it ends up being this massive, massive dump of code... Which is always kind of hilarious to me, because I am one of t... |
**Alex Sexton:** So you just hate yourself... |
**Mikeal Rogers:** No, no... I don't complain about Create React App because I'm never gonna use Create React App, so I honestly don't care... So I don't understand the argument from that perspective, but we are getting to the point where these are getting huge. The baseline to set up is just enormous. |
**Alex Sexton:** Yeah... I think actually the Ember community nailed this before more or less anyone else with EmberCLI. EmberCLI is one of the best... Like, I did Ember before EmberCLI, and I did Ember after EmberCLI, and baking in EmberCLI is like an officially supported thing; the docs for Ember have EmberCLI usage ... |
**Juan Pablo Buritica:** \[40:13\] I'm with you with that, because EmberCLI is to me the de facto example of how these tools should work... But what I respect from EmberCLI is that they have a vision; they had a vision and they implemented across add-ons, across templates... All that stuff just works. But I've had the ... |
**Alex Sexton:** Yeah, the Create React App eject stuff I think is a good idea for those situations, to where you always a way of just busting out of the thing; it writes the configuration files that you already have and then says "You can figure it out from here." But that's when updates become hard. |
I think the thing that the Ember community accidentally really nailed is that the community bought into the tool, and since it's officially supported, when you write an add-on or when you write a third-party thing, it's your job to integrate it with EmberCLI rather than Create React App, which has to manage all of its ... |
All the docs for React are still just "Open this file. Write jsx directly in it and try to run in this way or that way", whereas the Ember docs say "npm install EmberCLI and then run these commands through EmberCLI". So I would love the React community to switch the docs to default to Create React App if it became an o... |
**Mikeal Rogers:** On that bit of advice, we're gonna take a quick break. When we come back we're gonna get into the project of the week. Stay tuned. |
**Break:** \[42:57\] |
**Mikeal Rogers:** Now we're gonna get into the project of the week. Since Juan's here, I wanted to continue to embarrass him and call him out a little bit... You wrote this great guide called The Collaboration Guide; it's on your GitHub. I wanna feature this as the project of the week because it's awesome. It's litera... |
**Juan Pablo Buritica:** Thank you... Now I'm blushing over here. |
**Mikeal Rogers:** \[laughs\] So why did you write this? |
**Juan Pablo Buritica:** It came from the real struggle that we were having at Ride, basically seeing the rest of the company try to adapt to the fact that engineering was completely distributed just motivated me to make sure... So these guides had to purposes. First, telling engineering how I expected them to communic... |
A lot of it is, of course, inspired by the open source way of working, but it was mostly to just define the culture of how we communicated, and it turned out pretty good. I've applied the majority of this stuff at Splice now, and it's worked really well. You'll probably see me every now and then tweet about "Please don... |
A few people have forked it, and actually I've seen some better or more thorough ones -- I forgot the one... I think it's LenaSun; she has a broader one that she did for her company. I'll find the link and I'll share it, but it was even more detailed than mine. It's pretty cool to just bring that and open it up and see... |
**Mikeal Rogers:** When I hear people talk about having remote people and remote teams, they tend to bring it up in this context of like "Oh, you can just hire these really good people that are somewhere else", and I've worked with a lot of companies that have done this and it hasn't worked out very well when they have... |
**Juan Pablo Buritica:** At Splice right now we have an engineering office in Santa Monica, California, and that's engineering only; that's where the CTO is - the CTO and founder, Matt Aimonetti is there. We have two QA engineers, two backend engineers and Matt. Then the rest of engineering is distributed between Latin... |
The reason why people think that being collocated is better is because we're just lazy around communication and being around people; everyone ends up finding out about this stuff that's going on in the company. But when you have one person out of the office and you're actually remote, you have to do a conscious effort ... |
\[48:16\] So I wanna keep that until we grow; right now we're 12 engineers... Probably around 20-25 I'd be open to having people in the office, but it's something that Matt and I are still trying to figure out, because we really like the distributed engineering culture and the vision of just letting people be adults an... |
If I ever - and of course I do wanna start adding more junior members - that will switch my approach, because then I'll probably have to instill some really solid support structures for entry-level positions and that will require having people in office, or at least very available for them... That will probably switch ... |
**Mikeal Rogers:** What are the key benefits of having a remote team? Do you think it adds a lot of more diligence in how you do communication and how you do the planning? |
**Alex Sexton:** Can I jump in on that? Because I have a strong opinion. As a remote employee for a large Silicon Valley company... |
**Mikeal Rogers:** That has a big office of engineers, right? |
**Alex Sexton:** Yeah, a ton... So I wanted to talk to you about not hiring people in New York for a little bit - that may be an extreme case, or whatever, but that's fine... Stripe I think has learned that you definitely don't wanna have one engineer who is remote on a team if you can help it. |
**Juan Pablo Buritica:** No. |
**Alex Sexton:** It's like a team of ten engineers, and one is remote - it's almost always gonna be a bad situation. |
**Mikeal Rogers:** Was that you for a while, though? |
**Alex Sexton:** Oh yeah, for sure. We were only 40 people, it was gonna happen. But there's some critical mass, and I think we actually have some percentage number - that I don't know, so I'm not gonna say one - of a team needing to be remote before the whole team acts in a way that is helpful for all remotes. But the... |
**Juan Pablo Buritica:** Right, it's math. It's just math. I like the exposure to cultural diversity as well, and also remote work enables people like single parents who probably just have to be next to their kids all the time... There is just a very different approach to distributed teams that I like, and I philosophi... |
**Mikeal Rogers:** This is actually a really good point. The more that you can break up a workload into asynchronous steps, rather than this synchronous working mode, the more flexibility people have in their schedule and the more kinds of people that you can get. There's a lot of people out there that just don't have ... |
\[52:04\] I've talked with the people from Free Code Camp about this, and how they've designed their learning curriculum so that you don't have to sit down or go into a bootcamp to learn it. It's really asynchronous, so that people who have kids, people that maybe already have jobs can follow up when they have time and... |
**Alex Sexton:** Big shocker, Mikeal's advocating for an asynchronous, non-blocking I/O for learning... \[laughter\] Mark it on the board! |
**Mikeal Rogers:** Oh my god... Yeah, and like me -- if you're working remotely, which I do, you should probably live in the most expensive place; that's a good idea, so that's what I do. |
**Juan Pablo Buritica:** Like downtown Manhattan, like I do. |
**Mikeal Rogers:** Yeah... Anyway, let's move on to picks. Time for picks! Juan, do you have something for us? |
**Juan Pablo Buritica:** I need five minutes. I am a procrastinator. |
**Alex Sexton:** I'll go first. |
**Mikeal Rogers:** Alright, go for it. |
**Alex Sexton:** I generally use maybe like a 1 mm pick, usually with like a grip, maybe like a good Dunlop... \[laughter\] My pick of this week is another specification, which is the CSS Grid specification. It recently went into production with Firefox 52, which was earlier this year (6-7th March). It was kind of the ... |
There are definitely the long tail of things that you could do with it that are very confusing, but the core use cases where you set up a grid, you literally just describe a grid in almost a grid format in the CSS, in order to explain the column and row layout that you want. So it's really powerful, but also really app... |
There's an old CSS-Tricks article that's pretty good on it, but there's also GridByExample.com, which is based on a book that Rachel Andrew wrote, and there's just a bunch of very simple examples of what the different parts of CSS Grid are and what the different words mean, which I assure you are much easier than the f... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.