I was thinking more specifically about building web apps (or software systems). I think there's something there as well
1,614 karma · joined January 18, 2012
meet.hn/city/us-Durham
Socials: - linkedin.com/in/prashanth-sadasivan - github.com/prashanthsadasivan
---
I was thinking more specifically about building web apps (or software systems). I think there's something there as well
I think the concept of 'covered ground' is especially fascinating when it comes to thinking about the meta of building web apps. Do you really appreciate the trade offs between MySQL and MongoDB, if you haven't ran into the scaling issues between the two? I don't think "running a bad migration" is covering enough ground to appreciate the differences. Is struggling to wrangle a bug in an Angular 1 directive enough 'covered ground' to understand the meta in building frontend applications?
And I wonder if the meta is moving towards low code and no code frameworks. Dark Lang looks pretty cool, though I've never really used it. Retool proved really valuable for internal dashboards for managing customer support at my last company.
You could explore the meta at a more fine grained level than just 'web apps', or zoom out to software in general and try to understand the meta (just like you could analyze why certain units in SC2 are just broken, or understand why the economies of the different races mean different opportunities for timing attacks for each race)
I want game devs to be able to make a living, but there's a difference between game devs who responsibly put in monetization and game devs just trying to squeeze every last cent through deceit and manipulation.
I understand the point about 'gray area', however there is truly a difference in power here, and end-users are never accurately informed about what of their data is available to 3rd party advertisers. In fact, I don't think content producers like Stratechery know what data ad trackers track and how it's used.
There is a problem about funding good content like Stratechery, but surely mass surveillance by private corporations isn't the only option?
I've often had this thought - what is the ultimate cost of giving someone a random friday off, not counted against any sort of vacation policy? "Hey, you've been working really hard and the team is better off for the work you've done, take a three or four day weekend". Would that really harm the bottom line? I mean, in a metrics driven environment, if we hit our metrics, then why not spend some time gearing up for the next thing by recharging?
Now that I'm on DDG, I find that I'm following a similar pattern of searching DDG, then searching google, and I'm finding that most of my searches work great on DDG. What's surprising to me is that when I move on to using Google, I'm considering widening my search even beyond DDG and Google. It feels like, by considering different search options, I'm going back to how I used to explore the internet, rather than defaulting to taking Google's results as truth.
And now, seeing a variety of options from DDG, I am surprised at how irrelevant some of the links are on Google some times. It feels like when I search on Google, Google is telling me 'No no, you don't care about JsonAPI parsing performance, you care about parsing json, because we know best'.
I'm glad that DDG is alive and doing well. I love using it and I don't notice any difference for most queries, and falling back to google hasn't really been as painful as I thought it would be.
But also to basically decide that the language ergonomics and syntax is "finished" this quickly is truly impressive. The addition of macros, combined with the huge focus on developer experience, I think allows the core team to say "its feature complete" while not worrying about any particular missing features in the language (you can probably just implement it yourself anyway)
That being said, I found this anecdote to be particularly... unsettling.
> “I try to tell him somebody wrote code to make you feel this way — I’m trying to help him understand how things are made, the values that are going into things and what people are doing to create that feeling,” Mr. Lilly said. “And he’s like, ‘I just want to spend my 20 bucks to get my Fortnite skins.’”
It's tough to explain away the emotional desire for something that was manufactured to be cool and addictive
I don't really care about growing something as a startup. I don't need to revolutionize anything. I just want to make someone's day better through software. I want to launch a cool product that people find fun, silly, useful, critical to their process, whatever you want, and NOT be beholden to interests of anyone who isn't involved in the daily operations of whatever product that is.
I just want to build something, and make it better every day. Something that I own, that I can change however I want, whenever I want. I shouldn't have felt like I needed a16z to invest in my company to believe that my product is worth something.
[1]http://angularjs.blogspot.com/2014/10/ng-europe-angular-13-a...
http://www.shakelaw.com/legal-info/freelancehire-agreements/
https://coinbase.com/docs/merchant_tools/payment_buttons
I've used it on overstock.com and it's pretty incredible. I think it's the least amount of information I've ever had to enter to buy something online. All I entered was the shipping address and my email address.
Q. My soufflés keep collapsing! What can I do?
A. In order for the meringue to peak properly we suggest adding a little lemon juice to the béchamel. This strengthens the mixture and prevents tragedy.
Just because its not focused on code doesn't mean you can dismiss it as "some intern" project.
Maybe I just didn't understand what you were trying to say...
Keep developing this awesome framework.
As a developer who has friends who have developed "non-trivial" iOS apps, damn. This is pretty spot on exactly what happened (happening still even) on Android with pre/post 3.0 applications. Making sure that the UI works on both categories of devices is just awful. There are a few projects out there to help (ActionBarSherlock, HoloEverywhere), but it takes a lot of diligence, ESPECIALLY if you're trying to do combination tablet and phone apps.
A lot of the posts I've read on this thread are missing the point of the post. It's not just about change, its not about fragmentation, its about the excitement for newcomers to join an ecosystem that has felt super saturated for years. It may not actually shake the foundation of the app store, but it at least allows for new talent to enter on the same playing field as those who have been developing iOS applications for years. That's just exciting.
I'd say first pick a project by going and building something that relies on some cool Github library. I don't think anyone but me clicks on the "Explore" tab on Github, but check it out, find a repository that you think is awesome, try using it in your own small project. Then I'd say go ahead and look at the issues that the library is having, and start tackling them one by one.