Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
mbastos
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
5 ms
·
1.
▲
Blocking ChatGPT Isn't Security, It's Just Employee Distrust
(michaelbastos.com)
4 points
by
mbastos
1y ago
|
2 comments
2.
▲
Why Startups Lead in Adopting New AI Developer Tools
(michaelbastos.com)
3 points
by
mbastos
1y ago
|
0 comments
3.
▲
Self-taught engineers often outperform (2024)
(michaelbastos.com)
452 points
by
mbastos
1y ago
|
353 comments
4.
▲
From Vibe Coding to Testing for Juniors
(michaelbastos.com)
4 points
by
mbastos
1y ago
|
0 comments
5.
▲
Layoffs, Automation, and the Road to Reinvention
(michaelbastos.com)
3 points
by
mbastos
1y ago
|
0 comments
6.
▲
The Myth of Endless Dev Jobs
(michaelbastos.com)
5 points
by
mbastos
1y ago
|
2 comments
7.
▲
by
mbastos
1y ago
Honestly, the software job market has always been small. The big lie pushed by tech giants was that everyone should learn to code, not because there were unlimited jobs, but because they wanted a massive talent pool to cherry-pick from. But
8.
▲
Employers Pay Problem-Solvers, Not Encyclopedias
(michaelbastos.com)
5 points
by
mbastos
1y ago
|
1 comments
9.
▲
by
mbastos
1y ago
Jobs aren’t really about what you know, they’re about the problems you can solve. The knowledge matters, sure, but it’s secondary to: can you fix this, and can you do it efficiently enough that it’s worth paying you for it? If you’re a soli
10.
▲
Future-Proofing Junior Devs in the LLM Era
(michaelbastos.com)
4 points
by
mbastos
1y ago
|
1 comments
11.
▲
by
mbastos
1y ago
As someone who makes a living with programming and has a CS degree and have a 14 year old starting college for CS next semester, I just want to say: your juniors shouldn’t be discouraged in the field of software engineering. LLM Tools don’t
12.
▲
by
mbastos
1y ago
I love that, yep I think not enough is said about encouraging individual creativity in an organization, if you can pull something off you should be allowed to, at least for as long as the company can afford it.
13.
▲
by
mbastos
1y ago
Good point, I think it makes me somewhat more human that I actually care about my people's personal lives, it's more the military guy in me than the technologist per say but you're right if they don't want to say they sh
14.
▲
Encourage Engineers to Build Side Projects
(michaelbastos.com)
3 points
by
mbastos
1y ago
|
5 comments
15.
▲
by
mbastos
1y ago
I had someone tell me the other day that they don’t like it when their employees work on side projects. I actually encourage my team to work on side projects in their free time of course, even if those projects may eventually lead them else
16.
▲
Three Decades of Software Execution over Dogma
(michaelbastos.com)
4 points
by
mbastos
1y ago
|
1 comments
17.
▲
by
mbastos
1y ago
Been doing this kind of work since the 90s, and if there’s one thing I’ve learned, it’s that there’s never been a shortage of hot takes on what makes a “real” engineer. I was self-taught for my first decade, then got my CS degree while work
18.
▲
Automating Dependabot PR Merges with CI/CD
(michaelbastos.com)
5 points
by
mbastos
1y ago
|
1 comments
19.
▲
by
mbastos
1y ago
Automatically merge Dependabot pull requests after your CI workflow succeeds.
20.
▲
Why the Tech Debt vs. Tech Asset Metaphor Still Holds
(michaelbastos.com)
6 points
by
mbastos
1y ago
|
2 comments
21.
▲
by
mbastos
1y ago
We all talk about “moving fast” and “shipping features,” but who picks up the tab for those shortcuts? In Part 2 of our series on Technical Debt vs. Technical Assets, we tackle the pushback head-on: • Why the true “lender” is your future se
22.
▲
Automating Weekly Releases with GitHub Actions
(michaelbastos.com)
3 points
by
mbastos
1y ago
|
1 comments
23.
▲
by
mbastos
1y ago
I just published a deep‑dive on how a GitHub Actions workflow can cut, tag, and publish a fresh release every single week, no matter whether you’re running on Python, Go, React, or a poly‑glot monorepo. Here’s the gist of what the post cove
24.
▲
Technical debt vs. technical assets: What's the difference?
(liblab.com)
41 points
by
mbastos
2y ago
|
40 comments
25.
▲
by
mbastos
2y ago
Some people see technical debt as a list of missing features, but it should be a list of the problems that you know you have to vs want to solve. The list can vary but should include known bugs and errors in your code. It should also includ
26.
▲
The Case for the Freedom of a Machine to Learn
(michaelbastos.com)
1 points
by
mbastos
3y ago
|
0 comments
27.
▲
Accruing Technical Assets vs. Paying Off Technical Debt
(blog.liblab.com)
2 points
by
mbastos
3y ago
|
0 comments
28.
▲
by
mbastos
3y ago
These were all valuable marketing approaches to take a decade or more ago so the reason why people are still doing it isn’t ignorance because they did once work very well once. The real reason is complacency and or an inability to change ta
29.
▲
Perilous Pitfalls of a B2B Marketing Budgets
(michaelbastos.com)
2 points
by
mbastos
3y ago
|
1 comments
30.
▲
The problem is not the Office, it's the Commute
(michaelbastos.com)
7 points
by
mbastos
3y ago
|
4 comments
More ›