Remote Work, Salary, and Career Growth: What the Evidence Actually Shows
Start with an honest observation. When you search for concrete, recent evidence on remote work, salary, and career growth, the results are thin. A query of Hacker News stories returns zero hits. The same query on dev.to returns a handful of unrelated posts, the top one being a weekly check in thread about personal wins. That is not a failure of the search. It is the state of the public record on this topic.
The central argument of this note is simple. We should be careful about repeating confident claims on remote work, pay, and growth when the available evidence is this weak. The evidence list here contains no workforce survey, no compensation dataset, and no longitudinal study. It contains one empty Hacker News result and one dev.to result set that does not address the topic at all. Anyone writing a strong conclusion from that would be inventing it.
What the evidence does and does not support
The first source is a Hacker News search API response. It reports zero hits for the topic query and zero total hits, with an empty hit list [0]. Read plainly, this says that at the moment of the query, no recent Hacker News stories matched the search by date. It does not say remote work is declining, that salaries are falling, or that career growth has stopped. It says the search found nothing.
The second source is a dev.to article listing. The top result is a post titled "What was your win this week?!", a community check in about small personal wins from the week [1]. It is not a study of remote work. It is not a salary report. It is not a career growth analysis. Including it here is useful only to show how far the retrieved results sit from the topic.
Why weak evidence matters for developers in Indonesia
Indonesian developers and technology leaders make real decisions with this kind of information. A developer weighing a remote offer against an office role is implicitly comparing pay, progression, and visibility. A team lead setting a compensation band is guessing at market rates. A founder deciding on a distributed team is estimating their talent pool. Each of those choices carries financial and personal weight.
If the public evidence is empty, those decisions rest on anecdotes. An anecdote is not useless, but it is local. One person's remote raise does not describe a market. One company's return to office policy does not describe a trend. Treating a single story as a pattern is how bad compensation decisions get made.
How to read a thin evidence base
- Check the source type. An API response with zero hits is not a finding about the world. It is a finding about the search.
- Separate the query from the conclusion. "No results for this phrase" is not "this thing is not happening."
- Ask what would change your mind. If no data could move your position on remote pay, you are not reasoning, you are repeating.
The reasonable objection
A fair objection is that absence of evidence in one search does not mean the trends are unknown. Compensation data exists in private salary surveys, recruiter databases, and internal HR systems. Remote work research exists in academic and industry reports. That is true, and it is exactly the point. The evidence for these claims lives somewhere else, not in the sources retrieved here. The retrieved sources are too weak to carry the argument, so the honest move is to say so and go find the real data before publishing a conclusion.
One clear thought to end on
Before you repeat a claim about remote work, salary, or career growth, ask where the number came from. If the answer is a search that returned nothing, you do not have a finding. You have a prompt to go get one.