text stringlengths 0 1.17k |
|---|
[3048.38 --> 3053.82] web don't forget that uh the trends are very clear that everyone's moving to mobile i know i sound like a |
[3053.82 --> 3060.14] broken record here but if uh if i have to tell anyone anything it's um develop and test on mobile |
[3060.14 --> 3064.38] phones and tablets for your great web stuff because that's where your users are and and we think dark |
[3064.38 --> 3071.02] can help you do that awesome so okay great so we we ask our uh our guests the same uh set of questions |
[3071.02 --> 3075.10] at the end of every show and i want to go ahead and ask you all these questions so i'll ask lars first |
[3075.10 --> 3079.18] and and you kind of both answered this first one already but and just in case there's anything else |
[3079.18 --> 3086.54] uh do you have like a call to arms for the community um yes my call to arms is that innovation |
[3086.54 --> 3091.34] is important and programmers have to be flexible and try out new stuff to see if they're more |
[3091.34 --> 3096.78] efficient using a different platform there than they used in the past so try out that and and |
[3097.66 --> 3103.50] see if it's more efficient and set anything from you other than uh building mobile stuff i'll be |
[3103.50 --> 3109.10] really specific about it in dev tools you can turn on mobile emulation so my call to arms is |
[3109.10 --> 3113.74] when you develop on your desktop and you're you're in chrome or dev tools turn on mobile emulation |
[3113.74 --> 3118.38] and just always live with that uh that little window there gotcha |
[3120.46 --> 3125.98] the second question here is um if you weren't doing this what would you be doing and i'll ask you first |
[3125.98 --> 3133.18] seth uh probably doing something around education or teaching i'm really inspired by the uh the mooc the |
[3133.18 --> 3137.42] the online classes and courseware stuff and so i don't know i think i think that'd be pretty interesting |
[3137.42 --> 3145.26] gotcha and for you lars oh i need more spare time i am i would travel the world uh on a bike |
[3146.22 --> 3148.62] um well you can only travel part of the world on a bike |
[3150.70 --> 3150.78] yeah |
[3150.78 --> 3159.02] but i think i get on a plane at some point or a boat that that is true but uh half a year on the bike |
[3159.02 --> 3164.86] would be great for me uh but i always have so i've tried it before and it never works so |
[3164.86 --> 3170.94] um i would say if i don't do that i would probably do another language or vm project nice |
[3172.94 --> 3178.06] and lars um for a programmer hero or just somebody that's been hugely influential in your life |
[3179.26 --> 3185.90] oh i have to mention my old professor ole lehmann masson uh he was the uh co-designer of the beta |
[3185.90 --> 3193.50] programming language a successor to similar 67 if you remember that uh he's been very inspirational in |
[3193.50 --> 3197.90] pushing me to do languages and and virtual machine implementation all the way back in the |
[3198.78 --> 3205.82] mid 80s so that's he's probably the main reason why i'm um doing it still that's awesome and seth |
[3206.70 --> 3212.46] i gotta say uh neil degrasse tyson the scientist and educator is just really inspiring to me because |
[3212.46 --> 3218.46] that's someone who clearly knows what he's doing and talking about but is so passionate and inspirational |
[3218.46 --> 3224.06] with how he delivers that stuff to to the world so i really enjoy watching him i've actually been |
[3224.06 --> 3228.86] waiting for the day for somebody to mention him as their hero because he's he's uh he's been a |
[3228.86 --> 3233.58] personal hero for many that i've known and he's with the new show recently obviously it's really good |
[3233.58 --> 3238.30] so people are really enjoying his method of teaching kind of comes from his own predecessor too |
[3238.30 --> 3250.06] yeah nobody said anything to that no no love for adam no love for adam i've been listening to this |
[3250.06 --> 3253.66] show i mean this is one of those shows where i wanted to kind of jump in but i feel like i don't |
[3253.66 --> 3258.70] add a ton i wanted to kind of dig in a bit more about the pub package manager but uh we can save that |
[3258.70 --> 3265.18] for a different show i'm sure yeah yeah so anything else you guys want to mention here before we go ahead |
[3265.18 --> 3273.02] and close out the show uh just thanks for inviting us um we need to to get everybody to listen in on |
[3273.02 --> 3278.70] what that is all about so um we are just happy to be here yeah i really appreciate the opportunity i |
[3278.70 --> 3284.38] remember uh the changelog is always one of those podcasts that is on the top of my queue and for a |
[3284.38 --> 3289.74] long time now so it's it's kind of an honor to be on the show so thanks well it's an honor to have |
[3289.74 --> 3294.78] you guys so what so i just wanted to absolutely yeah so i wanted to once again just say thanks to |
[3294.78 --> 3300.38] lars and seth for joining us on today's show like like we kind of kind of alluded to uh dart is a |
[3300.38 --> 3307.18] is a big project and um it's hard to to do any project the size of dart you know justice in a 45 |
[3307.18 --> 3312.46] minute to an hour radio show uh so i just want to encourage just like they were saying to encourage |
[3312.46 --> 3316.78] anyone if you're interested in this whatsoever just head over to the website it's it speaks for |
[3316.78 --> 3321.26] itself and it's something that uh you can just start hacking on in your own time and and really i mean |
[3321.26 --> 3326.46] just with the small amount of time i've spent on it just to kind of learn it and stuff it's been a uh |
[3326.46 --> 3331.18] it's been a pleasant experience something worth checking out worth hacking on i think it's uh |
[3331.18 --> 3336.54] definitely something we will want to consider uh talking about more on this show in the future but |
[3336.54 --> 3341.58] uh once again i just wanted to say thanks a bunch for joining us and and that's it for this week uh |
[3342.22 --> 3347.26] just for the listeners if you have not subscribed to the changelog weekly it is our weekly email where we |
[3347.26 --> 3353.02] share everything that hits our open source radar you can subscribe at the changelog.com weekly |
[3353.98 --> 3360.70] and um we will be back next week i don't think we know the uh guest yet adam so we will save that as |
[3360.70 --> 3366.46] a super the guest is still pending yes you're right yeah yeah so until next week though let's say goodbye |
[3367.02 --> 3368.54] all right bye-bye thank you |
[3377.26 --> 3383.58] you |
• Mike Parham's new project, Inspector, is a monitoring tool for application infrastructure |
• Inspector is a reimagined version of monitoring, with a focus on guiding users to build reliable applications |
• It doesn't monitor initd services, instead promoting the use of modern init systems like upstart or systemd |
• Inspector aims to provide a more user-friendly and efficient monitoring experience than existing tools like Monit |
• It makes some design choices that might not be liked by everyone, such as not supporting legacy initd services. |
• The host and guest discuss the guest's transition to creating a commercial product on top of an open-source product, specifically with sidekick and inspector. |
• The guest shares their decision to create a business model that includes both an open-source product and a commercial product. |
• The guest explains that he initially only had an open-source product, but found that it didn't generate enough revenue to justify his time. |
• The guest describes how he created a commercial product on top of sidekick and started selling it, which led to a good income and the ability to provide for his family. |
• The guest mentions other business models, such as services and consulting, and notes that he prefers to keep his business small and focused on creating smaller, useful tools. |
• The guest shares his experience with sidekick and inspector, and notes that creating a commercial product on top of an open-source product can be a successful business model. |
• Open-source vs. commercial versions of Sidekick |
• Concerns about people taking Sidekick features and adding them to the open-source version |
• Distinguishing between paying for features and paying for long-term support and maintenance |
• Customer behavior: companies want stability and support for their business, but developers may use open-source versions for personal projects |
• Sales numbers for Sidekick Pro: $7,500 in 2012, $85,000 in 2013, and expected to top $175,000 this year |
• Recurring income and diversification: the decision to launch a new product with a similar model to Sidekick Pro |
• Diversifying investments and products to reach a wider customer base |
• Inspector as a generic product useful to anyone using Linux, not just Ruby |
• Diversification of products to mitigate risk of a single product's failure |
• Inspiration from Mana and existing open-source tools that are cumbersome to use |
• Criticism of existing open-source monitoring tools as being unfriendly and overly complex |
• Goal of creating a simple, easy-to-use product (Inspector) with minimal configuration |
• Steps to create a successful open-source/commercial product, including: |
• Finding a non-trivial and important tool for your current system or workflow |
• Identifying a market gap in an existing product with too many features or complexity |
• Creating a simpler, more user-friendly product that solves a specific problem |
• Streamlining a word processor by simplifying and adding useful functionality |
• Building a business model by offering free and paid features |
• Drawing a line between free and paid functionality |
• Evolving from an open-source project to a commercial product |
• Monetizing a product through recurring income and pricing strategy |
• Identifying pain points in software development, such as html to pdf conversion |
• Using the "30 by 500" formula to calculate potential revenue |
• Breaking down the process into achievable steps |
• Building a business on spare time and with minimal investment. |
• Salary vs sidekick pro income and when the author started considering going full-time |
• Drawing a line between pro features and open source features in the inspector project |
• The author's approach to distinguishing enterprise features from team features |
• Balancing open source contributions with pro features and revenue generation |
• Managing third-party contributions and avoiding conflicts of interest |
• Lessons from Twitter's API management and road mapping approach |
• Discussion of Twitter's free and paid model and the trade-offs involved |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.