austin-cheney

Ever since the first programming language the goal was to make the work easier

The historical evidence disagrees. The point of software is automation and the point of automation is elimination of labor by any means. Nowhere in that is easier.

Clearly developers have forgotten what automation is because the quest for easier satisfies the narcissism of people who lack the ability to see otherwise.

I am looking at the subtitle:

The future of software development will belong to those who can think clearly at scale, maintain durable mental models amid rapid change, and integrate machine-generated output into human-directed intent.

Wasn't this always the case? Maybe I just take this for granted because I am dumb Army guy and this is the only lens through which we dumb Army people see the world.

Whenever the subject of AI comes up in connection to programming it feels like the conversation always misses the human element. When you look at this only in terms of human behavior I am not seeing anything new with AI.

Maybe, its because I write in JavaScript and maybe its different in other areas of programming. In JavaScript it has always been a race to the bottom. The product is never the goal. The goal is always hiring and regarding code as a commodity that is designed to fail elegantly and frequently. So, when I look at AI writing code for developers I can't help but ask: What's different? Isn't that why Angular and React became popular, because they abstract away writing code?

I cannot speak for why everyone in the US buys solar. I can only speak for my local community.

If you want to find locations of grid instability focus on growth, both residential and industrial, that is radically out of scale compared to larger geographic averages. Otherwise, it seems like you are measuring using the wrong trends.

What’s crazy is that the grid instability was there before the explosion of data centers and the primary revenue generator of the much larger geographic region is energy transport/production.

I once had this diff tool that blew up in popularity. It had features users wanted that did not exist before. Its popularity was all word of mouth spreading among developer tools. The real shock was when I joined Bank of America in 2017 and found a ton of people there using it either directly or embedded in some other tool.

I would argue that the valley’s biggest advantages were finance and talent, of which both are squandered for AI.

Meanwhile anybody else can now become the next Silicon Valley by simply replicating what the valley once was and actually shipping original products people actually want.

Grid instability, which includes an increasing frequency of brown outs. It’s the primary reason residential owners are heavily investing in solar panels.

If you don’t know where I live how can you know if my claim is true or not?

I oppose the data centers because they drive up utility costs and contribute to the instability of the local electrical grid. I get pain from them and no benefits. I really don’t want most of the unprofitable AI foolishness that is being forced on us.

The paper costs 6 Euros to access :(

Otherwise, that summary introduces several downstream consequences that are a huge oh shit. I am casually interested in why those downstream consequences vary more for female participants, as compared to males, or if they even vary at all.

I became a father at 24 and had both of my kids before I finished college. I didn't start programming until age 28. I turned out alright, and I am based in America where the costs of childcare and medicine will make you homeless.

If you want to work with cool tech bros who prefer to talk about themselves then don't bother. If you want to get a job at some place more mature then get the cert they require.

Starting a business is hard. Jensen Huang said he probably would not have done had he known how hard it would be. Bill Gates also said working those kinds of hours is not for everyone.

In the end you have to want it. The “it” is not any kind of real success, but rather just doing the work, those thousands of tiny accomplishments that nobody else sees. The work spent toiling away making continuous progress on things you aren’t comfortable with, like sales or finances. It’s hard to claim victory over those things when building the product takes all your time and money. That balance are those many tiny things you have to claim victory over. It never gets easier, but it does get more reassuring as your support system grows.

Good to know our US law makers continue to give Israel billions of dollars to advance ethnic cleansing forthwith.

If Node is your web server then node does have a way to serve the code to the browser... or you could just have node write the stripped code to a file for your other web server. It sounds like you are not even trying to think through this. I recommend putting fingers on keyboard and just trying to find your way through the solution instead of complaining about how impossible life is.

A couple things I have learned from burn out:

* Software, isn’t a profession. A profession is more than just employment. It’s a set of minimal agreed ethical standards that governs conduct, output, and relationships. Education, medicine, the law, the military, and most every industry has this. Software does not have this, so other developers critical of your anti-populist approaches to better performance and lower costs can go fuck themselves.

* The primary goal of software is hiring and employment. If you are an experienced developer who ships completed products then build for yourself first. All be your first client/customer and realize other potential clients/customers are likely not shitty developers whose only concern fear of writing original code.

* Jobs will come and go. Always have a back up plan, both financially and professionally. I have been doing this long enough that my retirement accounts are worth more than I am in every other regard, which is safety net. I also have back up employment with a part time job that is worth as much as being an experienced software team lead.

* I love sharing and writing open source, but many people who write software just expect you to give them all the answers. It feels like there are now people who can build anything and there are people who barely open a code editor without crying. People who cannot receive guidance without first crying about why you didn’t do all the work for them or simply give them all the answers should just be ignored.

* There are great leaders in software, but they seem exceedingly rare. Don’t be hurt when insecure people intentionally destroy your employment. Consider it the expectation of doing this work for a living.

I do, not quite every single day.

It sounds like you would prefer if I just write some code for you instead of doing it yourself. I don't mine doing that. I am willing to advise you with a consultation fee.

Confusing or not it works for me. No compile step and no build step. The application starts up in 0.2 seconds on Linux and about 1.2 seconds on Windows.

Since you need just a little help…

Yes, I push all my TS code through Node for type stripping. No, Node is not executing browser code. No, I am not suggesting Node is running in the browser.

For extra extra extra clarity importing functions in JavaScript does not execute them. They still have to be called for them to execute.

I am still willing to fix your code for a consultation fee.

If you hire me as a consultant I will do it for you at $150 per hour.

You are so thinking about this only from a framework perspective, as if you have no imagination. You can answer all your questions yourself by simply writing the code without a framework. Its not that scary.

It is as simple as I am suggesting, but only if you have actually done it yourself more than once. Whether or not your application is error prone is entirely on how you execute regardless of the tools in your toolbox.

Get the masters. Jobs at Amazon are not immune from layoffs.

Again, I never said Node is did anything for the front end.

I use WebSockets. If the user changes a value you have to send that changed value forward. If the value changes outside the UI you have to send it into the UI.

On application startup I assemble together the various front end files I need and store this in memory as a string. When the server sees a request for the desired page I respond with the desired string.

Since I am not handcuffed by some giant framework I have maximum flexibility to do what makes sense.

That doesn't explain how your front-end TS code is transformed into JS.

Node will do that at run time. Its automatic. Functions do not have to execute to receive this benefit. They just have to be imported. Ensure you are using a very recent version of Node.

I write all my application code in TypeScript, even if it is for the browser. I then import all that code into Node regardless of whether it will execute in Node. All code that will not execute in Node needs to be wrapped in a function for safety, because global references like "document" or "window" will not work in Node.

I am aware and it’s not what I said.

Node strips types on all imported code regardless of where that code executes.

I don't have statistics. My wife works in elementary special education. Previously to her current assignment to a classroom with assigned students she worked across the entirely of a large school system as adviser.

What are you really asking? You use data to populate content or inform your logic.