HN user

lucidone

702 karma
Posts3
Comments121
View on HN

I wouldn't mind RTO so much if the cities where most tech jobs are were affordable. I'd rather be a millwright in my middle-of-nowhere mining town with a 10 minute commute in a 250k house versus a software developer with an hour long commute and a million dollar mortgage in big-metropolis. For now, I am making hay while the sun is shining and getting the best of both worlds while squirreling away as much cash as possible.

They should have leaned into becoming a developer community (the developer community) instead of focusing on Q&A. StackOverflow jobs were a great resource. Add an ad-hoc discussion forum and chat and it would have be great, like the modern IRC.

Grass is greener and so forth but as a Canadian I find our current government paternalistic, pandering, reactive, and stifling. Not every problem should be solved by the sledgehammer of our public service, regulation, and bureaucracy, all of which are highly inefficient and wasteful. It's tax season - I pay nearly half my wages to the government in income tax - all so they can redistribute it to those who they deem worthy and unworthy (similar how to they might deem some content harmful and other content unharmful). Let me make my own decisions!

This is because of Wordpress. Wordpress work pays less than application development typically. Writing an application with Symfony or Laravel pays market rate for an equivalent dev in your ecosystem of choice (Rails, Django, whatever).

Most applications that would leverage this (e.g. server-side rendered Rails or Laravel or Django) already have those templates as partials for their views, so leveraging the functionality is trivial.

Front end development doesn't have to be awful, particularly with how much JavaScript the language has improved alongside browser APIs. React made sense at one point because the abstractions it employed were common in other contexts: lifecycle events (intentionally avoiding the "hook" word here) are present pretty much everywhere in programming abstractions (on initialization, on deinitialization, on update, and so forth). These were aptly named "onComponentThing"s and grokable.

Hooks, and particularly useEffect, ruined it for me. I have given up trying to understand why changing button states or presenting modals has become so obtuse and frustrating. I don't care about updating my react-router and rewriting it again for the third or fourth or whatever time. I don't want another new testing library, another new "best practice", or another repeated mistake in the reinventing-the-wheel-cycle the React community seems obsessed with.

It's all so exhausting. I write Rails now with erb templates and some dumb javascript to toggle modals and change button colours. It's not cool but at least I can understand it six months later.

For some reason rich people assume their riches makes them wise. Humanity hasn't changed much (at all) since culture was recorded. Read philosophers if you want philosophy - Andreessen is a (poor) sophist and he wants to sell you something.

Haven't ever used Rust and probably won't. Regardless, the melodramatic cliquey "I'm leaving the project" bluster as of late reminds me of my 14 year old self on various vbulletin forums and grants me conviction avoiding adopting this language and its ecosystem. I prefer the tools I use for building businesses to be administered by adults.

American tech workers were really lucky and still are lucky. I envy their salaries even in the midst of the current "tech winter". North of the border we are paid a hefty discount - probably why we're employed at all - with income tax and costs of housing eating into the savings we could have. Still enough to sock away a bit every month, but it feels like swimming upstream sometimes.

Companies generally exist to make money. Law and medicine are fields I personally do not want optimized for profits. I believe a better approach to be making governments more efficient and more aligned with the interests of their constituents (e.g., rewards for meeting targets that indicate a benefit to society - improving gdp, reducing health care spend, reducing criminal recidivism, whatever).

The comment about healthcare (life-altering health outcomes at play) interviewing being less of a rigorous process than screening the devs for icanhazcheeseburger is spot on. What the fuck is wrong with us?

Wondering if HN can give me a hand. Been trying to segue from dev to devops (or platform eng) and certs seem like a good way to indicate interest and some level of competency in lieu of job experience. Had devops interviews before any nobody wants to take a chance on me or feel like it'll cause problems since I am mid career as a dev. What are my avenues if not certs to get my foot in the door? Targeting AWS. Have a dev blog and github with projects.

From a developer perspective, trying migrate a behemoth of a salesforce instance to their new tooling (Salesforce DX) in order to introduce version control and pipeline checks has been an absolutely horrible experience.

I don't think it's a problem necessarily. "unless" is more obvious to me since since it visually stands out more than "if !required_thing" while I'm casually scanning the code. So, in practice, it acts as an indication from the author of the code to the reader that "this line of code is a guard since we're using an unless".

I'm not a very experienced Ruby developer but RuboCop does a pretty good job at guiding and teaching you to use `unless` as a guard in method definitions, e.g.:

  def my_method(required_thing)
    raise 'required_thing is required' unless required_thing.present?
    
    ...
  end
In practice, this hasn't been as issue as a consequence of the tooling and ecosystem around Ruby.