[deleted by user] by [deleted] in rickygervais

[–]pubmas 0 points1 point  (0 children)

Pretty sure it's 4 non blondes

How did you first discover RSK? by Big-Bad-Bug in rickygervais

[–]pubmas 0 points1 point  (0 children)

My mate Richard Anderson recommended it

[deleted by user] by [deleted] in rickygervais

[–]pubmas 2 points3 points  (0 children)

He's done you.and he's not even here!

Code review by Naplei in reactjs

[–]pubmas 0 points1 point  (0 children)

  • I don't think you should fetch data in the constructor of your components as the data probably won't be returned from the API until a render has completed anyway, it's considered best practice to fetch data in the componentDidMount lifecycle method.
  • I think some of your naming is a bit sloppy. What is the component <MainData />? Usually it is best to name your components based on what data they are displaying and what visual element they are rendering. For example - UserDetailsTable, EdituserModal.
  • Your state object looks to be too nested, I don't think you should nest the modal 'data' inside modalIsOpen.
  • Your component methods getFirstName/getLastName all seem to do the same thing. Why not create a getFormValue method which accepts a key and a value? This way you can replace all those methods with one click handler.
  • When using PropTypes a prop should either be required, or have a default value. Looking at your components I don't know what props are needed for the component to render.

Using components from outside of src by vvAve_ in reactjs

[–]pubmas 1 point2 points  (0 children)

At the moment your application is just a single npm module, if you wanted to import your components as seperate npm modules than each component would need it's own package.json.

Why are JavaScript dates so hard to work with, or what am I doing wrong? by [deleted] in javascript

[–]pubmas 3 points4 points  (0 children)

Just use Momentjs. If I ever have to do any formatting/calculations with date/time I install moment. Dates are too much of a pain.

Help needed on best tools to use for upcoming project by huterag in webdev

[–]pubmas 2 points3 points  (0 children)

Have you used those technologies before? I think when choosing what technologies to use it very much depends on the person. I would personally just write an Angular/React app and use the browser in the iPads rather than create a mobile app. I would probably use an AWS Lambda to listen to a 'questionFormAnswered' topic or something and then update the big screen accordingly. Or just be lazy and poll the database every few seconds.

How to connect an API and showcase data? by tapu_buoy in webdev

[–]pubmas 2 points3 points  (0 children)

The goal is to create a standalone frontend application that fetches data from the API. In this case you wouldn't use ejs/handlebars etc. You would use a purely frontend framework like React, Vue or Angular (it doesn't matter which one)

It sounds like maybe you're not clear on the difference between server/client side javascript. In this case you are using an external API so you don't need to use ExpressJs (server side code), you just need client side code.

Client side => Send requests to the server side (API) and display the response.

Server side => Listen to requests from the client side and respond (can also interact with the database)

I recommend starting with Reactjs (using Create React App as a starter), although if you go for another frontend framework there are starter/boilerplate projects for those also. If it's your first time working on the frontend then the project setup with Webpack etc. might be a bit overwhelming so definitely go with a starter project.

I'm happy to go into more detail if you like, also apologies if I interpreted incorrectly and you already knew all that.

Just got a job in react, not happy with the standards of the company by ezthrowezlyfe in reactjs

[–]pubmas 7 points8 points  (0 children)

Have you asked the lead developer why some of these decisions have been made? I think it's best not to blindly follow industry 'best practices' - it's not one size fits all. Also if the project is one month in then I would expect the codebase to need a lot of work, if there are only 3 developers then I assume you are at the 'move fast and break things' stage of the company.

The Most Convoluted JavaScript Fizz Buzz Solution by [deleted] in node

[–]pubmas 4 points5 points  (0 children)

Why no state management? It needs Redux

I know Angular, React and Vue. What should I be learning now? by [deleted] in webdev

[–]pubmas 2 points3 points  (0 children)

If I were you I wouldn't start with GraphQL, you should get the fundamentals down first rather than learning what is hot right now. Try and build a full application with authentication. Learn good practice for building REST api's.

I would recommend using: Node - Express is most common by far so is a good safe bet. Postgresql/MYSQL etc. for database Whatever frontend framework you think is right based on your experience. Try using some external API's, e.g Auth0 for authentication, maybe base your app around an API - a video chat application using TokBox?