chocolatemario

It’s hard for me to believe that, unless you’re just doing simple glue work or you’re working in a low stakes environments, anyone is just delegating everything to agents. If you’re working on a migration (common in enterprise infrastructure work), you’re familiar with the needless abstractions, and it’s something you’ve done many times over; agents can certainly expedite change. If you’re building anything with depth and you do not have a clear understanding of the underpinning logic, you’re either very gifted in your ability to reason about abstractions or you’re setting yourself for a failure at some point in the future. You need expertise at some point. Programming/debugging as a means of learning a domain is akin to writing as a means of clarifying your thoughts.

That being said, yea enterprise coding can be extremely mundane and it’s setup for learning it deeply then finding a way to do it faster. I’m likely in the 90% range of my work being done by Claude, but I’m working in a domain I’ve got years of experience with hand coding and stepping through code in my debugger.

I think this latter piece is the challenge I’m struggling with. There is an endless amount of work that can be done at my company but as long as the economy is in a weird spot, I’m being led to believe that ai is making me expendable. This is a consequence of the fact that glue work represents 80% of my output (not value). The other 20% of time at work is exploring ideas without guaranteed results, its aligning stakeholders, its testing feasibility with mvps or experts from another area I need some help with. If glue work represents tangible output and conceptual work is something that may not actually have value my manager wants me to explore it, I’m just a glue guy in enterprise while I’m left chasing the dragon of a cool project for me to really sink my teeth into. That project is just a half baked bad idea from someone disconnected with reality. Glue work is measurable in LoC (however useless a metric it is measurable) and it’s certainly paying the bills.

This just sounds like a low quality bar or PRs that are too wide in large in scope for AI. In any case, it sounds like taking a single stab at it with an LLM and calling it good. I’m not really AI for everything type of dev, but there are some tasks that AI excels at. If you’re doing it for feature work on a high churn product without a tight grip on the reins, I fear for your products future.

Mastodon isn’t particularly good for monetization.

Yea of course. Users of streaming services don’t use those services to prolong the success of the providers yet they continue to buy in for services rendered. I think a truly community driven approach is going to be independent of Reddit as a backbone.

Unfortunately reddit isn't a tech commune. If its intent is to be publicly traded, then it needs to find a way to turn a profit sooner or later.

I do the same except in org mode. I’ll export to markdown as needed but generally publishing documents is a secondary goal to empowering and decreasing the burden on myself.

Design docs for each and every feature has turned out not to scale for my current team. Larger, multi team features demand consolidated documentation, but for internal changes we rely on quick meetings as code reviews. Part of me misses the ceremony of the round table discussions, but the real difficulty is keeping track of why changes happen. Documenting processes and cross cutting concerns is a must have, but keeping track of all changes across quickly moving teams… it’s no surprise so many teams are just rife with tribal knowledge.

My Amazon experience was similar. Especially the lack of coding due to the emphasis on devops/meeting culture. I have since felt that once a product reaches maturity, additional headcount (butts in seats) are operators first and secondly a swarm for something like a broadly scoped breaking change, runtime upgrade or platform migration. There is plenty of fat to trim even in aws despite it being among the more secure jobs to have at the company.

I’ve seen work slow down across a few teams and it just leaves me in a place of boredom and complacency with a major technical itch. Despite this itch looking to be scratched, I cannot seem to find the time/energy to pursue coding regularly outside of work in the limited free time I have. Maybe if I were single, no kids, dogs…

When you say JavaScript, do you mean java? Rust undoubtedly raises the floor which is great, but designing scalable systems that enable new members to ramp up is a timeless skill independent of language.

As someone who isn’t a rust native but an interested outsider, it can obviously be cumbersome to use on my pet projects compared to something like python, js, c# or C. Dealing with references to generically types traits adds a lot of syntactical burden (re: shit for me to type) and defining types and their implementations leaves something to be desired regarding its grammars.

That being said, my toy programs do not require particularly complex types and the rust compiler is nothing short of a brilliant. The book is a surprisingly easy read, the module system is fine, cargo is decent out of the box, and there is an interesting mix of paradigms in the language itself. In my mind, the power of the compiler is certainly the big feature of rust and that compilers input language is decent enough such that I wouldn’t dislike using it as a daily driver.

The light show at the end gave me a chuckle. Pretty fun little puzzle.

I feel that in real terms, you are absolutely correct. Big tech companies consciously over-hire and throw away work with impunity knowing it will not hurt their bottom line. Denouncing employee productivity like this just seems like an excuse to trim some fat indiscriminately during economic downturn instead of attacking the root of the problem as you suggest they should. They obviously should try to fix the wasted work problem, but that is undoubtedly more difficult than overprovisioning your workforce and dialing back during times of economic duress.

I think articles like this just don’t belong on hackernews. This seems like a train of thought turned blog post. Maybe this guy thinks he is a guru, but it seems like it’s simply an attempt to formalize his musings. I’ve no qualms with this as a post, but it’s why I’m on this forum.

I didn’t listen to that episode but I have to imagine that was a leading question.

As a C# developer I could say the same about my experience dealing with my first foray into [insert random language] and my attempt to develop [something with a non-trivial framework].

The issues you had could be attacked by navigating through this section of documentation, diving into the tutorial referenced in the beginning of the Overview section and the subsequent sections: https://docs.microsoft.com/en-us/aspnet/core/web-api/?view=a.... This is not necessarily in defense of c# and dotnet, but this reads like you barely spent any time trying to digest the documentation.

Easy fix, but vimium does not play well with this.

the old monotonically growing reading list. I must figure out a way to organize mine better

This has a limit of 1000 keys, does not handle redriving failed requests and offers no report of the job.

What you could do is use s3's inventory report feature, give the manifest generated to batch operations and handle the delete logic in a lambda. A lifecycle policy with some tagging could also fit your needs here.

Merry Christmas from Seattle.

If you don't know about references, I feel like you shouldn't be touching react. React is quite easy to pickup if you have an understanding of JavaScript and the Dom. The tooling surrounding react is an entirely different story.

I went to college directly out of high school and wasted my parents money. It felt impossible to break this to my family that I was leaving school.

After leaving school, I worked for ~4-5 years before I started taking classes again. After landing my first internship as a developer, I've been working as a developer and completing a CS degree f/t ever since. My parents were sold a lie, but I was a fool to buy into it.

The punchline being that I don't even need the degree to work as a developer. However, the subject matter is enjoyable and it's better to leave some doors open for future options (masters, phd or whatever).

Never forget ZZ. Or, my preferred method, suspend the process for later use.

Both operating systems have there idiosyncrasies, but that should be expected. Both work exceptionally well for development and leisure use. Personally, I prefer a macbook pro, but I've been developing on a windows machine for the last year and have come to enjoy my time with it quite a bit. These higher level issues not relating to the core processes can generally be handled by your own skill as an administrator.

It may support those behaviors under some circumstances. Of course, this is dependent on why you are using it. I've heard of bodybuilders who take it to the extreme and drink diet sodas like water. However, if usage is as benign as some artificial sweetener as opposed to sugar in your coffee, you are really only reaping the advantages of artificial sweetener.