You are an inspiration. I have been following your journey since your post about quitting Google hit the HN front page. And what a wild ride it has been.
Your journey shows how hard it is to build a business (especially hardware-based), but with discipline and perseverance, it's definitely possible to create one as a solo founder.
I also have a business idea that I would like to work on, but I am not ready to quit my full-time job yet. I have a few questions for you:
1. Have you always been so disciplined in life? If not, how did you improve it?
2. As you shared here (https://mtlynch.io/solo-developer-year-1/), doubts are natural when you haven't succeeded yet; how did you keep going? Did you ever come close to giving up and going back to corporate America?
3. I believe you have a partner; how did this affect your relationship with your partner?
4. Knowing what you know now, what would you do differently?
If you are ever in NYC, please hit me up; I would love to buy you a drink and chat more in person.
It has two perspectives, 'Main' and 'Review'. For each perspectives, you can configure different 'windows' to be shown/hidden. Window types are 'Changes', 'Journal', 'Branches', 'Git Output' etc.
For the Main perspective, I configure it to show me History + Remote/Local branches + 'Git Output'. This is when I want to interact with the remote repository.
For the Review perspective, I configure it to display the Files/Folders and Changes. You can configure the 'Files' view to show 'modified' files on the top, review the differences in 'Changes' section below and do quick commits.
Yes, the above is not as nice as Eclipse being able to display semantic changes but it's a very nice workflow and have not found anything better.
I worked at a company which wrote their own scheduler and it was fraught with bugs. Dealing with time and date is HARD. Really, really hard. Your custom scheduler will break and at a worst possible time.
If Cron doesn't work, get an open source or commercial solution. And who cares what tech the scheduler is written in? Scheduler's job is to provide run your programs and provide API and a nice GUI if you desire.
Holy Crap. This is amazing. Lot of folks have tried to make a general purpose visual programming solution and it always sucks. However, if we narrow the problem to
1. Show some data on a grid based on user input.
2. Let user select a row.
3. Provide different buttons to take actions on the selected row by doing an API call.
Then your tool solves the above problem extremely well (based on the tutorial I saw). And I guarantee you that any organization with tech teams have need to create plenty of such 'mini apps'.
I recently started a new job as a technical lead and I am going evaluate this tool seriously. Due to the nature of the business, we will be prefer an an on-premise solution. Do you have existing clients who use your on-premise solution? How are the updates to the tool distributed? And most importantly, what's the pricing like? Feel free to reach out to me via email.
BTW, you guys have done FANTASTIC job on the main page design/copy. It's been a long time since I saw a product website which instantly sold me on the idea. Well done!
> I’m not asking for your trust, but I’m committed to earning it.
Love this line. I had followed Xamarin when it was independent and I get a strong feeling that Nat wrote this himself and it's not just a PR speak. I am cautiously optimistic about GitHub going forward.
I would agree that majority of people don't realize how addictive smartphones can be and they don't care about fixing it.
At the same time, I think there are a decent number of people who realize that a smartphone is a GREAT tool they must have in their life but if they are not careful, it will take over their attention completely. The fact that apps like Moment (https://inthemoment.io/) exist and do well is a proof.
I welcome Siempo and I hope they offer a compelling app on the iOS platform. (See my other comment to know why I have my doubts regarding this)
Currently, I use the Moment App on the iOS to keep track of how much time I spend on my phone and it has been immensely useful. Though it only captures my usage and can't actively help me reduce my smartphone usage.
I love the ability to batch up the notifications. In my ideal world, I would get notifications at 8AM, 12pm, 5pm and 9pm. And that's all.
I am jealous of the Android platform that it is possible to create an app like Siempo. I don't think iOS has an API to create a comparable experience.
I hate the driver who pens the L line going to Brooklyn from Manhattan. He speeds way too much and then breaks way too hard. I have seen passenger fall because of it time and again. If we can't get rid of the union workers, I would rather have MTA pay these guys wages to sit at home and replace them with computer-driven subway.
Why is this article so highly voted? As someone who doesn't know Kubernets, this article is just a mumbo jumbo with links to other articles and does not provide any useful detail what so ever.
Wow. I have been using C# for a long time and has dabbled in F# a little bit. And I know F# can help you reduce some boilerplate that C# requires but I have never seen reducing code base by 90 percent like in your case. Can you give us little bit more details? Eg 350k doesn't include blank lines, right? What did the application do? Is it a Windows service or a Web App or a command line program?
Here's the current status of .NET software development.
I think there is a broad agreement that unit testing is a very useful tool in developing quality software. Because of the inherent limitation of C#, you can't unit test easily if you don't use DI. This often leads to a situation where you have tons of interfaces + each interface is implemented exactly by one class. This is because product like Isolator is not free. Hyptothetically, if Isolator was provided by Microsoft for free, I am sure that we will see reduced usage of DI.
Don't get me wrong, I think there are other scenarios where DI is a great technique in designing components which are flexible. However, those scenarios are not that many. Using DI to make your software unit testable is an overkill IMHO.