futureproofd

Sometimes, yes. Other times, no. It depends who's leveraging the technology to write these things. Though even in the positive outcome cases, the volume alone is suffocating. My brain doesn't have time to commit all of it.

I've noticed early into AI adoption in the workplace that some colleagues took advantage of the technology by appearing to be hyper-proactive; New TODs weekly, fresh new refactoring ideas, novel ways to solve age-old problems with shiny new algorithms. Fast-forward to today, and this is occurring two-fold. Not only are they trying to appear more proactive, combining this with the fear of AI layoffs, they're creating solutions to problems before the problem has even been fully defined.

For example, I was tasked to look into a company-wide solution for a particular architectural problem. I thought delivering a sound solution would give me some kudos, alas, I wasn't fast enough. An intern had already figured it out and wrote a TOD. I find myself too tired to compete.

It's as if what William Gibson wrote about in Idoru has already become a reality. Soon we will see celebrity AI gossip.

Large institutional landlords use Equifax data, TWN, and other 3rd party financial tracking systems to dynamically price renters across the board; new rentals, security deposit, renewals, etc. These are pricing strategies insurance companies use to their advantage, often partnering with landlords to ensure they're getting risk-reduced renters.

Here in Ontario at least, when you transfer ownership of a bike, you have to get it certified for safety. In my case, the bike was an '81 xs400 which required a fork seal replacement and new front tire (due to side wall damage). With parts and labour I paid approximately $500. Fair enough.

Now, if he had recommended a full carb clean and battery replacement, of course that would bring the total to over $1000. Those recommendations are optional though, and your bike can live without them (if you enjoy using the kickstarter constantly ;)

I'm currently enjoying Zero to Production in Rust. It assumes you already have some experience building production-ready systems, and applies rust-specific syntax and concepts to that. As a complete beginner with the language and having read "the book", I find this to be a good resource to apply the book's concepts to real-world scenarios.

Personally, I take it seriously and I think that we at least have the opportunity to make our concerns known here as well.

To boil down my job title would reduce me to a computer programmer. I'm fine with that and it's what I tell to people I meet. In the industry though, it's another story, because we have to play the game in order to succeed. The result of this is that everyone on my team is a senior software person, while I reside in North America, and them, all overseas. You can imagine the pay-gap.

So where does this put me as the more experienced person on the team, getting paid double the salary of those who share the same job title? As the organization expands and goes through its cost cutting phases, I imagine that spot is directly in the sights of, well a coat saving opportunity. Am I paranoid? Maybe.

I think the intention was to spark conversation loosely around SPAs vs SSR. It seems we're at yet another turning point and frankly, I'm enjoying the debate.

It's nice to read that someone else has had a positive experience with the zero2prod book. I'm working my way through it and my impression so far (even after reading the official "book") is that Rust is hard; I enjoy the challenges and the eventual realizations, but working my way through some of the chapters that involve implementations, traits, and macros makes me wonder: Would I actually be able to do this myself in a reasonable amount of time, in a professional setting?

It's actually quite simple even without using some of the advanced features: What I do is create a directory structure for each domain as I explore them. I.e.

Toplevel: - Work -- Job A: -- Daily notes -- Services -- Auth --- overview --- login flow -- Client -- Logger -- Job B: -- Daily notes -- Architecture -- node -- react -- etc

(edit: sorry about the formatting)

As the scope of your work expands, you add another sub-directory or file where necessary. Once it starts to grow in size, you can start making insightful connections via [[keyword]].

Furthermore, you can pretty much take this knowledge base with you, wherever you go, by uploading the vault file to your google drive and accessing it locally via SMB. Automatic save/backup.

Do we work for the same company? :P

Confluence has been the bane of my attempts in finding any relevant docs. Which one is the source of truth? Which one was a draft written by an overly eager to make a first impression, new employee (who is no longer with the company)? Don't even get me started on saving meeting notes to confluence.

These days, I maintain my own knowledge base on Obsidian. If there's ever any confusion or request for more information within the company, I copy-pasta the relevant note from my obsidian bank to whomever person or whichever confluence page they deem the source of truth.

I've been considering htmx for some of our more complex forms with a lot of colocated information. One approach I have in mind is using a small frontend state management library like Alpine.js with the htmx alpine-morph plugin.

In short, if a required field in a different section, i.e. used for a "complex calculation" is changed by the user, then we'd pass that flag in part of the POST request to recalculate.

More code results in more bugs. You need to throw money at software developers to build something, anything really. Only then do you hire a 3rd party pen-testing company for a few days. That's the way it works in our shop anyway. It's unfortunate, but sometimes the expected velocity to achieve MVP glosses over best security practices.

