ux4
Joined 9 years ago
Joined 9 years ago
Ignore all the spammy websites that usually regurgitate random links. Focus on the sites with high DR that don't have the "NoFollow" attribute. These are the hard-hitting websites that boost your domain for SEO purposes and can be good places to get feedback on your own product.
Market validation - especially for online products and services - is indeed incredibly important, but not many people like to write about it because it is actually very drab and a tiny bit audacious.
His market validation - you are seeing it. It is a submission to Hacker News.
Ok ok, that is a given, but the author alludes to other various ways he gets feedback and validation for his products. He also talks about how well his products were received on Product Hunt and you can also follow him on Twitter.
My final advice for seeing how online services validate their ideas - run the product's domain through a backlink checker. It lets you see what other websites link to their product and what avenues they pursued for outreach. Each of those submissions exposes the product to potential customers and gives valuable feedback to the creator.
When you are building for fun, it is for yourself. When you are building for profit, it is for other people. When you are building for fun, you get to decide what to work on and when to stop - usually when it is no longer fun. When you are building for profit, other people decide what you work on and when you are done - usually when no new features are requested, you have no competition, and you have absolutely saturated your market. This rarely ever happens so you always have something propelling you.
The biggest failure most engineers encounter is they build things nobody asked for. They build products without customers lined up, for markets that do not currently exist, with only feedback from themselves. This is because they built the product for fun thinking they were building it for profit.
The line between the two is very easy to blur - especially when reading OP's blog where he genuinely sounds like he had fun building his projects, but I guarantee there was also a lot of very unfun background work done in the name of profit.
Edit: Don't just take my guarantee for it, read about his challenges for One Item Store https://tinyprojects.dev/projects/one_item_store
Containerism and modern devops practices become borderline impossible when you're working with a monolithic database that's encumbered in complex business processes. Ideally you're working with independent, decoupled microservices, but that's far from the reality that most admins face.
Receiving career advice online isn't very useful unless you live in the bay area or know the credibility of the person giving advice. Odds are your local labor market has a completely different landscape with different skill requirements.
I would like to encourage you to act on those ideas because the real art is in translating those ideas into practical solutions. Everyone has their own ideas of what would solve a problem, but 99% of those ideas will not work because they are not grounded on reality.
Secondly, there isn't really any scalability in the market for heavy equipment. Even if firms made a big change to the heavy equipment design/mfg industry, they most likely won't capture any new markets. Even a substantial change won't make the average Joe say "Hey I should buy a 400 ton dump truck." The only benefactors of the disruption would be the consumers listed above, who again are pretty indifferent.
Finally, it's also heavily burdened by bureaucracy and regulations. I imagine the biggest bottlenecks to the industry are all the requirements for safety and quality. If someone gets hurt with your equipment, you are in for a multi-million dollar lawsuit. You need approvals, permits, inspections, and QA, each of them slowing the process down further. It's also possible the industry can experience a drastic change from a breakthrough in technology, some kind of mass adoption of a new process, or some sudden increase in demand for heavy equipment, but I see that being dependent on changes outside of the industry.
Practice gratitude. Get a pen and paper and start writing down things in your life that you're grateful for. It can be something as simple as being grateful for food, water, and shelter (which gets taken for granted so often).
Do this for 15 minutes a day (preferably as soon you wake up) and you will notice your outlook on life improve. Religious people do this in the form of prayer, and it has been scientifically proven to increase your happiness.
http://articles.latimes.com/2010/jun/30/local/la-me-rave-dea...
Lawyers made a case of negligence against the organizers, they had a lengthy trial, the organizers settled with the parents outside of court, and the festival was never held in Los Angeles again. As a result of this tragedy and similar events, tight security is introduced, rules are put into place, and we get sterilized events in an attempt to tame the beast. But where do we draw the line?
Reading this article felt like the typical Coachella-hate circlejerk because it was more about Coachella than any other music festival, but a good point they brought up was the RFID chips on wristbands that allow them to track your location 24/7. Sure it helps with logistics, but it also lets them track you back to your hotel, where you ate for breakfast, what vendor booths you visited, who you were with, etc. This in combination with the required Coachella phone app would allow them to accrue a pretty large amount of personal data.
Highly technical programming articles can be hard to digest and don't appeal to a wide audience so they get less upvotes, especially if it's about a specialized language. If you really wanted to read those articles, you could still find them in abundance on other programming/hacking/specialized forums.
> I talked with several engineers in infra orgs, who had 30-50% of their teams drafted into the ADO org. And in some cases, it was the best engineers who left.
> On Tuesday, Meta’s Chief Information and Security Officer (CISO), Guy Rosen, announced his departure.
This Guy was here since 2013, after his mobile tracking app Onavo was acquired, VP of Trust & Safety / Integrity during the high-stakes times of the Cambridge Analytica scandal, handling platform abuse and election interference during a very "yuge" election cycle.
With that goes the accumulated ethics, philosophy, and tribal knowledge that drives organizational cybersecurity and risk, 3 very important factors that can't be automated away or even openly spoken about. This sounds like a massive change to decision making that is larger than engineering.