ant1oz

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.

Totally agree with you.

But do we really need AI?

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.

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.

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.

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.

Have you every tried to version your permissions on Hasura? Not cool. Product polish is amazing, and I love the postgresql integration.

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.

I totally agree, the list of frontend pro is super cool, especially the subscribe real time API, but on the backend, it is a pure nightmare, either using very cutting edge third parties, the authorization is a super big pain in the butt to implement. Cool you got a graph, now you need to make sure only user a can edit row b, there is the shortest path, but the data storage is still centralised.

And I doubt there will ever be any PWA POSSIBLE with graphql, so no offline usage, no local storage , nothing cool toward the web6 decentralised stack.

Yeah, that is sad.

Also, I have noticed a similar correlation in front-end development. There is a consensus amongst recruiters and decision making that react is the best framework around. First it is NOT a framework ( and it would be better if it was one ), second, it was created 8 years ago when js6 wasn't out yet, and it was addressing a problem since then fixed by native js proxies. Most reactjs Devs are junior, or at best intermediate- but junior, really, since they've only worked with on library all their career, calling themselves full stack engineering, but can't write one SQL query, or cannot write anything else than js.

Those communities are very toxic, because the deliver crap code, they think they are super good and very confident about it, and they absolutely love to trash everyone that disagree with them.

See, you got the elitist toxicity, and the noob toxicity. If I had to choose, I'll run with the elites 100%. At least, we get a hope to deliver.

Good one

I don't agree with you.

You can't fix people who cannot learn because of their belief that they already know everything. They will take anything personally that goes in the way of their ego.

For examle, take a react web developer - that only knows React, who think that the React way is the only way, read some blogs written by a junior programmer - and take it as a truth.

2015 : Class components is the React way 2016 : Functional component is the React way - don't use context 2017 : Use Context - that's the React way 2018 : Write CSS in Javascript ... and the list goes on.

Now, good luck explaining to that dev that he basically doesn't knows how to think by himself, and because he thinks that he already knows EVERYTHING - he won't listen - or even learn by his own critical and common sense judgment.

Those type of developers are very toxic, they are VERY vocal about how exceptional they think they are, and they will discard the opinion of anyone better than them - just because it doesn't fit their opinion of themself.

They will stay mediocre - no matter what.

Drop The team, fire everyone, and instead of replacing them with same crap, hire a 5x dev.

So let's say you have 5 crap shit toxic dev, producing spaguetti technical debt - paid 100k/year.

Fire them all, and hire 2 real senior devs at 250k$/y each. And Rewrite the whole stack. It will be faster on the long term.

Also, there is nothing worse for a good dev to work with existing shit code - spend 3 months trying to refactor the code - introduce regression bugs while doing it - and deal with poor technical choices - while at the same time they could rewrite the whole project in a more elegant and stable way in the same amount of time.

It is normal. Frontend code is much harder to test than backend. It also has a visual aspect that backend doesn't have. Your API server doesn't care about cross browser specs, or screen resolution. So when a new iPad comes in, you don't have a new dozen of bugs. Also frontend lacks developers, so it happens that there are plenty of intermediate developers who have a junior level, leading to spaghetti code, and unmaintainable code, and poor management pushing unrealistic deadlines.

That's really cool. Bill is a legend. I've studied with Peter Andrews this year on his farm. Assuming you're in the IT space, Have you found a way to concile work with green regenerative ethics? Still looking on how to find that remote job myself.

Well, I can't stay in a place more than 3 months, because when I walk in, I am the best engineers they ever seen in their lifetime. I can produce code in 10x less than they do, I can replace the BA, while at the same time write specs, I did so many jobs in so many companies, and they don;t know it because I am very very humble, and I don;t like to show off. Then they ask me to do a noob job, or to work on the ugliest piece of spagetti code for few months, or they ask me to work with this Junior dev who got a shit mouth and likes to show off how much younger and vocal he is compared to me, and all of it is making me feeling like I don;t belong there, and that I am not valued for my uncommon talents ( I have 4 ) - and no matter how much effort I put in trying to help them, they won;t note that I can actually be much much more effective at helping them if they stop explaining me how to do my job - or pretending they know how to code - because they wrote a couple of Todo app in React for job interviews.

