Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
greenowl
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
5 ms
·
31.
▲
by
greenowl
1mo ago
and much better franchise
32.
▲
by
greenowl
1mo ago
time to play ping pong till it comes back up
33.
▲
by
greenowl
1mo ago
Many companies already found a better way - they stopped interviewing. You don't need to interview anyone because there aren't any jobs available. If there happen to be any open roles typically they are not advertised and filled
34.
▲
by
greenowl
1mo ago
Not to rain on anyone's parade but I find it strange how excited and giddy people on HN get for any new X.X model releases. Pumping it straight to the top, clamoring to use it, check and compare benchmarks, bragging about it being you
35.
▲
by
greenowl
1mo ago
Cut them a break. They are trying to IPO soon.
36.
▲
by
greenowl
1mo ago
I know of a few software engineers who have stopped using AI beyond using it selectively as a search / troubleshooting / stack overflow replacement. If you are taking steps to protect your brain maybe in a way you are also protect
37.
▲
by
greenowl
1mo ago
Once you let AI into a large codebase there's no going back. It's a virus that slowly takes over.
38.
▲
by
greenowl
1mo ago
Beyond "branding", I don't mind this general direction. There absolutely should be a fool proof undefeatable mechanism that identifies or watermarks code that was completely LLM generated. If you use LLMs, own it.
39.
▲
by
greenowl
1mo ago
I think LLMs make programmers lazy more than anything. And when programmers stop programming for extended periods, they lose their programming skills. No surprise here. Use it or lose it. I think a possible solution on both fronts (maint
40.
▲
by
greenowl
1mo ago
Sounds like you are already on the "right" path? Step 1 is "surrendering" to AI-driven coding. Beyond that, the new competitive edge for developers everywhere is mastering AI tooling for maximum productivity and velocity
41.
▲
by
greenowl
1mo ago
Maybe do some volunteering in the medical / healthcare / care-taking space.
42.
▲
by
greenowl
1mo ago
I committed to the fully agentic approach for a while. No code by hand! Setting aside the "capability" of the tools, I knew it was the wrong direction after a couple months or so in. I specifically remember during a large featur
43.
▲
by
greenowl
1mo ago
We are able to early detect these cancers right now with routine targeted imaging. Perhaps we should be working to solve or improve on the drawbacks associated with doing this, some of which are: CT scans emit ionizing radiation. MRI contr
44.
▲
by
greenowl
1mo ago
FWIW, I worked fully remotely (pre COVID) and my employer at the time was willing to fully cover the costs of renting a coworking space. Though I never specifically asked, I sincerely doubt they would have footed the bill to construct a det
45.
▲
by
greenowl
2mo ago
Stop eating my sesame cake!
46.
▲
by
greenowl
2mo ago
The same exact people that the companies got rid of. The government pays them now instead of their former employer.
47.
▲
by
greenowl
2mo ago
More fearmongering overhyping the technology. The investment bubble MUST continue!
48.
▲
by
greenowl
2mo ago
Still rocking an M1 Air - 2020 build. 8GB ram. No slowdown or deterioration at all. Battery health reports the battery max capacity at 84%. Best computer I've ever owned, by far.
49.
▲
by
greenowl
2mo ago
Stepping back a bit, if you are working remotely that's likely a proxy for an increased likelihood of job loss due to AI. Why start and invest in a construction project for a building that may not be staffed long term? Perhaps renting
50.
▲
by
greenowl
2mo ago
The plus side of all this is that entry level software development jobs are typically pursued by recent college graduates. They are young. While it sucks to have blown a lot of money and accept they've been duped to get a degree in so
51.
▲
by
greenowl
2mo ago
Of course it will. Doesn't matter though. Coding expertise is no longer valuable. What is valuable now is productivity. Which in today's day and age is the ability to quickly and efficiently drive AI. Hence the never-ending gro
52.
▲
by
greenowl
2mo ago
> Eliciting the right requirements and user needs. Creating a sound architecture and design. Validating final product meets the requirements. Ensuring there is good test coverage. Besides your first point, the rest can be delegated to AI
53.
▲
by
greenowl
2mo ago
We've wronged an entire generation by pushing "learn to code".
54.
▲
by
greenowl
2mo ago
Curious what you think your organization's crown jewels actually are? Because, almost certainly, it's not your source code.
55.
▲
by
greenowl
2mo ago
Yeah, no way. I'd move to the middle of nowhere and work multiple jobs on a farm and in construction. Learn how to grow food, and build things. Meet the farmer's daughter, and marry her. Then, buy my own land, grow my own food,
56.
▲
by
greenowl
2mo ago
Worked at multiple startups as an early engineer. A few were successful. One wasn't. A "staff engineer" was not an available position or job title at any of them.
57.
▲
by
greenowl
2mo ago
Most senior level programmers have 2 options. (junior / early-mid level folks may want to consider re-skilling to a different field) 1. Embrace the AI and continue working and earning for as long as you can. Bank as much savings as
58.
▲
by
greenowl
2mo ago
Kind of a silly, borderline delusional premise. Be a "great" dad while also working a full time job? What a huge constraint to operate within.