Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
vsareto
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
by
vsareto
3y ago
Well if you can't, then I guess we shouldn't be complaining about feeding brains and average employees who just want to follow specs
2.
▲
by
vsareto
3y ago
This just sounds like someone who can't write good specs
3.
▲
by
vsareto
3y ago
It's because defining requirements is someone else's job, so if you get involved, you will be doing part of their job while you might already be working at your capacity. The Agile style user stories that often lack technical deta
4.
▲
by
vsareto
3y ago
How sure are you they are incompetent vs. just not giving any fucks/disconnected from the job and there to get paid (it's objective one after all!) This seems a little inconsistent to me. Is it really their fault if the industry s
5.
▲
by
vsareto
3y ago
> I remembered the account of developers committing bugs so that reviewers were forced to find something instead of just giving the all clear. You'd be better off pair programming everything and forgoing code reviews. Sometimes I th
6.
▲
by
vsareto
3y ago
It would be nice if only the people with real conviction were doing things by choice, but that isn't realistic. Most people are compelled to have a job, and the system has no guarantee of placing you in the job where you best fit. It&#
7.
▲
by
vsareto
3y ago
There's two abuses in this system you have to watch out for: - being presented under-cooked ideas so you do the thinking for them. - too many ideas (which can lead to the first) with an inability to focus There is a feedback loop for t
8.
▲
by
vsareto
3y ago
>Comparison to the rest of the market (on both sides) is the crux here, not being 'honest' or whatever (what does this even mean). Isn't it? That market comparison is fraught with conditions and often only follows ill-defi
9.
▲
by
vsareto
3y ago
They should remove the L4 from the job post title if that's the case, or replace it with (L1 - L7) so it's clear it's for broad levels of experience
10.
▲
by
vsareto
3y ago
How far are they going to go to validate it’s legit if you make one up? But say you don’t want to forge one for just any company because that might not be legal. You could make your own company with a site and make offer letters that way.
11.
▲
by
vsareto
3y ago
Most people don't know what a $400k Security Engineer actually does to warrant that pay because you can probably find a similar job at another company that pays much less and probably makes you work more. I sure as fuck don't and
12.
▲
by
vsareto
3y ago
>The GPTs/GPT Agents and Assistants demos in particular showed that they are a black box within a black box within a black box that you can't port anywhere else. This just rings hollow to me. We lost the fights for database por
13.
▲
by
vsareto
3y ago
You need specific hardware for Win 11. A motherboard for a Ryzen 7 I bought in only 2017 doesn't qualify.
14.
▲
by
vsareto
3y ago
I doubt any military or strategically important applications will be regulated
15.
▲
by
vsareto
3y ago
Better than companies doing their own thing and not having any restrictions or oversight at all. Remember that those companies will get rid of some portion of their workers as soon as they think an AI can do most of that work. Heck, they di
16.
▲
by
vsareto
3y ago
>Your commit message should have a short title explaining the change and the body should go into as much detail as necessary into why the change took place, I can see the what from looking at the diff. That sounds tedious like commenting
17.
▲
by
vsareto
3y ago
If you do it for yourself, that's great, but you should withhold the benefits of that from the company if they aren't going to reward you for being better.
18.
▲
by
vsareto
3y ago
But why should any of us bother picking up new skills and adjusting mindsets if the author has to fight for a raise after saving the company $500k? Secondarily, why should the author continue to fix things like this when they don't ben
19.
▲
by
vsareto
3y ago
My guess is they aren't seeing how much they're going to need for retirement (maybe it's much cheaper in Finland than the US), or have not thought about it, or have accepted/decided that they will work for more of their
20.
▲
by
vsareto
3y ago
The biggest looming factor is that many jobs in the US are at-will employment, so while people can have good intentions and share those with you, the person or company can turn around and fire you for almost any reason. There's no pena
21.
▲
by
vsareto
3y ago
>The trust that’s given to employees will be returned tenfold–or even hundredfold. Everyone wins. I must be a mercenary because that still reads to me as "we can do these things instead of paying you more". In fact, there is no
22.
▲
by
vsareto
3y ago
I wish, but those things are heinously expensive for what you get
23.
▲
by
vsareto
3y ago
>It is a natural consequence of people who only “develop” by gluing things together. God help them if they’d actually have to write some core function themselves. That's on the industry for not training and gating well. It would be
24.
▲
by
vsareto
3y ago
I just don't see it mattering long-term. We bounced back from the dotcom crash to even higher levels. Same with other downturns. The importance of tech hasn't declined any. There are plenty of tech companies to find good jobs at t
25.
▲
by
vsareto
3y ago
A bigger population just hasn't been trained properly. We have no controls for that, so people get lucky with disparate learning being just enough for their first job, then that turns into experience towards the next job. Then they fin
26.
▲
by
vsareto
3y ago
If you can be good at front and back end and keep up with both of them simultaneously, that's great, but: - you spend more time to keep up with both of those sectors compared to dedicated front or back end positions - you context switc
27.
▲
by
vsareto
3y ago
>Instead, many of those functions are performed by software development teams. And they likely won’t be as good as dedicated SRE teams. But few businesses care about that right now considering layoffs. Throwing developers at a problem ev
28.
▲
by
vsareto
3y ago
>I am baffled by my teammates who seem to have no visual awareness of their code. I have somewhat avoided this because it can make you look like you're changing things for no good reason (no easily communicable reason, anyway). I st
29.
▲
by
vsareto
3y ago
>At some point that's going to hurt you in terms of the sharpness of your knowledge and what you can demo/talk about on your successful projects when interviewing. I don't think this is a real problem IMO. If you learned i
30.
▲
by
vsareto
3y ago
>There are some cases where working hard/loyalty/etc can lead to outsized rewards People are so disillusioned to "hard work == comfortable life" that they might not even recognize it when it's real, or be incredi
More ›