I recently moved to a newly built condo in Toronto and there was a special resident onboarding email, which happened to include a promotional offer from Rogers, advertising a rock bottom deal on internet that I couldn't refuse. I later asked the Rogers representative on the phone how they managed to score the deal with the building developer, and he basically told me that they have an ongoing relationship. They basically have the deal made as soon as the project gets off the ground.

They legally have the right of way to build infrastructure to connect to newly developed, last mile locations? Interesting.

Admittedly I scrolled down to find the obligatory archive link to read this for free, but it's got me wondering now, how do the economist and other online publications make money if we can easily circumvent their paywall (assuming this is their main revenue driver)?

This is great, thank you. I love a good music exchange. And the comment below on Adam Curtis leaves me with hours of digging down this particular rabbit hole. Good stuff.

Interesting examples of related art. M.F. also mentions the paintings of Nigel Cooke in one of his writings > https://www.juxtapoz.com/news/paintings-by-nigel-cooke/

One music artist that I've been enjoying listening to lately is Biosphere. Specifically the Substrata album; To me it feels like a foreboding journey of the present with longings of some past.

There's also this common obsession around Burial with music geeks that he (Burial) was so mysterious that no one ever knew who he was, or that he never gave interviews (except to M.F.), which is obviously wrong. There's lots of info on him, similarly to Aphex Twin. I think the lack of media presence is more about intentionally avoiding crap that comes with it.

It's good to see the occasional Mark Fisher thread here. On the topic of Hauntology and lost futures, I think this guy does a great job of explaining it through the analogy of the Fallout videogame series: https://www.youtube.com/watch?v=gSvUqhZcbVg

Analogies through pop-culture is something Mark Fisher also did very well to get his point across, and appeal to a broader audience.

What are the rules / law for identifying an instagram post as an ad? If this isn't enforceable then young people don't stand a chance against the insidious nature of marketing.

In the 90's, "cool-hunters" would hire street promoters to hype brands one-on-one, directly to the consumer. These promoters were often friends of the consumers, who essentially became walking adverts for <insert big brand here>. Sounds a bit like the company "Influenceter". It's always been a goal of advertising to capture the minds of the youth culture. Facebook just does it to scale.

The fact that the messaging was there to begin with is the issue. People assume tech companies are immune from the law based on make believe claims that their ideals allow them to circumvent it.

All these name drops makes me think we should have another "Best Sci-Fi" post/thread. I recall a past HN discussion based on top sci-fi according to reddit, which led me to Greg Egan's Permutation City - one of the best recommendations I've gotten in a while.

Gibson and Stephenson have different styles of writing. The comments throughout this thread are evidence enough. I could see many liking one over the other so I have a hard time taking your recommendation even though I'd like to.

I've also been a developer for almost 10 years without any Computer Science training (aside from my college diploma). I've also felt the same way about not needing any further formal education up until a certain point.

That point is now, and it's partially out of boredom. I've worked with many languages, frameworks, libraries, patterns, and they're all starting to look the same. I've become a master of tools, able to reach for the right tool given a specific scenario, but I'm starting to find I'm lacking a sense of curiosity and depth.

Maybe without a strong foundational knowledge, we'll only ever be users of the tools, and never creators. I feel like I need to start giving back at some point in my career. Maybe it's time to start working on foundations.

Thanks for the response. Right now I'm focused on Javascript professionally (NodeJS for the backend and React on the frontend). I'd say my long term goals are to give back to the community through open source in some capacity.

In particular, I'd like to contribute to a library or a framework so I guess that would mean understanding the reasoning and the fundaments of why/how the library was created. Whether that means understanding design patterns of Javascript specifically or software fundamentals, I'm not sure.

Sorry if this still sounds too broad, but I'm growing quite bored of working as a typical developer and need a bit of guidance.

I'm really digging these days to solidify my foundation of software development so I thought this link might contain some useful information. Perhaps it does, but it seems a little abstract.

Being said, I'd rather get deep into the weeds with some technical summer reading. I'd love to get some recommendations from everyone here if possible.

Would be much appreciated! I don't know if you've heard it before, but Biosphere - Substrata is a fantastic album (possibly for a psychedelic trip as well!)

This is exactly what I've been telling some friends who've been at the same jobs for the past 5 years getting 3% standard raises. They don't even take into account the inflation (which itself may be underestimated). I always tell them they're actually losing money every year by staying at those particular jobs.

Maybe your profile needs some updating. The market is HOT right now.