Ask HN: What are your contrarian views?
There are lots of smart people in this community who are deeply specialised in all sorts of domains.
I'll bet there are some fascinating counter-consensus views at the edges on what the future holds in these domains.
Let's hear them!
What do you think is true in your domain that most of your peers don't?
238 comments
[ 2.5 ms ] story [ 290 ms ] thread- they can be useful on their own without providing a path to something much more advanced
Do they claim to do this?
Edit: it should be clear that I'm speaking anecdotally, right? I obviously can't say for certain.
The recent AirTags discussions have really exposed the phenomenon. The amount of disinformation is pretty incredible, which in turn brings out the pro-Apple folks who feel like they need to correct the facts. So it gets pretty heated.
That sounds plausible. Do you have evidence they do it more than any other large consumer-oriented company?
I think people just naturally tend to promote things that align with their values and rip things that don't. Most technology has no real core values, so they don't inspire much passion either for or against. Only certain things really inspire a lot of passion. Apple is one of course with their design emphasis and they inspire a lot of passion both for and against. Crypto is another. 37signals/basecamp was one of those I guess. Rails was definitely another. All of these things had some outlier values that inspired passionate arguments. Emacs and VIM. Etc.
You can definitely see an anti-fanboy effect with Crypto. If you're a marketer and want to farm upvotes on HN to build up fake accounts, just go in a random crypto thread and type some vapid criticism like "Sure it's great if you love money laundering" even if the criticism is out of context and you'll instantly build up your account.
Sorry what values do huge corporations have?
What people value in a product, not corporate values.
> Sorry what values do huge corporations have?
I didn’t say they had any.
There are also many political shills and astroturfers here.
As someone not working in those industries, it would seem an obvious choice to move to a safer language, so there must be something I'm missing?
The second reason is lack of tooling - specifically Functional Safety toolchains that can be used for ISO26262 projects. There are plans by Ferrous to develop one, but it will take years to gain any adoptions [1].
[1] https://ferrous-systems.com/ferrocene/
tens of thousands of dollars and several months of QA per release means that thanks very much but we’re going to keep using what we have because yours looks nice i’m sure but we don’t care.
Are you just hinting at the fact that these industries are slow to evolve, or is it something specific about the languages?
My team have in the last decade spearheaded initiatives like adopting Agile, C++ (subset) use, Git (as opposed to SVN/proprietary) and extensive use of modern code hosting and CIs and we've met with a lot of resistance in our company (and those we work with). I've also interviewed lots of experienced embedded engineers, e.g. automotive, who have never heard of Agile or used Git.
I think it's a fear of change (risk) and also that the embedded engineering domain is so closely tied to hardware development, which is even slower to change.
https://htmx.org
javascript is a bad front end scripting language for light use cases:
https://hyperscript.org
The recent trend towards decentralization of tech is great, but if data is not portable then its just a different centralization.
For ex. Matrix/Element is great as an example of decentralization, but since you cant do much with the data if you want to go to something else, its still lock in.
You can do a lot with LIDAR, but you can't recognize e.g. traffic lights with absolute certainty.
We could probably have a fully autonomous auto fleet with current/available technologies, if we adapt the roads, rules and such.
Human-like autonomous driving might not happen but getting from a to b doesn't strictly require that.
PS: I am saying this as a former head of product management...
You have to build the organization to be resilient to the types of incoming requests that it will receive. Some sales leads could -- intentionally or accidentally -- lead your organization and product down a path that limits future potential or causes cultural damage.
One of the ways to counter this is simply to spend more time collecting requirements and discussing the topic both internally and externally. Benevolent partners shouldn't want to rush to determine the shape of a feature.
Another slightly-less common counter would be to make the entire process more transparent. That could be difficult for some partners who might want to collaborate on the basis of creating a unique advantage that they'd like to achieve ahead of competitors. However, increasingly, I think that the cost to hide or obscure such plans is becoming greater than the benefits.
(and yep, none of this suggests anything about whether product manager roles are required or not: I think that's more to do with the size of the organization and whether specialization is required. my point is mostly that, regardless of scale, the organization needs to guard itself against misaligned incentives)
1. if these great UX and tech people do the product management themselves?
2. who does product and customer discovery?
3. Is it highly likely that the UX and tech people will know how to do product and customer discovery well - for example ask questions and carry out research the right way?
GET requests should not modify server state outside of caching and should be idempotent!
Sure, things can work okay server side if you're with a top 10 cloud provider, but support gets abysmal quick as you move further from the top.
[1] I'll define this as "the majority of home users perform the majority of their day to day web actively almost exclusively over IPv6"
Now I have better service (reliable 1gb fiber) but no IPv6. Once providers are better motivated, I predict a jump.
Agree with issue on server cloud provider support though, sadly.
-t.thoughtLeadersInTech
People probably aren't going to share the truly interesting insights that deletes a business competitive advantage they have or say something that risks getting them cancelled.
Other applications are like trying to stick a round peg into a square hole.
Some/Many employers are really attached to controlling their employees -> so they want to see them on time, at their job etc.
Nobody will rebel, when told to come back at work and stop remote working.
A lot of people are already so dependent on the system that they will fight to protect the idea: "Oh but it's important for social life to actually go to work". As if, it is literally impossible to meet people in other places than work.
I bet next recession companies extend their life by ditching the office and in extreme cases laying off staff and replacing with staff from lower cost of living areas who can work remote.
Bingo. Remote working is a cost cutting measure. Only those companies that can afford to return to the office are doing so.
Next recession you'll see even more companies go remote as the recession forces cost cutting and rent/commute and their related insurance costs are cost centers that can be removed.
Remote working is a cost cutting measure. Only those companies that can afford to return to the office are doing so.
- Managers must also be programmers
- Managers should set timescales for projects, not the people under them
Probably one of the biggest factors I’ve seen in predicting the success of a software team.
Its like the difference between being a farmer with a plow and having an army of farming robots. The productive multiplier is astronomical.
To gain an appreciation for natural productive multipliers you could play games like Factorio.
Bless, or curse, capitalism.
That's one of the problems with asking people for their "contrarian views".
Apple's shift to Swift has caused a lot of software to be rewritten. It's not obvious that the reduction in software correctness bugs which Swift provides offsets the kind of bugs that are the result of rewriting software. Apple's software rewrites have introduced very little tangible benefit to the end customer while creating lots of software gremlins which are very annoying to them. Worse, focussing engineering resources on rewriting existing apps in Swift vs pushing the apps forward in terms of UX and features have allowed competition to catch up and surpass Apple in several areas that do matter to customers.
In hindsight, there will be a lingering question of if it would have been better for Apple to have continued to evolve Objective-C further in ways that could have provided similar technical benefits to Swift's introduction. At best the shift to Swift will have been seen as a necessary evil that exposed Apple's flanks. At worst, it will have been considered an unnecessary technical exercise that may have been started as a way to retain top technical talent, but even failed long-term in that respect.
Swift isn't alone in this respect. I think TypeScript is another example of a language which started out claiming to offer a better experience than Javascript only to become very complex. I'm sure that this added complexity helps some programmers some of the time. But just like CISC was a dead end and all computer chips are essentially RISC-based today, I suspect the pendulum may have swung too far in terms of adding features to some of these developer-friendly languages.
But, it's a contrarian view for a reason. I'm just somebody who fell in love with the simplicity of Objective-C almost 20 years ago, before the iPhone was a thing. So I may be looking back at things with rose tinted glasses.
However, it is far easier to read and learn than objective-c. All of our new software is written in Swift and we will never go back to objective-c.
Specialized training, certifications and real world experience are a better use of time and money.
In any field, or just for people that want to develop software?
I’m only familiar with the tech industry (software, marketing, design, etc.).
(it seems likely true, and with a success rate like that, improvements rather than migration of existing codebases would make sense. just keen to find some supporting success stories :) I found some cfengine ASAN examples but nothing hugely conclusive yet)
https://static.googleusercontent.com/media/research.google.c...