mmcnl

73 ms·

901.
by mmcnl 9y ago
This is great, however the real strength of blockchain lies in it being a distributed database. These are all single node examples. Would love to see some examples of a simple network based blockchain
902.
by mmcnl 9y ago
For me, the technology used in projects like these is far more interesting than the end result itself (I'll probably never actually run it, but I took a good look at the source code).
903.
by mmcnl 9y ago
This 100%. The customers are completely out of scope in this article. They are are essential. You're not engineering stuff just because the CEO of the company likes it. You're doing it because you can add value to your customers.
904.
by mmcnl 9y ago
What is your definition of flawed, then? It is the most widely used distribution network of applications. Personally, I would argue the exact opposite. The web in its current state is a brilliant piece of technology that is vastly undervalu
905.
by mmcnl 9y ago
This article addresses web apps at the micro level. Comparing a React based webapp to a 20-year old UI, the end result. It fails to address distribution. How did that UI end op on your display? Through 13 floppy disks. How did the React bas
906.
by mmcnl 9y ago
The problem is that the PIN is always dominant over Face ID or Touch ID. Face ID doesn't work? Use your PIN. What happens if you use local 2FA and your Face ID doesn't work? You can't enter the PIN, because that would effecti
907.
by mmcnl 9y ago
I love this. Pure information without bloat. One of the reaons I love "Teletekst" "teletext"). It also looks very nice, despite the fact that is 30 years old. 101 is news. 818 is domestic football. It's actually sti
908.
by mmcnl 9y ago
Simple and easy to use. Official vue-router and vuex (centralized state management) libraries are excellent.
909.
by mmcnl 9y ago
Nested updates are always a problem, not just with Vue. Just avoid messing with attributes below the first level of nesting.
910.
by mmcnl 9y ago
That is a big incentive for everyone who likes money, not only for services like Lyft and Uber.
911.
by mmcnl 9y ago
This article seems very anecdotal to me, and thus tells me nothing. Jobs come and go. Jobs once held in high regard are now common jobs. Also people nowadays have (good paying) jobs that didn't exist decades ago.
912.
by mmcnl 9y ago
You haven't read the article, apparently. It focuses on Mithril (not React). And Nuxt simply abstracts the build step away server-side, so it's still there.
913.
by mmcnl 9y ago
It is none of their business, but they desperately want a piece of the pie so they brand their phones (and probably sell them at a small discount - this is the value proposition here). Branding also results in shifting responsibilities from
914.
by mmcnl 9y ago
This is simple risk management. The risks are too big that you're paying someone $400/hr without the expected benefits. There's just a too wide margin of error. Pay four people, things even out if and the whole thing just bec
915.
by mmcnl 9y ago
LPT: Don't complain, but suggest improvements. Stop looking at "management" as some evil superpower that can't be reasoned with. They're just people with different responsibilities. Align.
916.
by mmcnl 9y ago
create-react-app and vue-cli are both good tools.
917.
by mmcnl 9y ago
That usually only works well for really small components. Once you're serious about your web app, you'll end up using the whole developmnet Webpack environment in short time anyway.
918.
by mmcnl 9y ago
> There are major state update issues and the team had opted to assign IDs and data to the DOM elements and use those to look up state in the redux store before modifying it. This sounds awful and seems like an anti-pattern. I don'
919.
by mmcnl 9y ago
With PHP you also need to implement a webserver (Apache), so you're one-liner is also actually not a one-liner at all. Also, pick the right tool for the right job. Who writes code these days that silently sit still for a decade? Hardly
920.
by mmcnl 9y ago
A wonderful list of excuses to pay your employees as little as possible. Kudos.
921.
by mmcnl 9y ago
Agreed. The more simple answer is to never commit unfinished or broken code. Inline todo's are a definitive no-go. This implies a lack of control of workload management.
922.
by mmcnl 9y ago
The current state of front-end web development isn't a mess, it's actually the opposite. I would argue it is bleeding edge. If you look at it from an engineering perspective (inside-out), it's probably not the best. But if yo
923.
by mmcnl 9y ago
This might be true, but it is not the best solution. Seperation of duties should be in place here.
924.
by mmcnl 9y ago
This is a signal of short-sighted incompetent management.
925.
by mmcnl 9y ago
People are people indeed, which means people are not companies. The best interest of the person you work for might not (will almost never) be the same as the best interest of the company. Superiors want people who are working hard for them,
926.
by mmcnl 9y ago
Still does not make you able to store apps with a combined size of 1.3GB in the cloud.
927.
by mmcnl 9y ago
I understand what you're saying, but I still fail to see how all of this translates into not being a team player. That really has nothing to do with this at all. If the interviewer still wants a solution based on the facts as they lay
928.
by mmcnl 9y ago
I fail to see why analyzing a problem before solving it somehow translates into "not going to work well with the team". Problem analysis skills are far more valuable than problem solving skills. Anyone can search on Google for a s
929.
by mmcnl 9y ago
And always perform hash verification or decrypting client-side so you can prevent brute-force attacks (purposely slowing down the hash verification or decrypting to 100ms is okayish already).
930.
by mmcnl 9y ago
Well that would be a perfect answer if you ask me.

More ›