mirror of
https://github.com/LCTT/TranslateProject.git
synced 2024-12-26 21:30:55 +08:00
清除过期文章
This commit is contained in:
Xingyu Wang
parent
86311241a4
commit
f90610c528
@ -1,57 +0,0 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: ( )
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (Dell EMC updates PowerMax storage systems)
|
||||
[#]: via: (https://www.networkworld.com/article/3438325/dell-emc-updates-powermax-storage-systems.html)
|
||||
[#]: author: (Andy Patrizio https://www.networkworld.com/author/Andy-Patrizio/)
|
||||
|
||||
Dell EMC updates PowerMax storage systems
|
||||
======
|
||||
Dell EMC's new PowerMax enterprise storage systems add support for Intel Optane drives and NVMe over Fabric.
|
||||
Getty Images/Dell EMC
|
||||
|
||||
Dell EMC has updated its PowerMax line of enterprise storage systems to offer Intel’s Optane persistent storage and NVMe-over-Fabric, both of which will give the PowerMax a big boost in performance.
|
||||
|
||||
Last year, Dell launched the PowerMax line with high-performance storage, specifically targeting industries that need very low latency and high resiliency, such as banking, healthcare, and cloud service providers.
|
||||
|
||||
The company claims the new PowerMax is the first-to-market with dual port Intel Optane SSDs and the use of storage-class memory (SCM) as persistent storage. The Optane is a new type of non-volatile storage that sits between SSDs and memory. It has the persistence of a SSD but almost the speed of a DRAM. Optane storage also has a ridiculous price tag. For example, a 512 GB stick costs nearly $8,000.
|
||||
|
||||
**[ Read also: [Mass data fragmentation requires a storage rethink][1] | Get regularly scheduled insights: [Sign up for Network World newsletters][2] ]**
|
||||
|
||||
The other big change is support for NVMe-oF, which allows SSDs to talk directly to each other via Fibre Channel rather than making multiple hops through the network. PowerMax already supports NVMe SSDs, but this update adds end-to-end NVMe support.
|
||||
|
||||
The coupling of NVMe and Intel Optane on dual port gives the new PowerMax systems up to 15 million IOPS, a 50% improvement over the previous generation released just one year ago, with up to 50% better response times and twice the bandwidth. Response time is under 100 microseconds.
|
||||
|
||||
In addition, the new Dell EMC PowerMax systems are validated for Dell Technologies Cloud, an architecture designed to bridge multi-cloud deployments. Dell offers connections between private clouds and Amazon Web Services (AWS), Microsoft Azure, and Google Cloud.
|
||||
|
||||
PowerMax comes with a built-in machine learning engine for predictive analytics and pattern recognition to automatically place data on the correct media type, SCM or Flash, based on its I/O profile. PowerMax analyzes and forecasts 40 million data sets in real time, driving 6 billion decisions per day.
|
||||
|
||||
It also has several important software integrations. The first is VMware’s vRealize Orchestrator (vRO) plug-in, which allows customers to develop end-to-end automation routines, including provisioning, data protection, and host operations.
|
||||
|
||||
Second, it has pre-built Red Hat Ansible modules to allow customers to create Playbooks for storage provisioning, snapshots, and data management workflows for consistent and automated operations. These modules are available on GitHub now.
|
||||
|
||||
Finally, there is a container storage interface (CSI) plugin that provisions and manages storage for workloads running on Kubernetes. The CSI plugin, available now on GitHub, extends PowerMax's performance and data services to a growing number of applications built on a micro-services-based architecture.
|
||||
|
||||
The new PowerMax systems and PowerBricks will be available Monday, Sept.16.
|
||||
|
||||
Join the Network World communities on [Facebook][3] and [LinkedIn][4] to comment on topics that are top of mind.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://www.networkworld.com/article/3438325/dell-emc-updates-powermax-storage-systems.html
|
||||
|
||||
作者：[Andy Patrizio][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://www.networkworld.com/author/Andy-Patrizio/
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://www.networkworld.com/article/3323580/mass-data-fragmentation-requires-a-storage-rethink.html
|
||||
[2]: https://www.networkworld.com/newsletters/signup.html
|
||||
[3]: https://www.facebook.com/NetworkWorld/
|
||||
[4]: https://www.linkedin.com/company/network-world
|
||||
@ -1,173 +0,0 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: ( )
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (2018: Year in review)
|
||||
[#]: via: (https://jvns.ca/blog/2018/12/23/2018--year-in-review/)
|
||||
[#]: author: (Julia Evans https://jvns.ca/)
|
||||
|
||||
2018: Year in review
|
||||
======
|
||||
|
||||
I wrote these in [2015][1] and [2016][2] and [2017][3] and it’s always interesting to look back at them, so here’s a summary of what went on in my side projects in 2018.
|
||||
|
||||
### ruby profiler!
|
||||
|
||||
At the beginning of this year I wrote [rbspy][4] (docs: <https://rbspy.github.io/>). It inspired a Python version called [py-spy][5] and a PHP profiler called [phpspy][6], both of which are excellent. I think py-spy in particular is [probably _better_][7] than rbspy which makes me really happy.
|
||||
|
||||
Writing a program that does something innovative (`top` for your Ruby program’s functions!) and inspiring other people to make amazing new tools is something I’m really proud of.
|
||||
|
||||
### started a side business!
|
||||
|
||||
A very surprising thing that happened in 2018 is that I started a business! This is the website: <https://wizardzines.com/>, and I sell programming zines.
|
||||
|
||||
It’s been astonishingly successful (it definitely made me enough money that I could have lived on just the revenue from the business this year), and I’m really grateful to everyone’s who’s supported that work. I hope the zines have helped you. I always thought that it was impossible to make anywhere near as much money teaching people useful things as I can as a software developer, and now I think that’s not true. I don’t think that I’d _want_ to make that switch (I like working as a programmer!), but now I actually think that if I was serious about it and was interested in working on my business skills, I could probably make it work.
|
||||
|
||||
I don’t really know what’s next, but I plan to write at least one zine next year. I learned a few things about business this year, mainly from:
|
||||
|
||||
* [stephanie hurlburt’s twitter][8]
|
||||
* [amy hoy][9]
|
||||
* the book [growing a business by paul hawken][10]
|
||||
* seeing what joel hooks is doing with [egghead.io][11]
|
||||
* a little from [indie hackers][12]
|
||||
|
||||
|
||||
|
||||
I used to think that sales / marketing had to be gross, but reading some of these business books made me think that it’s actually possible to run a business by being honest & just building good things.
|
||||
|
||||
### work!
|
||||
|
||||
this is mostly about side projects, but a few things about work:
|
||||
|
||||
* I still have the same manager ([jay][13]). He’s been really great to work with. The [help! i have a manager!][14] zine is secretly largely things I learned from working with him.
|
||||
* my team made some big networking infrastructure changes and it went pretty well. I learned a lot about proxies/TLS and a little bit about C++.
|
||||
* I mentored another intern, and the intern I mentored last year joined us full time!
|
||||
|
||||
|
||||
|
||||
When I go back to work I’m going to switch to working on something COMPLETELY DIFFERENT (writing code that sends messages to banks!) for 3 months. It’s a lot closer to the company’s core business, and I think it’ll be neat to learn more about how financial infastracture works.
|
||||
|
||||
I struggled a bit with understanding/defining my job this year. I wrote [What’s a senior engineer’s job?][15] about that, but I have not yet reached enlightenment.
|
||||
|
||||
### talks!
|
||||
|
||||
I gave 4 talks in 2018:
|
||||
|
||||
* [So you want to be a wizard][16] at StarCon
|
||||
* [Building a Ruby profiler][17] at the Recurse Center’s localhost series
|
||||
* [Build Impossible Programs][18] in May at Deconstruct.
|
||||
* [High Reliability Infrastructure Migrations][19] at Kubecon. I’m pretty happy about this talk because I’ve wanted to give a good talk about what I do at work for a long time and I think I finally succeeded. Previously when I gave talks about my work I think I fell into the trap of just describing what we do (“we do X Y Z” … “okay, so what?“). With this one, I think I was able to actually say things that were useful to other people.
|
||||
|
||||
|
||||
|
||||
In past years I’ve mostly given talks which can mostly be summarized “here are some cool tools” and “here is how to learn hard things”. This year I changed focus to giving talks about the actual work I do – there were two talks about building a Ruby profiler, and one about what I do at work (I spend a lot of time on infrastructure migrations!)
|
||||
|
||||
I’m not sure whether if I’ll give any talks in 2019. I travelled more than I wanted to in 2018, and to stay sane I ended up having to cancel on a talk I was planning to give with relatively short notice which wasn’t good.
|
||||
|
||||
### podcasts!
|
||||
|
||||
I also experimented a bit with a new format: the podcast! These were basically all really fun! They don’t take that long (about 2 hours total?).
|
||||
|
||||
* [Software Engineering Daily][20], on rbspy and how to use a profiler
|
||||
* [FLOSS weekly][21], again about rbspy. They told me I’m the guest that asked _them_ the most questions, which I took as a compliment :)
|
||||
* [CodeNewbie][22] on computer networking & how the Internet works
|
||||
* [Hanselminutes with Scott Hanselman][23] on writing zines / teaching / learning
|
||||
* [egghead.io][24], on making zines & running a business
|
||||
|
||||
|
||||
|
||||
what I learned about doing podcasts:
|
||||
|
||||
* It’s really important to give the hosts a list of good questions to ask, and to be prepared to give good answers to those questions! I’m not a super polished podcast guest.
|
||||
* you need a good microphone. At least one of these people told me I actually couldn’t be on their podcast unless I had a good enough microphone, so I bought a [medium fancy microphone][25]. It wasn’t too expensive and it’s nice to have a better quality microphone! Maybe I will use it more to record audio/video at some point!
|
||||
|
||||
|
||||
|
||||
### !!Con
|
||||
|
||||
I co-organized [!!Con][26] for the 4th time – I ran sponsorships. It’s always such a delight and the speakers are so great.
|
||||
|
||||
!!Con is expanding [to the west coast in 2019][27] – I’m not directly involved with that but it’s going to be amazing.
|
||||
|
||||
### blog posts!
|
||||
|
||||
I apparently wrote 54 blog posts in 2018. A couple of my favourites are [What’s a senior engineer’s job?][15] , [How to teach yourself hard things][28], and [batch editing files with ed][29].
|
||||
|
||||
There were basically 4 themes in blogging for 2018:
|
||||
|
||||
* progress on the rbspy project while I was working on it ([this category][30])
|
||||
* computer networking / infrastructure engineering (basically all I did at work this year was networking, though I didn’t write about it as much as I might have)
|
||||
* musings about zines / business / developer education, for instance [why sell zines?][31] and [who pays to educate developers?][32]
|
||||
* a few of the usual “how do you learn things” / “how do you succeed at your job” posts as I figure things about about that, for instance [working remotely, 4 years in][33]
|
||||
|
||||
|
||||
|
||||
### a tiny inclusion project: a guide to performance reviews
|
||||
|
||||
[Last year][3] in addition to my actual job, I did a couple of projects at work towards helping make sure the performance/promotion process works well for folks – i collaborated with the amazing [karla][34] on the idea of a “brag document”, and redid our engineering levels.
|
||||
|
||||
This year, in the same vein, I wrote a document called the “Unofficial guide to the performance reviews”. A lot of folks said it helped them but probably it’s too early to celebrate. I think explaining to folks how the performance review process actually works and how to approach it is really valuable and I might try to publish a more general version here at some point.
|
||||
|
||||
I like that I work at a place where it’s possible/encouraged to do projects like this. I spend a relatively small amount of time on them (maybe I spent 15 hours on this one?) but it feels good to be able to make tiny steps towards building a better workplace from time to time. It’s really hard to judge the results though!
|
||||
|
||||
### conclusions?
|
||||
|
||||
some things that worked in 2018:
|
||||
|
||||
* setting [boundaries][15] around what my job is
|
||||
* doing open source work while being paid for it
|
||||
* starting a side business
|
||||
* doing small inclusion projects at work
|
||||
* writing zines is very time consuming but I feel happy about the time I spent on that
|
||||
* blogging is always great
|
||||
|
||||
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://jvns.ca/blog/2018/12/23/2018--year-in-review/
|
||||
|
||||
作者：[Julia Evans][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://jvns.ca/
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://jvns.ca/blog/2015/12/26/2015-year-in-review/
|
||||
[2]: https://jvns.ca/blog/2016/12/21/2016--year-in-review/
|
||||
[3]: https://jvns.ca/blog/2017/12/31/2017--year-in-review/
|
||||
[4]: https://github.com/rbspy/rbspy
|
||||
[5]: https://github.com/benfred/py-spy
|
||||
[6]: https://github.com/adsr/phpspy/
|
||||
[7]: https://jvns.ca/blog/2018/09/08/an-awesome-new-python-profiler--py-spy-/
|
||||
[8]: https://twitter.com/sehurlburt
|
||||
[9]: https://stackingthebricks.com/
|
||||
[10]: https://www.amazon.com/Growing-Business-Paul-Hawken/dp/0671671642
|
||||
[11]: https://egghead.io/
|
||||
[12]: https://www.indiehackers.com/
|
||||
[13]: https://twitter.com/jshirley
|
||||
[14]: https://wizardzines.com/zines/manager/
|
||||
[15]: https://jvns.ca/blog/senior-engineer/
|
||||
[16]: https://www.youtube.com/watch?v=FBMC9bm-KuU
|
||||
[17]: https://jvns.ca/blog/2018/04/16/rbspy-talk/
|
||||
[18]: https://www.deconstructconf.com/2018/julia-evans-build-impossible-programs
|
||||
[19]: https://www.youtube.com/watch?v=obB2IvCv-K0
|
||||
[20]: https://softwareengineeringdaily.com/2018/06/05/profilers-with-julia-evans/
|
||||
[21]: https://twit.tv/shows/floss-weekly/episodes/487
|
||||
[22]: https://www.codenewbie.org/podcast/how-does-the-internet-work
|
||||
[23]: https://hanselminutes.com/643/learning-how-to-be-a-wizard-programmer-with-julia-evans
|
||||
[24]: https://player.fm/series/eggheadio-developer-chats-1728019/exploring-concepts-and-teaching-using-focused-zines-with-julia-evans
|
||||
[25]: https://www.amazon.com/gp/product/B000EOPQ7E/ref=as_li_tl?ie=UTF8&camp=1789&creative=390957&creativeASIN=B000EOPQ7E&linkCode=as2&tag=diabeticbooks&linkId=ZBZBIVR4EB7V6JFL
|
||||
[26]: http://bangbangcon.com
|
||||
[27]: http://bangbangcon.com/west/
|
||||
[28]: https://jvns.ca/blog/2018/09/01/learning-skills-you-can-practice/
|
||||
[29]: https://jvns.ca/blog/2018/05/11/batch-editing-files-with-ed/
|
||||
[30]: https://jvns.ca/categories/ruby-profiler/
|
||||
[31]: https://jvns.ca/blog/2018/09/23/why-sell-zines/
|
||||
[32]: https://jvns.ca/blog/2018/09/01/who-pays-to-educate-developers-/
|
||||
[33]: https://jvns.ca/blog/2018/02/18/working-remotely--4-years-in/
|
||||
[34]: https://karla.io/
|
||||
@ -1,144 +0,0 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: ( )
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (!!Con 2019: submit a talk!)
|
||||
[#]: via: (https://jvns.ca/blog/2019/02/16/--con-2019--submit-a-talk-/)
|
||||
[#]: author: (Julia Evans https://jvns.ca/)
|
||||
|
||||
!!Con 2019: submit a talk!
|
||||
======
|
||||
|
||||
As some of you might know, for the last 5 years I’ve been one of the organizers for a conferences called [!!Con][1]. This year it’s going to be held on **May 11-12 in NYC**.
|
||||
|
||||
The submission deadline is **Sunday, March 3** and you can [submit a talk here][2].
|
||||
|
||||
(we also expanded to the west coast this year: [!!Con West][3] is next week!! I’m not on the !!Con West team since I live on the east coast but they’re doing amazing work, I have a ticket, and I’m so excited for there to be more !!Con in the world)
|
||||
|
||||
### !!Con is about the joy, excitement, and surprise of computing
|
||||
|
||||
Computers are AMAZING. You can make programs that seem like magic, computer science has all kind of fun and surprising tidbits, there are all kinds of ways to make really cool art with computers, the systems that we use every day (like DNS!) are often super fascinating, and sometimes our computers do REALLY STRANGE THINGS and it’s very fun to figure out why.
|
||||
|
||||
!!Con is about getting together for 2 days to share what we all love about computing. The only rule of !!Con talks is that the talk has to have an exclamation mark in the title :)
|
||||
|
||||
We originally considered calling !!Con ExclamationMarkCon but that was too unwieldy so we went with !!Con :).
|
||||
|
||||
### !!Con is inclusive
|
||||
|
||||
The other big thing about !!Con is that we think computing should include everyone. To make !!Con a space where everyone can participate, we
|
||||
|
||||
* have open captioning for all talks (so that people who can’t hear well can read the text of the talk as it’s happening). This turns out to be great for LOTS of people – if you just weren’t paying attention for a second, you can look at the live transcript to see what you missed!
|
||||
* pay our speakers & pay for speaker travel
|
||||
* have a code of conduct (of course)
|
||||
* use the RC [social rules][4]
|
||||
* make sure our washrooms work for people of all genders
|
||||
* let people specify on their badges if they don’t want photos taken of them
|
||||
* do a lot of active outreach to make sure our set of speakers is diverse
|
||||
|
||||
|
||||
|
||||
### past !!Con talks
|
||||
|
||||
I think maybe the easiest way to explain !!Con if you haven’t been is through the talk titles! Here are a few arbitrarily chosen talks from past !!Cons:
|
||||
|
||||
* [Four Fake Filesystems!][5]
|
||||
* [Islamic Geometry: Hankin’s Polygons in Contact Algorithm!!!][6]
|
||||
* [Don’t know about you, but I’m feeling like SHA-2!: Checksumming with Taylor Swift][7]
|
||||
* [MissingNo., my favourite Pokémon!][8]
|
||||
* [Music! Programming! Arduino! (Or: Building Electronic Musical Interfaces to Create Awesome)][9]
|
||||
* [How I Code and Use a Computer at 1,000 WPM!!][10]
|
||||
* [The emoji that Killed Chrome!!][11]
|
||||
* [We built a map to aggregate real-time flood data in under two days!][12]
|
||||
* [PUSH THE BUTTON! 🔴 Designing a fun game where the only input is a BIG RED BUTTON! 🔴 !!!][13]
|
||||
* [Serious programming with jq?! A practical and purely functional programming language!][14]
|
||||
* [I wrote to a dead address in a deleted PDF and now I know where all the airplanes are!!][15]
|
||||
* [Making Mushrooms Glow!][16]
|
||||
* [HDR Photography in Microsoft Excel?!][17]
|
||||
* [DHCP: IT’S MOSTLY YELLING!!][18]
|
||||
* [Lossy text compression, for some reason?!][19]
|
||||
* [Plants are Recursive!!: Using L-Systems to Generate Realistic Weeds][20]
|
||||
|
||||
|
||||
|
||||
If you want to see more (or get an idea of what !!Con talk descriptions usually look like), here’s every past year of the conference:
|
||||
|
||||
* 2018: [talk descriptions][21] and [recordings][22]
|
||||
* 2017: [talk descriptions][23] and [recordings][24]
|
||||
* 2016: [talk descriptions][25] and [recordings][26]
|
||||
* 2015: [talk descriptions][27] and [recordings][28]
|
||||
* 2014: [talk descriptions][29] and [recordings][30]
|
||||
|
||||
|
||||
|
||||
### this year you can also submit a play / song / performance!
|
||||
|
||||
One difference from previous !!Cons is that if you want submit a non-talk-talk to !!Con this year (like a play!), you can! I’m very excited to see what people come up with. For more of that see [Expanding the !!Con aesthetic][31].
|
||||
|
||||
### all talks are reviewed anonymously
|
||||
|
||||
One big choice that we’ve made is to review all talks anonymously. This means that we’ll review your talk the same way whether you’ve never given a talk before or if you’re an internationally recognized public speaker. I love this because many of our best talks are from first time speakers or people who I’d never heard of before, and I think anonymous review makes it easier to find great people who aren’t well known.
|
||||
|
||||
### writing a good outline is important
|
||||
|
||||
We can’t rely on someone’s reputation to determine if they’ll give a good talk, but we do need a way to see that people have a plan for how to present their material in an engaging way. So we ask everyone to give a somewhat detailed outline explaining how they’ll spend their 10 minutes. Some people do it minute-by-minute and some people just say “I’ll explain X, then Y, then Z, then W”.
|
||||
|
||||
Lindsey Kuper wrote some good advice about writing a clear !!Con outline here which has some examples of really good outlines [which you can see here][32].
|
||||
|
||||
### We’re looking for sponsors
|
||||
|
||||
!!Con is pay-what-you-can (if you can’t afford a $300 conference ticket, we’re the conference for you!). Because of that, we rely on our incredible sponsors (companies who want to build an inclusive future for tech with us!) to help make up the difference so that we can pay our speakers for their amazing work, pay for speaker travel, have open captioning, and everything else that makes !!Con the amazing conference it is.
|
||||
|
||||
If you love !!Con, a huge way you can help support the conference is to ask your company to sponsor us! Here’s our [sponsorship page][33] and you can email me at [[email protected]][34] if you’re interested.
|
||||
|
||||
### hope to see you there ❤
|
||||
|
||||
I’ve met so many fantastic people through !!Con, and it brings me a lot of joy every year. The thing that makes !!Con great is all the amazing people who come to share what they’re excited about every year, and I hope you’ll be one of them.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://jvns.ca/blog/2019/02/16/--con-2019--submit-a-talk-/
|
||||
|
||||
作者：[Julia Evans][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://jvns.ca/
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: http://bangbangcon.com
|
||||
[2]: http://bangbangcon.com/give-a-talk.html
|
||||
[3]: http://bangbangcon.com/west/
|
||||
[4]: https://www.recurse.com/social-rules
|
||||
[5]: https://youtube.com/watch?v=pfHpDDXJQVg
|
||||
[6]: https://youtube.com/watch?v=ld4gpQnaziU
|
||||
[7]: https://youtube.com/watch?v=1QgamEwwPro
|
||||
[8]: https://youtube.com/watch?v=yX7tDROZUt8
|
||||
[9]: https://youtube.com/watch?v=67Y-wH0FJFg
|
||||
[10]: https://youtube.com/watch?v=G1r55efei5c
|
||||
[11]: https://youtube.com/watch?v=UE-fJjMasec
|
||||
[12]: https://youtube.com/watch?v=hfatYo2J8gY
|
||||
[13]: https://youtube.com/watch?v=KqEc2Ek4GzA
|
||||
[14]: https://youtube.com/watch?v=PS_9pyIASvQ
|
||||
[15]: https://youtube.com/watch?v=FhVob_sRqQk
|
||||
[16]: https://youtube.com/watch?v=T75FvUDirNM
|
||||
[17]: https://youtube.com/watch?v=bkQJdaGGVM8
|
||||
[18]: https://youtube.com/watch?v=enRY9jd0IJw
|
||||
[19]: https://youtube.com/watch?v=meovx9OqWJc
|
||||
[20]: https://youtube.com/watch?v=0eXg4B1feOY
|
||||
[21]: http://bangbangcon.com/2018/speakers.html
|
||||
[22]: http://bangbangcon.com/2018/recordings.html
|
||||
[23]: http://bangbangcon.com/2017/speakers.html
|
||||
[24]: http://bangbangcon.com/2017/recordings.html
|
||||
[25]: http://bangbangcon.com/2016/speakers.html
|
||||
[26]: http://bangbangcon.com/2016/recordings.html
|
||||
[27]: http://bangbangcon.com/2015/speakers.html
|
||||
[28]: http://bangbangcon.com/2015/recordings.html
|
||||
[29]: http://bangbangcon.com/2014/speakers.html
|
||||
[30]: http://bangbangcon.com/2014/recordings.html
|
||||
[31]: https://organicdonut.com/2019/01/expanding-the-con-aesthetic/
|
||||
[32]: http://composition.al/blog/2017/06/30/how-to-write-a-timeline-for-a-bangbangcon-talk-proposal/
|
||||
[33]: http://bangbangcon.com/sponsors
|
||||
[34]: https://jvns.ca/cdn-cgi/l/email-protection
|
||||
@ -1,63 +0,0 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: ( )
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (Taking a year to explain computer things)
|
||||
[#]: via: (https://jvns.ca/blog/2019/09/13/a-year-explaining-computer-things/)
|
||||
[#]: author: (Julia Evans https://jvns.ca/)
|
||||
|
||||
Taking a year to explain computer things
|
||||
======
|
||||
|
||||
I’ve been working on explaining computer things I’m learning on this blog for 6 years. I wrote one of my first posts, [what does a shell even do?][1] on Sept 30, 2013. Since then, I’ve written 11 zines, 370,000 words on this blog, and given 20 or so talks. So it seems like I like explaining things a lot.
|
||||
|
||||
### tl;dr: I’m going to work on explaining computer things for a year
|
||||
|
||||
Here’s the exciting news: I left my job a month ago and my plan is to spend the next year working on explaining computer things!
|
||||
|
||||
As for why I’m doing this – I was talking through some reasons with my friend Mat last night and he said “well, sometimes there are things you just feel compelled to do”. I think that’s all there is to it :)
|
||||
|
||||
### what does “explain computer things” mean?
|
||||
|
||||
I’m planning to:
|
||||
|
||||
1. write some more zines (maybe I can write 10 zines in a year? we’ll see! I want to tackle both general-interest and slightly more niche topics, we’ll see what happens).
|
||||
2. work on some more interactive ways to learn things. I learn things best by trying things out and breaking them, so I want to see if I can facilitate that a little bit for other people. I started a project around this in May which has been on the backburner for a bit but which I’m excited about. Hopefully I’ll release it soon and then you can try it out and tell me what you think!
|
||||
|
||||
|
||||
|
||||
I say “a year” because I think I have at least a year’s worth of ideas and I can’t predict how I’ll feel after doing this for a year.
|
||||
|
||||
### how: run a business
|
||||
|
||||
I started a corporation almost exactly a year ago, and I’m planning to keep running my explaining-things efforts as a business. This business has been making more than I made in my first programming job (that is, definitely enough money to live on!), which has been really surprising and great (thank you!).
|
||||
|
||||
some parameters of the business:
|
||||
|
||||
* I’m not planning to hire employees or anything, it’ll just be me and some (awesome) freelancers. The biggest change I have in mind is that I’m hoping to find a freelance editor to help me with editing.
|
||||
* I also don’t have any specific plans for world domination or to work 80-hour weeks. I’m just going to make zines & things that explain computer concepts and sell them on the internet, like I’ve been doing.
|
||||
* No commissions or consulting work, just building ideas I have
|
||||
|
||||
|
||||
|
||||
It’s been pretty interesting to learn more about running a small business and so far I like it more than I thought I would. (except for taxes, which I like exactly as much as I thought I would)
|
||||
|
||||
### that’s all!
|
||||
|
||||
I’m excited to keep making explanations of computer things and to have more time to do it. This blog might change a bit away from “here’s what I’m learning at work these days” and towards “here are attempts at explaining things that I mostly already know”. It’ll be different! We’ll see how it goes!
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://jvns.ca/blog/2019/09/13/a-year-explaining-computer-things/
|
||||
|
||||
作者：[Julia Evans][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://jvns.ca/
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://jvns.ca/blog/2013/09/30/hacker-school-day-2-what-does-a-shell-even-do/
|
||||
Loading…
Reference in New Issue
Block a user