Just wait for WW3, and wait for all big cities and gvt building who don't care about life and nature gets destroyed. Then you'll have left the country people - the one who know how to survive with land, grow their own food - without lobbies telling them to have their seeds patented in order to sell them - and restore the landscape and the environment. Nothing to do - just wait. If that doesn't happen - then we're all doomed. All we'll have left is Matrix - or Brave new world - no freedom - which will eventually lead to human extinction.

So to make things clear:

A junior is an engineer that has less than 2-3 years experience professionally, and about the same time building and learning how to code by themself on their spare time. An Intermediate engineer is a Junior engineer with a good attitude - that says: I am still earning, and I am humble, and I listen more than I talk. A Senior Engineer Has 10+ years of experience coding, and developing solutions. He has navigated all the corporate BS, politics, and quit several teams of arrogant Junior con artists, or poor project managers - and is tired of all this BS. A real Senior engineer can code the entire solution by himself in 6 months , instead of a team of 5 juniors over 2 years. A real senior engineer - worth 10x the salary of a junior, and at least 5 time the one of his direct supervisor - for one reason:

You can remove everyone in the product team that doesn't have at least 5 years of experience developing code. And you will have better results at delivering your product.

In your case, you probably will end up with zero employee.

Now how much money are you offering this Senior engineer? Will you pay him/her the equivalent of the whole team you just fired? Or just advertise a "competitive (LMAO) " 170k$ package with amazing bonuses...

Which is like what.... only 40% more than the Junior that costs more time than it actually saves?

Maybe start respecting what it means to be a performant senior engineer - Most of them died of depression, burnout - or jumped in the management wagon - because they were too tired of corporate BS and saw no points in even remotely trying to deliver technical solution in an environment where they don't have decision power - while at the same time - nobody in the hierarchy above (and under them) slightly understand the blueprints.

When you realize the value of this rare person, you can think of multiplying the salary package by at least 3.

Then, you can do your interview rounds.

The heck! if I ever want to work in a tech team again - that either will be at a market salary (understand getting paid 5 times less than what I technically worth) for an ethical projects - which is rewarding for my soul and self respect - OR - I will get a 500k$/y for a basic coder job at Google/FB/etc.

Maybe you are not looking for a senior engineer, maybe you are looking for an intermediate one.

If you come to hire a senior engineer at that salary, be warned: he's not a senior.

After reading those comments, I am so glad I did upgrade my old mbp 2015 to a razer laptop. Battery life is horrible, but I don't care.runnkng out of battery in Bed coding, or bar coding forces me to take a pause anyway.

So so glad, running plasma.

It is you.

Vue3 sounds perfect, The major upgrade from v2 is the use of Proxies (https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...), which was missing at the time of Angular v1, which enables native dual binding - and global dual binded deep complex objects.

I personally think React is way over-complicated - and was solving a debugging problem in 2015 - when proxy were not around.

Now look at this vue3 code, and please try to do the same with React

    // file A.js - uses the basic vue proxy implementation

    import {ref} from 'vue';
    export const a = ref([])
    a.value.push(1)

    // 'a' could be a complex library - that is self contained.

    // file B.vue - the actual .vue component

    <template>
       <ul>
        <li v-for="(key, value) in arr">
          {{key}}=>{{value}}
        </li>
      </ul>
      <button @click="add()">Add element</button>
    </template>

    <script>
    import {a} from A.js
    component('hello', {
      setup() {
        const add = () => a.push(a.length+1)
        return {
          arr: a, 
          add
        };
    }
   });

/* No props here, it uses a global object For example, you could have a library that keeps an array of loggedin friends, that connects to websockets - and updates in real time - totally external to the vue UI. All you need is to import it - no need to pass it as a prop - or dependency inject it the angular2+ way */

