I spent most of October tweeting bash comics, and I’m excited to announce that my “Bite Size Bash” zine is coming out on Wednesday!
here’s a thread with a little bit about why I wrote the zine…
I have a friend who’s a super accomplished senior engineer who mentioned once that they find working on bash scripts really scary and demoralizing.
so, why do really talented programmers struggle with bash?
some problems with bash:
1. It's a weird & counterintuitive language 2. you probably don't need to write it that often, so you don't practice 3. the times you DO need to use it, it's often because something important (like a build) broke and it needs to be fixed RIGHT NOW
but I spent a month thinking about what's actually required to write bash scripts, and it turns out that you only need to learn a few things to be confident with basic bash scripting
and most of the bash programs (like CI scripts) that you'll deal with in real life just are not that complex because (if we're honest) nobody really wants to be maintaining a complicated bash script anyway
here's the table of contents for "Bite Size Bash"! it's split into a "basics" section, which will help anyone who needs to deal with bash scripts, and a "getting fancy" section if you really want to become a bash wizard :)
you can sign up here to get an email when "bite size bash" comes out on wednesday, and get a discount that only people on my email list get ;) : wizardzines.com/zine-announcem…
• • •
Missing some Tweet in this thread? You can try to
force a refresh
- at least in firefox, <input> & <button> are inline-block by default, not inline
- the width on a block element defaults to auto, not 100% (though it will often look like it's 100%)
- you can set the width on an inline element if it's a "replaced" element
this "replaced element" thing is really confusing (developer.mozilla.org/en-US/docs/Web…). I did some tests and it seems like in Firefox a textarea is `display: inline` by default, but it's a "replaced element" so you can still set the width in CSS
an important thing to me about my zine business is that 100% of the revenue comes from people buying zines.
I get asked all the time to write sponsored zines ("hey, could you write a zine about our product") and I always say no -- readers are the customer, not the product.
(which is not to say that sponsorships are bad! Lots of really good education work gets funded through sponsorships. I help organize a conference that we fund largely through sponsorships. It's just not what I do with my zines.)
also please don't reply to this with explanations of other ways I could take money from sponsors. Selling zines to people who want to know stuff is actually a really good business! I don't need extra sponsor income.
a big thing I try to do with my zines is stick to fundamentals: things that haven't changed much in the last 10 years and that probably won't change much in the next 10 either
one thing I think is unfortunate about programming culture is that "knowing fundamentals is really helpful!" can sometimes turn really gatekeeper-y ("oh, you don't know how THING works? WELL YOU SHOULD!! IF YOU DON'T YOU AREN'T A REAL PROGRAMMER"). it's so unnecessary to do that!
the thing is that it's SO NORMAL to make it 5 or 10 or 15 years in your programming career without learning something that seems "basic" about how a computer thing works. And it's both: 1. good to learn some of these "basic" things 2. totally okay to not have learned it yet!
some more facts about speaking at !!Con (May 9-10 in NYC)
- $256 honorarium
- we can pay for your travel if your employer won't
- all proposals are anonymous
- we often accept talks from first-time speakers
- the deadline to submit is March 1 :D
I'd especially love a talk submission from you if any of these are true:
- you find that people like you are underrepresented at conferences
- you've never given a talk before
- we've rejected a talk submission from you before.