There was a period where this confusion was there with Teams (Classic) and Teams (New).
There was the whole .NET Core/.NET (while having .NET Standard for libraries) confusion. Even now many people think .NET requires Windows. Maybe they should have named it .NET Open?
What confusion? "x years of .NET experience" is what I see and it should suffice unless your whole career has been in an archaic version of .NET framework then you should have no issues working with either.
Do they just not let marketing into the important meetings? Naming isn’t a solved problem but marketers are usually pretty good at knowing when to avoid confusing situations like these.
In my experience Marketing causes most product and feature naming issues. Technical folks want to name it something obvious, and marketing overrules them.
This is such a wholesome post. It also shows how much agency we can have in our local community. It reminded me of the Derek Sivers story[0] about the dancing man and the first follower when I read the part about the first person (Luke) joining them.
When I reread these, I always pick up some details that I missed in the earlier reads:
- On the shortness of life
- Traction: How Any Startup Can Achieve Explosive Growth
- Show your work and Steal like an artist
- Domain modeling made functional
I've created: 1. a very minimal bookmark app, 2. a completely local (localStorage) markdown notes app, and 3. now working on a local Kanban app (like a local Trello).
1 and 2 are publicly available. Apart from tweeting once about the second app, I didn't post links anywhere so it almost satisfies the "just for yourself" criteria.
Over the years, trying to learn different languages/frameworks, failing most of the times and succeeding occasionally, I have found two things that help me:
1. Find an interesting project that suits the language/framework and keep the scope very minimal so I can complete it in 2 days (weekend). I can always learn more doing a second or third project. But I find that I can maintain my motivation when I see results and complete a project.
2. Restrict the number of new technologies for the project to maximum two (best if it is one). When there are many new things, I find that it can be exhausting and I give up after just a couple of hours. So for ex: When I initially learned React, I didn't know GraphQL, so even if I see a case where GraphQL might be the best fit, I will use REST API. This way I'm not stuck on all fronts.
To answer the first question, there is no single project I build to learn every language because that becomes boring for me. I try to build different projects every time.
For ex: When learning React, I built a HN reader, Foreign exchange meme reaction, and an app where I can see the time of all my teammates spread across the globe (all completed and live). When learning ReactNative, I built a small Twitter clone (haven't published it).
This completely resonates with me.
Around 12 years back, when I was in my final year of college, I started a blog where I interviewed people who were doing interesting things (mostly online, like influential bloggers, startup founders, etc). Surprisingly [1], most people responded positively to the interview request.
After a few months of consistently publishing interviews, I started to get a lot of nice things come my way. The most memorable one is when one of the interviews led to a short term paid project and eventually a job offer (I didn't take it but wish I had).
I have had similar experiences in the past 12 years whenever I published something or built a side project and posted a Show HN.
[1] I say surprisingly because I didn't have a following at that point or a popular blog
I created https://plaintweet.com/ primarily for myself. I posted it on HN sometime back and many people visited it. It is completely free and doesn't use any analytics so I don't know how many people use it (if any).
It runs on a $5 VM along with some other small projects, so it doesn't cost me much and hence the outcome doesn't matter.
Fantasic idea and implementation. My timeline on here compared to twitter.com looks more sane and inteligent without those recommendations of 'X liked this tweet', and all the news topics. I assume that's because it's getting the raw feed.
I also love low-fi websites like this. I think websites shouldn't be a large drain on resources, and should embrace standard HTML as much as possible.
This has the opportunity to curve timewasting scrolling by making it more a periodical read. As such, I'd like the return of the timestamps and to implement hourly pagination, so that there's an 'end' point and a easy bookmark to start where you left off.
Thank you for the feedback. Glad you like this. Yes, I was spending way too much time because of the endless feed and scroll. I was seeing more things I didn't subscribe to (follow) than what I subscribed to. So I created this app.
The timestamp idea is great. I will look into implementing it next. It's always nice to have a start and an end. Maybe I will add a setting where the user can specify how frequently they want to fetch new items.
If this writing is what the author brings to the table, I think they are more than capable of writing a useful blog. And with more writing, it will only get better.
> It feels as if I should have great things to say about... stuff... and yet I don't. Every opinion I have is a copy of a copy of a copy of the first 5 top-level comments on a reddit-slash-hacker-news comment section.
Almost everything that's said or written is a copy of a copy of a copy. But as a reader, your 5th level copy might be the first time I'm encountering that particular idea. If only one person says something, the chances of me finding it are negligible. If a thousand people say the same thing, it significantly increases the chances of me finding it.
There was the whole .NET Core/.NET (while having .NET Standard for libraries) confusion. Even now many people think .NET requires Windows. Maybe they should have named it .NET Open?