Wes Deviers

Would be interested in your critique on this message I sent back to my son-in-law, a senior QA engineer whose company is drinking deeply of the AI-Will-Fix-Everything koolaid. —- SIL: Can I ask your honest opinion on AI? Where is this going to land? Me: Here’s where I think things are headed. There are a number of firms and individuals who are learning how to properly leverage AI and are doing amazing things with it. Everyone else who is using it are setting themselves up for serious problems, especially since a lot of them won’t recognize those problems until damage has been done. I think general public use of AI is going to run into the “unreliable narrator” pitfall: trust what the AI says and does when the information may be biased, misleading, or just plain wrong. This is not just the hallucination problem; it’s also biased or wrong information getting baked into the LLMs (eg, how much LLM training has been done based on Reddit threads). SIL: Some of my managers seem to ignore things like Skill Atrophy. I had the view that those in senior positions now are ok because they have the experience to help understand how to fix the issues with AI Coding. However, they seem to think those issues are just a matter of training AI to do better. But, skill atrophy is real, developers are writing about it and I know I've read some papers about studies into it. Things like Critical Thinking are decreasing because people rely on AI to do it for them. So I wonder if AI will really overcome these issues and become just as good if not better than humans at this. Are we going to see a takeover of engineering by AI? Me: No, because I think those efforts will lead to massive technical debt and serious maintenance problems. But I fear things will get ugly before then. Look, as it is roughly 2/3rds of software project are late, over budget, underperform, or fail altogether. As an industry, we’re just really bad at large software projects. AI will solve some of those problems at first, or at least appear to, but because of all the human reasons we’re bad at software, I think a lot of firms will end up in a AI legacy tar pit that will be hard to climb out of.

アメリカの友人達へ 今日、初めてブリスケットを食べた。 食べた瞬間、衝撃が走った。荒れ狂うタンパク質の暴風。圧倒的肉の嵐。ニューロンが焼き切れるような強烈なドーパミンが全身を駆け巡った。 一口食べるごとに農耕民族のDNAが書き換えられていく。

Backend development is simple, you just need to learn these HTTP methods Status codes Request headers Response headers Authentication Authorization JWT tokens Session management Cookies OAuth 2.0 API design RESTful APIs GraphQL WebSockets Server-side rendering Database design SQL queries NoSQL databases Database indexing Query optimization ACID properties CAP theorem Normalization Denormalization ORM (Object-Relational Mapping) Connection pooling Transactions Migrations Seeding data Caching strategies Redis Memcached CDN integration Rate limiting Throttling API versioning Middleware Error handling Logging Monitoring Application performance monitoring (APM) Load balancing Horizontal scaling Vertical scaling Microservices architecture Monolithic architecture Service-oriented architecture (SOA) Message queues Pub/Sub patterns Event-driven architecture CQRS pattern Saga pattern API Gateway Service mesh Docker containers Kubernetes orchestration CI/CD pipelines Environment variables Configuration management Secrets management CORS (Cross-Origin Resource Sharing) CSRF protection XSS prevention SQL injection prevention Input validation Output sanitization Password hashing Bcrypt/Argon2 Salt and pepper Two-factor authentication (2FA) Single sign-on (SSO) RBAC (Role-Based Access Control) ABAC (Attribute-Based Access Control) File uploads Streaming data Pagination Filtering and sorting Full-text search Elasticsearch Background jobs Cron jobs Task scheduling Worker processes Async/await patterns Promises Callbacks Thread pools Process management Memory management Garbage collection Performance profiling Benchmarking Testing (unit, integration, E2E) Mocking and stubbing API docs (Swagger/OpenAPI) Postman/Insomnia Version control (Git) Code review practices Debugging techniques Production deployment strategies

I mean this very sincerely: A professor who cannot name a conservative they admire should be fired. They are hired into their position because of their ability to understand, think, and teach. If they don't admire *anyone* who disagrees with them, they have failed.

Hi hello President Trump, Libertarian here I do recall a promise you made to us on day one, you would free Ross. We understand that you’re very busy uninstalling communism from our great country, so a day 2 pardon is acceptable. Looking forward to it.

Either ctrl-c/ctrl-v works through remote desktop or I just have to retype the whole file manually. There is no in between.

The Baltic Sea is a crocodile eating Finland

I think I can help with this. So it turns out that they are ALL correct. Reason being is those who pronounce it as AppalaChee-aa have inherited more Irish speech patterns either by local regional accent or ancestral roots. Those who pronounce it more Appalakee-aa have inherited more Germanic speech patterns. Likewise, those who say AppalaSEE-uh, are of French decent. As America was settled by massive groups of various countries, the French settled areas like New Orleans and Quebec, so you’ll hear SEE-uh more there because that’s how “chia” is pronounced in French. You and me say Chee-aa, because this area was largely settled by Irish immigrants who intermingled with Native Americans.

Without saying anything, show me how long you’ve been on the internet.

HP is giving out a Passive aggressive level over 9000

There can be only one.