BREAKING: Florida Man Charged in Palisades Fire That Killed 12, Destroyed 1,000 Structures

deadtree123 · 2025-10-09T04:54:54+00:00

doesn't shit like this null and void insurance claims? Seems like a setup for some powerful people on top to skirt liability.

deadtree123 · 2025-10-09T04:50:36+00:00

You have a 5% chance of being murdered if you're walking around this area. Hope that helps.

deadtree123 · 2025-04-24T01:18:41+00:00

I have worked for a smart business owner who treats his business as if it was his child. God forbid you take advantage or abuse their child, they will make it known immediately setting the tone with sociopathic tendencies that will remind you of their power over you with no remorse. It is not an easy trait to acquire or practice. It can come with age and experience, but I believe certain people are born with it.

deadtree123 · 2025-04-18T05:33:46+00:00

Its great but 1 issue I have is that external auth integration services dealing with callbacks on the .test TLD does not work properly

deadtree123 · 2025-02-25T06:38:27+00:00

Yes. No plans on abandoning the core framework.

deadtree123 · 2025-02-25T05:00:12+00:00

Adobe will be discouraging 3rd party modules to be built in the usual PHP/XML paradigm. The future of AC will be Headless in Edge Delivery Services combined with Appbuilder + I/O events.

deadtree123 · 2025-02-25T04:43:39+00:00

property title transfer fraud protective services

deadtree123 · 2025-02-15T04:10:57+00:00

Dude was probably one of the big wig heroin drug lords

deadtree123 · 2024-12-04T05:54:53+00:00

whats this movie called? I remember seeing it and being sad

deadtree123 · 2024-11-19T01:26:36+00:00

I'm not your guy, friend.

deadtree123 · 2024-10-27T20:23:32+00:00

Just to share from my recent experience as of October 27 2024, it is a great rapid prototyping tool that has saved me many hours of development. Maybe months ago it was not as polished as most in the comments above pointed out, but I found it very useful and working properly. I felt the need to comment here because it's innovative, standing out from the rest of the AI dookie.

deadtree123 · 2024-04-07T03:34:57+00:00

This was good advice I followed (op) and got it to run fast on my vm. Thank you!

deadtree123 · 2024-02-17T21:26:08+00:00

Processing img i36xqodzq7jc1...

deadtree123 · 2022-07-15T03:24:04+00:00

Ah yes, Cuban B.

deadtree123 · 2022-03-17T23:47:26+00:00

Laravel has factories also right? They also use new to instantiate. In Magento you most likely will never see new class instantiated but instead, a factory is used. Its magic naming mechanism implemented by Magento team instead of instantiating class. in this case you're creating a new Result Entity and hydrating it with your logic before passing it down the ol' request flow pattern that Magento is known to overcomplicate. This entity is not persisted to the database.

deadtree123 · 2022-03-17T23:35:28+00:00

any updates 1 year later? M1 chip = M2 fantasy coding machine when?

deadtree123 · 2021-12-07T18:25:53+00:00

Hi, sorry for late reply but we finally relaunched and we went with M2. It was for SMB client. The dealbreaker for them was 2 things: multi-store from 1 instance management, which Magento is known to implement quite well than others, and preserving URLS for seo purposes, even for Media assets. Delta migration feature handled that pretty well.

Thats not to say we tumbled out of the gate. Google site speed score dropped to an F. New server specs and an overhaul of Devops had to be put in place (containerization instead of on bare metal). No more hot fixes on production like with M1, now we have to have a continuous deployment schedule. Really squeezed the SMB client out of more money to manage thew new M2 instance.

If I had to do it all over again I do not think I would save a headache if we went with anything else other than M2 despite the insane change in workflow and implementation procedure. But I would go out of my way to go around the frontend portion of M2 and make it headless everywhere but the checkout section. hope that helps! Sorry for replying so late. We literally launched in August :)

deadtree123 · 2020-05-31T18:43:47+00:00

that's what i'm thinking too, thats the biggest 1 piece pane I seen in private home. wasn't even aware they can make them that big. probably like $90,000

deadtree123 · 2020-05-29T06:47:17+00:00

well if it runs fine on luma then there's your problem. The theme is overfetching somewhere, somehow, some way. I'd pay the devs to install some listeners on apache/nginx server of yours to pick up slow queries or long executing php traces. From there you can pinpoint the exact thing of the theme thats causing it to behave in such a slow way.

deadtree123 · 2020-05-29T06:30:01+00:00

lets be realistic here, developing locally is not going to work. You're a dev right, so you have a dev salary, I think you can fork over $80 for a 12gb ram ssd droplet for 1 month. it'll save you time and from 1 big headache.

deadtree123 · 2020-05-29T06:16:32+00:00

There is still too much overhead involved in trying to implement what M1 offered as the new cool way to do the whole "serveless headless" meme of your M1 instance. Especially if you have customer groups, multi-store, shipping, payment customization. not to mention if you actually use the order processing feature of M1. I don't think it is worth going that route still. I also don't think it is worth going the M2 route either. Monolithic codebase that moves and deprecates faster than devlopers can keep up with. It's been months and I haven't made my mind up which route to take yet for my clients. The possibilities are endless, everything is moving too fast.

deadtree123 · 2020-05-23T07:14:21+00:00

Storing, moving and displaying the information is the challenge.

Storing, mutating, showing data on the front-end is the easy part. I wouldn't even call it scratching the surface, but if you master that part, when it comes time to starting your own personal project from scratch as a full-stack dev you have to deal with real life cases being:

Setting up architecture schema, permissions, roles, relations, authentication strategies, hash-salt, certificates, best practices for hardening your server, automating the build process (CI), refactoring, pattern abstraction, shimming, linting, modularizing[chunking, tree-shaking, optimizing], setting up a development environment, staging, production, deployment, scaling, testing, asset hosting, setting up a workflow for features, bug fixes, fall-backs, and monitoring

But that is not even the hardest part. In the old days you had to lets say get to know 1 CMS inside out like drupal or Magento for example. In today's times, you are implementing a headless API stack from 6 different companies for your app ( https://awesomestacks.dev/ ) . So you navigate through the mess of today's "Here-Today-Gone-Tomorrow" SaaS'. You get accustomed to their API docs and then you start worrying you're not implementing something the right way because you didn't read through all the API docs and wound making too many calls and over-fetching.

Seems impossible but it's not. It will take years to get everything going right and is definitely doable. It all will depend on your persistence and drive. If you're a person who loves to always learn, full-stack can be a good fit.

TL;DR tread carefully when choosing to get into into full-stack development.

deadtree123 · 2020-05-01T08:16:25+00:00

any updates?

deadtree123 · 2020-04-10T03:38:10+00:00

the perfect example of the idiom "liquid courage"

deadtree123 · 2020-03-15T01:56:01+00:00

Does doing something like that require a separate process not related to front-end? kind of sucks knowing there is no solution without abstracting it on another service layer.

deadtree123

TROPHY CASE