List of investment trends, or Black Mirror bingo card?
16 Things
71–80 of 135 posts
Re: 16 Things
#72I'm not sure what they want to accomplish with this edict(?). Maybe it's an attempt to influence entrepreneurs to create ideas in those 16 areas. I mean, only those 16 areas? We are in the middle of some unprecedented cultural shifts, and those are the 16 areas to focus on?
For we, the readers, I think we should look at it more as kind of a brainstorm, something to get us thinking. I think looking for more in it than that is not what is most useful for us. Just my two cents.
Re: 16 Things
#73Their "Security" section is a bit naive. The questions it poses go all the way back to the 1990s. If the Jericho Forum had started a VC fund, this page would be their investment thesis. The 2000s saw a wave of companies try to capitalize on "deperimiterization", some with huge capex requirements (one NAC startup had designed and contract fabbed their own MIPS core). They all flopped. Maybe it's true that firewalls ar…
What bothers me are things like this which appear to be marketing messages aimed at CYA types or to simply lather up grandpa and the media: "The threat of people getting into our systems today is so great that every company in the world has to embrace the notion that not only are they going to get hacked, there’s a good chance hackers are already inside … and they just don’t know it." ...and this: "This set of compan…
The idea is that you shouldn't focus on making yourself "unhackable", because that is not possible. It's not possible to have 100% security. A skilled and determined attacker will likely get inside to some extent, even if it's just malware or access to an old unused server.
The point is to make detection and remediation important parts of risk management as well, not just prevention. Prevention is spell check, it's not always going to catch everything. Because the reality is, anyone (to your point, not necessarily everyone, but certainly anyone) can be hacked. Rather than focusing exclusively on a hard crunchy shell, make sure you can detect someone already inside and lock them down when you do. Corporate security needs to be right 100% of the time. The attacker only needs to be right once.
But yes, it's certainly possible that everyone can be hacked, and for certain definitions, it's completely likely that every company will or has been hacked (if you include malware, and information disclosure). How much malware is on your network that you don't know about?
Re: 16 Things
#74Re: 16 Things
#75In the 'Online Video' section he calls out podcasts as an emerging/trending medium. I'd love to hear more about where people in HN community feel it's moving. Of course there's the obvious Serial momentum, and as a passionate consumer of podcasts I'd love to think through with you guys a little more where we think it'll go. For example a YouTube-like podcast portal seems like a potential option (i.e. moving away from…
I run https://sysadmincasts.com/ , which is a weekly bite sized screencast for sysadmins. Also posted to Show HN a while ago [1]. I can tell you that my inbox is flooded with "Thank You" messages, and requests to put out more content, I am struggling to keep up! As patio11 put it, if you can say: "I'll save you 12 hours of Googling and reading Free Information On The Internet (TM) and it will cost you $50" [2], you c…
Just listened to the ZFS on Linux episode. I was sceptical about watching a command-line narrative, but this was incredibly well executed, with episode transcript and mini-reviews of related sites. As the episode started, the speech pattern was so slow I wondered if it was a TTS robot aimed at non-English listeners, but then the voice quickly picked up speed to reach excited-hacker cadence.
How long does it take to write and produce each episode? Would you care to share the toolchain being used for screencasts?
I miss the lost promise of SMIL which would have allowed in-context video links to URLs for related sites, or deep-linking to related video snippets in other episodes. If your project continues, you will quickly grow a library which will benefit from cross-indexing. You will also find that a subset of content will need to be refreshed, as tools and environments change. Metadata for modular snippets will improve discovery, reuse and update.
Rails Tutorial has generated six-figure revenue from screencasts combined with an ebook, so there is precedent for monetizing self-service video training.
Re: 16 Things
#76Earlier quoted context omitted.
I run https://sysadmincasts.com/ , which is a weekly bite sized screencast for sysadmins. Also posted to Show HN a while ago [1]. I can tell you that my inbox is flooded with "Thank You" messages, and requests to put out more content, I am struggling to keep up! As patio11 put it, if you can say: "I'll save you 12 hours of Googling and reading Free Information On The Internet (TM) and it will cost you $50" [2], you c…
Just listened to the ZFS on Linux episode. I was sceptical about watching a command-line narrative, but this was incredibly well executed, with episode transcript and mini-reviews of related sites. As the episode started, the speech pattern was so slow I wondered if it was a TTS robot aimed at non-English listeners, but then the voice quickly picked up speed to reach excited-hacker cadence. How long does it take to w…
Thanks for the kind words ;)
> How long does it take to write and produce each episode?
Rough guide is about ~2-3 hours per minute of video. Research, playing around with ideas, demos, writing, recording video, recording audio, editing, etc. So, ZFS part one was 12 min, that's about 24 hours, and part two is 18 min, so about 36 hours. Those two episodes are about 60+ hours of solid work. ZFS did take a little longer than 60 though, since I ended up doing tons of research, but I rather error on a better quality video, than putting out sub optimal content. These figures are shocking to many people, but I have honestly not found a quicker way. As I learn to use the editing software a little more, I have been able to shave an hour here and there, so that is nice!
> Would you care to share the toolchain being used for screencasts?
Sure, here is a basic dump of the tools I use:
Ubuntu (deskop)
Kazam (desktop recording)
Audacity (audio recording)
Kdenlive (edit the audio/video together)
Screenkey (keystrokes on screen)
Decrypt (intro screen)
OpenOffice Writer (transcripts)
Shaky (ascii diagram to png file)
Asciiflow (diagram tool input for shaky)
Gimp (graphics)Re: 16 Things
#77Talking about "Online Video", I'd like to explicitly mention https://www.vessel.com, which Jeff Jordan implicitly mention here: http://a16z.com/2015/01/22/online-video/
Re: 16 Things
#78For instance, the cost of an endpoint CPU and memory is a 1000x cheaper than the cost of CPU and memory in the server. [1] What do they mean? How was that calculated? It sounds completely wrong. [1] http://a16z.com/2015/01/22/cloud-client-computing/
I think this "thing" is insane.
First of all, battery life. He specifically calls out phones, and "not just phones, they could be wearables and other...", as targets for this. Every bit of computing you do on my device is battery life I lose. You're welcome-in-theory to use some compute on my CPU, but stay the hell away from my battery life, which in practice means stay off my CPU. So there's that.
Second, latency is a big thing in user experience. Go ahead, follow this author's advice, and do your JSON-to-HTML rendering on the client. See how it affects your latency. See how it affects your user experience. See how the latency affects your SEO standings. Try it out.
So once you realize you don't want to use client battery life, and you don't want to use client computing anywhere it would make the user experience perceptibly more latent, what're you left with? Yeah, sure, you could use some background computing power in the style of SETI-at-home and so on... but if you want users' explicit consent, you're competing with those existing for-the-betterment-of-humanity projects, and if you don't get explicit consent, you'd better tread mighty carefully.
Re: 16 Things
#79I just want to know who the fuck has $6000 worth of food in their freezer?
(See Internet of Things category)
Re: 16 Things
#80Earlier quoted context omitted.
Just listened to the ZFS on Linux episode. I was sceptical about watching a command-line narrative, but this was incredibly well executed, with episode transcript and mini-reviews of related sites. As the episode started, the speech pattern was so slow I wondered if it was a TTS robot aimed at non-English listeners, but then the voice quickly picked up speed to reach excited-hacker cadence. How long does it take to w…
Thanks for the kind words ;) > How long does it take to write and produce each episode? Rough guide is about ~2-3 hours per minute of video. Research, playing around with ideas, demos, writing, recording video, recording audio, editing, etc. So, ZFS part one was 12 min, that's about 24 hours, and part two is 18 min, so about 36 hours. Those two episodes are about 60+ hours of solid work. ZFS did take a little longer…
> Rough guide is about ~2 hours per minute of video.
That makes sense, given the high quality result. A 2003 thread estimated production cost for training videos at $1000-$3000/minute, http://answers.google.com/answers/threadview?id=254620 and that range still seems relevant, https://forums.creativecow.net/thread/17/871420
> here is a basic dump of the tools I use
Great that you were able to achieve this level of quality with FLOSS tools. Have you considered pay-what-you-want pricing, with a suggested anchor? Or creating (for pay) screencasts for commercial software? I've often felt that training material should be included in the marketing budget, as it increases the size of the market. E.g. a portion of donations/fees could go towards the OSS project.