@adyngom
Building M.A.N.T.I.S (mantistech.io) | Angular Google Developer Expert | Talk and Teach about #Angular, #Javascript, #Web Development & Deve
Ady's first interaction with a computer was playing PacMan but he was more interested in knowing how it was built than how much fun it was to play it.
For the past 20 years, Ady has strived in building simple, engaging and very intuitive consumer facing products.
As a JavaScript Teach Lead and UI Architect, he spends a bulk of his time producing intuitive systems that are easy to scale and maintain.
When away from the keyboard, he enjoys the Georgia outdoors with his wife and two daughters.
To him, the unpredictable weather is a known issue that simply adds to the overall charm and he would not have it otherwise.
Nothing here yet.
Thanks for the suggestion. I will definitely try it out and report back. I like the aspect of of creating a custom starter pack. For a current platform we are building, I ended going with Laravel since we have a tight deadline around it and not enough room for experimentation. The side projects will be done in MERN for now but I will stick with "safer" options in the meantime for production.
Hello Joseph Lloyd thanks for the answer. I'm about to finish Brad Traversy's course on Udemy about the MERN stack. It's 11 hours of content and very detailed. It's also making it obvious that it is a very painful process and probably a nightmare to maintain if you are a small team with no dedicated engineer to take care of this side of development. I have setup my first NEXT project this morning - damn that was simple. I have not got to the point of adding middlewares, adding authentication and jwt tokens. I will keep digging and report back. I'm glad though I'm going through the "pains" of MERN since many legacy projects will have it and it will be an easy way to understand and navigate through. I think that will also make me appreciate NEXT more. Heck even MERN.io is suggesting to move there. I will try to build a Help desk knowledge base app with NEXT for an internal app we have at work. Seems like a good place to start and I will report back. I'm sure the #hashnode team has good reasons for migrating. Syed Fazle Rahman please share any previous articles you wrote or resources about why you "sailed" away from it. Cheers
Hello yes. I have left the links in the articles with the stackblitz editor . But if you want to just run the demos you can do this as well: Counter: https://react-tuxbr7.stackblitz.io Vending machine: https://react-ruhwvv.stackblitz.io At this very moment seems like app url as a standalone is having issues on stackblitz
Hello Pawan. Having an "impossible deadline" is an issue that far outweighs any coding style you adopt. As a developer, you invest in your craft to actually make your tasks more manageable. Clean code when executed right, actually speeds up the process of the Software Development Life Cycle (SDLC). Let's see why, your code is easier to read for you and your peers who are suppose to review it before approving it. Once you have solved and abstracted certain functionalities those become reusable bits making subsequent development of similar features a breeze. On top of that your code is easily testable and maintainable so anytime there is an issue it takes a matter of seconds to locate the probable cause. Now of course, like any other craft, it will take time and practice. As I mentioned in the article: "I have honestly started to make that extra “craft” effort in the past few months and I can admit that it was a very, very slow start." And I highly suggest that one starts with small refactors before undertaking a huge and hard to manage switch. We are creatures of habit and making clean code "natural" to us will be like anything else the result of practice and repetition. Hope it helps. Cheers :)
I use actually both in combination with CSS grid usually handling the outer boxes layout and flexbox for the inner boxes. Looking a the percentages on the caniuse.com site they both have a great overall support depending on the browser you are targeting. You can check my recent article here if you want to learn more about CSS Grid - CSS Grid Layout - A "Quick" Overview CSS Grid Flexbox
Hey Joshua, thank you for the comment and I'm happy you like the article. To quickly answer your question, of course don't 'need' to do it with partials but they are great advantages in using that approach. Let me try to give you a quick example as a basic use case. Let's say we have a multiplier function that takes two arguments and returns the product. We will use that as our base function multiply ( x, y ) { return x * y; } Now let's say we have the need to calculate often halves, doubles and triples. Partial function application will allow us to create generic, reusable, predictable and intuitive secondary functions as you can see below const halves = multiply.bind( null , 0.5 ); halves( 2 ); // will output 1 const doubles = multiply.bind( null , 2 ); doubles( 5 ); // will output 10 const triples = multiply.bind( null , 3 ); triples( 27 ); // will output 81 You get the idea. I will take a closer look at your solution here and give you some feedback on it. But in an interview context it might be best to solve against the specs first then propose a better alternative. Let me know what you think. Cheers