I would say that working as a programmer in a corporate environment is a bit similar to being paid to be a novel writer by people who don't know how to read, but absolutely want to tell you how to do your job properly.
Readit NewsDead Comment
ant1oz commented on Ask HN: What are your unpopular opinions about programming? · Posted by u/polygot
ant1oz commented on Ask HN: AI innovation outside big tech is over. Debate me · Posted by u/carlosfm
Totally agree with you.
But do we really need AI?
ant1oz commented on Ask HN: What does the world need from software engineers now? · Posted by u/bosch_mind
I asked myself the exact same question few years back, and I came up with an open creative library.
Https://datapond.earth
Oh my god, this guy is the ultimate troll,!!!
Listen, have you ever observed a troll writing a book?
Really? Currency is a scam. You get paid in paper, pay taxes on it, which gets stolen( sorry in edged) in corrupted corps, with a debt system where you are just a slave of your mortgage - unless you're a clever troll, and you bought 10btc 10 years ago, write a book to put the price down, while at the same time, being the most biased possible to trigger HN readers in the hope of getting a Google page rank.... Pathetic.
ant1oz commented on The art of knowing when to quit blog.jim-nielsen.com/2023... · Posted by u/PebblesRox
As a contractor choosing max 3 months contract after more than a dozens of quits.
In my experience, 95% of tech team are disfunctional beyond repair. It pisses me off everytime, and I chose to let it go, stopping the energy hemoragy, and I usually take 2-3 months off, recharge. Now it's been 18 months, no income, enjoying life in SEA. At the end of the day, month, year, decade, I own less, but my life is much more interesting than dealing with mediocre people who knows how to fake it very well, knowing they'll never make it, happy to take the pay check.
ant1oz commented on Ask HN: Has anyone managed to find enjoyment in their work after burnout? · Posted by u/dotdashdashdash
Take long holidays. 6 months minimum traveling around.
if you have a family, or a tight mortgage - I'm sorry for you. As I don't have a straight answer. but 6 months away from keyboard is a strict minimum.
It worked for me every time.
I'm truly saddened to hear that this has been your experience throughout your career so far. It is not a universal experience. I hope you find a better managed shop soon that recognizes that it's easier to teach folks a tech stack than to teach someone to be a decent (or honest) person.
Too many tech shops sabotage their culture and dozens of potentially great contributors in order to keep a few (or one) toxic contributors that the powers that be erroneously believe are irreplaceable.
Anyone can be a 10x developer when you sabotage the well-being and productivity of those around you.
Well said.
I would also add that it is perfectly fine to have a list of red flags, and it is perfect fine to define your own bondaries.
Graphql is a red flag for me too, as well is React and node.js, and even git to some extend.
I love simplicity when designing web apps, their backend, their frontend and the deployment process in between.
Although the tech is old , I came up that vue3+pouchdb+quasar is an amazing combination for a stable replicable dev environment, pwa, supports offline usage, and introduces possible p2p replication between browser's pouchdb instances trough webrtc.
React , imo, is a good over engineered library suffering from fragmentation. Angular is less fragmented, and Vue is the most elegant, performant and versatile of the 3. Good Devs choose Vue after having worked with both react and angular. React Dev never tried Vue, nor Angular Dev try React. Vue Dev usually know all 3.
Having a red flag like graphql can tell a lot about technical overview and experience in failure.
Graphql solves a caching issue that Facebook has. Makes the frontend team life easy, making the backend team life hell , big big hello. Scope changes in the backend are terrible.
Unless your team is engineered driven, and engineers take tech decision, and setup the sprints, going graphql in the backend is a recipe for disaster.
From a management perspective, the fiction of the full stack developer that is equally skilled at everything is the easiest. You stick with that until you complicate your architecture (wisely or not) to the point where having specialists outweighs having to manage multiples queues of work and dependencies.
Worse approach imo.
Nowadays a full stack dev is an intermediate Fe dev, with junior backend skills. He will make your backend un-maintainable. Get a proper master on a proper contract rate to design your architecture.