I would start with asking the backend and front-end developers to learn Laravel and begin using it. All code review should be quite strict. It's going to suck for a while, but that's just the way of it.
Set up two nginx servers. One that's your usual to load Laravel and the other to the legacy nginx server that acts as routing to the legacy application. I would even recommend using OpenResty to help delegate if you need something intelligent.
I would strongly discourage a JS framework that would add increased complexity when you need to keep things focused. The front-end would need to be recorded in Laravel and brought back over in a clean fashion.
Set up a CI and ensure all the code that goes over to Laravel is near 100% tested. Might also be useful to set up a visual regression test tool such as Percy to ensure everything moves over nice. Push for SMACCS and BEM to keep things consistent. Or just make new styling for the new pages to surprise the users.
Rewrites are a trap though and can be painful. Keep a balance of features entering Laravel and the big foxes entering the legacy app. I would recommend RabbitMQ to communicate between them.
I have met a physicist at Perimeter Institute who went all the way to Engineering at Master level and pivoted to Physics PhD. If he could do that, I'm sure you can. I do not remember his name, just his face.
That's not true. KYC is for preventing money laundering and terrorist financing. You do NOT want the RCMP/FBI asking why you permitted terrorists to use your platform.
Having read Three Roads to Quantum Gravity, I think there's a lot of substance there. It's a book made to even include high schoolers, so you have to give it some benefit of the doubt.
As per the philosophy question, neither classical mechanics, relativity, or even death cares about what we think. What matters here is how we perceive and understand a concept.
You can sort of, but you'd need your own server. Google has control over this and I'm not sure if they permit different content for each device. They probably don't.
Given the title, I expected this to be about how PG improved their counting. This is not what it was about.
I remember working over half a billion records and having problems when I needed a count. I used count(id) but that was mainly from internet mantra. I did not see an improvement. Using Citus gave me a significant improvement from 7 minutes to 1. And that was just a single coordinator, two workers on the same host. It could become much much better.
If the data is very stagnant and writes are very low the triggers are great. Usually the "close enough" with pages is good if you have over 100k since paging - please correct me if I'm wrong - is sometimes 1k off.
My preference is Citus as a catch all, but a trigger, a Redis cache managed at the app level, or using page counts are all . really useful for stickier situations.
I remember being 10 and seeing my dog Moglee crawl up a 150m driveway to see his family after being hit by a truck. I remember the blood from his mouth and how much he wanted to be with his family. It was 2 days after Christmas.
Recently my old cat Jackie passed away. The moment I saw her not pee in the litter box but instead leave tiny droplets on the floor, I knew it was time to start planning for what the next few hours were going to be like. She was deaf, blind, failed kidney, two times underweight, and a tumor in her mouth. Her inability to eat or relieve herself had peaked. In the next four hours she was euthanized.
There's many instances throughout life that you know there's nothing you can do.
This doctor was right, your everything isn't always to spend moments with doctors. Sometimes it's to make the final moments worth it. I wasn't with Moglee. No one was. I was with Jackie, but the vet talked me out of getting antibiotics so she could eat instead of starving to death.
- Budget to be able to buy lattes. The inflation and results from $100 a month may be better spent frivolously than conserved. In other words, budget for frivolous expenses.
- Don't spend money on this stuff if you've got bigger problems.
My opinion:
I mean... It's a drink. I'd recommend Tim's instead of Starbucks if money is tight. As a person who spent two years homeless, this stuff is helpful for mental health. Being able to have less worries than more worries is important.
Don't forget the old 50/30/20 rule. 50% on needs, 30% on wants, 20% on savings. Recalculate that not to your needs or wants, but how often your unemployed and if that number is more than 20% a year you should increase savings to cover that as well. Then recalculate needs, review on current bills, and rebalance and so on.
Also keep a month or two of cash reserves for emergencies.
That's certainly a problem. My grandfather was a man who was tasked with killing spies, knew three languages, and out of all of this, I cannot even get him to talk about privacy or security. It appears even he was taught just to shut down on it and say nothing; even on your practices. All the while he taught child soldiers to become child assassin's for the US military.
If you're a security person, I suspect his recommendation would be - even though he doesn't understand IT and tech - to say you don't even understand how SSH works or can't tell the difference between encryption and hashing.
2019 appears to have lots of students who, although always on their phone, a good bunch don't have Facebook and consider it outdated. Instagram is the new Facebook.
Set up two nginx servers. One that's your usual to load Laravel and the other to the legacy nginx server that acts as routing to the legacy application. I would even recommend using OpenResty to help delegate if you need something intelligent.
I would strongly discourage a JS framework that would add increased complexity when you need to keep things focused. The front-end would need to be recorded in Laravel and brought back over in a clean fashion.
Set up a CI and ensure all the code that goes over to Laravel is near 100% tested. Might also be useful to set up a visual regression test tool such as Percy to ensure everything moves over nice. Push for SMACCS and BEM to keep things consistent. Or just make new styling for the new pages to surprise the users.
Rewrites are a trap though and can be painful. Keep a balance of features entering Laravel and the big foxes entering the legacy app. I would recommend RabbitMQ to communicate between them.