This is simply not possible to do this with React, instead everything needs to be passed as props, or context. Hooks are even harder than that - as the side effect detection (by design) is dependent on the order of the hook declaration - making the actual reusability of the whole hook ecosystem quite complex and subject to headaches.

Also, keep in mind that Vue3 is now more popular than Angular2, and that it reaches the same number of stars on Github than React - while the number of developers being proficient with Vue is way lower.

In my own personal experience, developing a complex webapp with Vue is way easier than with React - and the developers familiar with it are usually way more experienced than the React uni under-graduate (pretending to be senior full stack developers - because they can write node.js - and spawn a firebase google hosted instance) - because those Vue devs - they know - and because they know - they choose Vue.

Vue4 engine - IMHO - could be written in Rust and compiled to web-assembly - if that makes sense in term of performances.

That was the least technical analysis on web3, just a rant. The guy is like... DAO can only be wrapped in a corporation... Have you heard of Cooperative business structures where each employee have an equal vote and own the business?

Same with Authentication... The idea of web3 is decentralisation... Once the app is operational, there are no more server fees. It's always online - heard of arwave?

Web3 is not crypto man...

Web3 is a design blueprint that is based on decentralised databases, decentralised Auth and decentralised payments and decentralised storage.

It is way harder to implement web3 solutions today than web2. Travel back in 2002 at the early days of web2, and look at how miserable it was to create a webapp.

There are actually no valid point, the guy doesn't even go technical, while talking about a technical subject- and the read is not short.

The concept of web3 is that no more dependencies on AWS, Azure and cloud premises- which are all controlled by govt.

Tor is Free??? What? Please share your server provider... As far as I know, you still have to host your TOR website on a physical server, and pay for it. Ahah. Maybe you talk about access? Well ipfs is free, arwave is free and Ethereum is free then.

This article is a piece of opinionated incompetent crap written in good English.

Location: Australia Remote: Only Remote Not willing to relocate Technologies: GoLang, DB Design & SQL, API design, Javascript, Vue.js, Angular, 20 years experience My CV on linkedin: https://www.linkedin.com/in/antoinelucas1/ Email: [email protected]

Looking for part-time contract, or full time contract short term.

20 years experienced self taught Dev here. And still learning.

The best analogy I can get with programming is to compare it with lawyers.

It takes 7 years to become a lawyer's, and it takes about the same to become a senior programmer.( Assuming 7 years of work experience with a mentor ).

Now, lawyers all have a field, family laws, international laws, constitutional laws, corporate laws. Ask a lawyer who did all his career in corporate law to have a go at a divorce hearing... He will be miserable, and fail.

Programming is similar. You can hear a good lawyer talk and win a case, and it looks easy. But it's not easy.

How many case did he lost before, how many failures.... And now many hours of study did he spent to make sure the argument is a winner?

And where I resonated with in this blog post, is the arrogance and the entitlement of some of those junior programmer, specially in the front-end web industry, who claim to be senior.

I once worked with a 22yo kid who was paid as much as I did, and couldn't write a loop.... He was just a good talker and negociator. 1000$/day to write CSS is really a failure from recruiters and the whole business in general. When juniors think they are senior, they usually take the lead, and the projects goes direction 'fucked'.

And now being good at programming also means being able to get rid of those parasites , which is not eqsy- as their capacity to argue and convince is inversely proportional to their capacity to deliver quality working code.

Yes.

Then you've got lucky, last retro I went.... Managers were present, tech lead sucking leaking asses with their wide ears opened, and best devs leaving to better horizons.

Lul, you are over-estimating managers capabilities to differentiate a 10x developer from a 0.1x developer.

Same story here, on top of that, the tech lead had the most aggressive linting on the planet (no ES class allowed, limited arrow functions, and so on....) I burned bridge, I don't want to have to deal with people that mind fucked limited in their brain where only good code pass this abusive code lint. TS is really cool, forcing the use of `any` is really dumb.

The only downside of burning bridge is that now, I don't have an overview on how bad shape this project is.