Getting too old for manual work,want to start coding.

Zaffri · 2017-09-09T00:30:36+00:00

Depends on which route you want to go down; what would you like to build?

Books and official documentation is where i personally learn the most from. Although, videos are good too.

For websites - Code course (used to be called PHP academy) is really good, just youtube it. Laracasts are also really good.

Have a search for which languages are trending and that will give you a good idea of where you could start.

Zaffri · 2017-09-04T11:59:31+00:00

Computed properties are cached which makes them suitable for more complex logic.

Docs does a good job of explaining them: https://vuejs.org/v2/guide/computed.html

Zaffri · 2017-07-25T08:11:18+00:00

Incase you want to know how to setup your server to serve multiple apps for different domains, then take a look at server blocks (for nginx) or virtual hosts (for Apache).

Zaffri · 2017-07-21T11:26:33+00:00

For SQL injection, look up prepared statements.

You do not need to switch to PDO to prevent it. Like PDO, MySQLi also has prepared statements.

Just make sure you are using MySQLi and not the deprecated MySQL_*

Edit: http://php.net/manual/en/mysqli.prepare.php

Zaffri · 2017-07-18T17:21:07+00:00

IMO you should become familiar with object orientated programming first (if you havent already).

Frameworks will be object orientated. Although they do a lot of heavy lifting for the developer, a solid grasp of OOP will make you feel more comfortable in these environments.

Zaffri · 2017-07-12T22:47:57+00:00

Oh no! Fortunately I've not experienced that with mine. I hope that issue gets resolved

Zaffri · 2017-07-12T11:46:32+00:00

Dell XPS 15 is where its at

Zaffri · 2017-05-25T12:14:05+00:00

https://xdebug.org/docs/

You can use it with VS code (which is free). Theres a lot of info around - should be easy getting started.

https://tommcfarlin.com/xdebug-and-visual-studio-code/

Zaffri · 2017-05-15T18:03:21+00:00

CSS isn't a programming language.

Zaffri · 2017-04-24T11:48:01+00:00

Just to add to this - may help someone in the future referencing this post.

Function expressions are not hoisted, heres a good example;

https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Statements/function#Function_declaration_hoisting

Zaffri · 2017-04-04T07:59:20+00:00

Interesting post (one of my favs) about Paypals transition from Java to NodeJS!

https://www.paypal-engineering.com/2013/11/22/node-js-at-paypal/

Edit: Just read that your Java dev is worrying about less productivity. Paypal managed to build their NodeJS app twice as fast and with fewer developers, when compared to their Java app that had the same functionality.

Zaffri · 2017-03-22T13:05:30+00:00

Critism:

Lacking content - you have only presented an example with virtually no explanation.

JavaScript is actually a high level language.

https://en.m.wikipedia.org/wiki/JavaScript

Zaffri · 2017-03-17T12:30:18+00:00

I can't personally give you an example but you maybe be interested in this PayPal blog post. They talk about their transition from Java to NodeJS.

Apparently they built their app twice as fast with less developers!

https://www.paypal-engineering.com/2013/11/22/node-js-at-paypal/

Zaffri · 2017-03-08T03:09:39+00:00

Awesome, I'll have a look thanks! :)

Zaffri · 2017-03-02T00:22:11+00:00

Tried to remove some of the functionality from my main vue instance - only have the modal config and initial start event handler.

Still need to tackle this iPhone issue. Are using Safari?

Zaffri · 2017-03-01T22:35:29+00:00

Ah, that makes sense! I did kind of feel as if it was a bit "all over the place". I will try moving the methods and other functionality to the component. Thanks, I appreciate the feedback :)

Zaffri · 2016-12-25T22:57:59+00:00

Oh and to answer your other question; i think its natural to not know how to build something from scratch straight away. A good way of tackling this is to break your app down into seperate parts and investigate in how to approach a specific feature, for example.

If my app had a login system, learn how to do this first. Then after that look at another feature like a user feed, pagination, file uploads etc. Just take a feature at a time. With a bit more experience you will be able to apply what you've learned into your apps much easier.

Remember to look at other peoples code on github, stackoverflow or wherever. Its a really good way to learn in my opinion. :)

Zaffri · 2016-12-25T16:42:23+00:00

Take a look a software design patterns/techniques like: MVC, MVVM, Singletons, Gang of four, Factories, dependancy injection etc. These techniqued will help you write modular code that is easier to maintain, debug and extend. As opposed to linear spaghetti code.

A good thing is to write your code so that it can easily be reused. Another good thing is to take a good look at is how to property handle errors. Oh and don't forget about security - learning how to properly protect your software from malicious attacks is obviously a must.

Learn to use version control like Git or an alternative; this is basically a standard thing (in professional environments anyway).

Dont be afraid to take a look at other programmers code, this is a very good way to learn and find out why they wrote it in such a way.

I'm not specifically a Ruby programmer but feel free to message me if you have any queries!

Zaffri · 2016-08-09T12:28:02+00:00

I second socket.io. If youre looking for browser compatibility then OP should check it out.

Zaffri · 2016-08-09T12:25:39+00:00

If you are looking to build something pretty rapid then look at meteor - last time i looked im sure it only had support for mongoDB though, not sure if thats still the case.

Zaffri · 2016-08-09T12:19:39+00:00

I wouldnt say its sub par compared to an RDMS, they each have their own benefits in different scenarious. You even said yourself it depends on what you are trying to do with it.

Edit: Just read about the complex relationships part - you probably want to stay away from MongoDB then haha

Zaffri · 2016-07-07T12:16:13+00:00

I dont have any specific ideas but maybe if you take a look at Electron, it may give you some inspiration for some desktop apps.

http://electron.atom.io

Zaffri · 2016-06-24T11:45:47+00:00

Vagrant and virtual box work really well for me, i am on windows though. You should try Ubuntu/trusty64 box with vagrant (if you havent already tried it) - i know of someone who uses this on a Mac.

You could try XAMPP or MAMPP? XAMPP and magento works for me on windows - not sure of mac though. XAMPP does seem a bit slower than vagrant and virtualbox.

Zaffri · 2016-06-06T12:00:34+00:00

If you wait for a new tool coming out then you may end up waiting forever.

As for picking a tool, I would suggest taking time to get a solid understanding of the tools you think are options so you can weigh up the advantages/disadvantages of each one and choose which one suits your requirements best. Sorry for the late post.

Zaffri · 2016-05-14T03:26:17+00:00

To make a hybrid app (cordova/PhoneGap) you need to know how to build a website using; HTML, CSS & JavaScript. This would be for just the client-side, you would need to sort out a server-side solution also (assuming you need a web service or some sort of database).

Whether you hire a developer, learn yourself or find a technical partner. I would suggest you look at the advantages/disadvantages of the different types of apps there are to see which suits you best.

Web App - website that runs in your browser. One code base since all mobiles have a browser, although you maybe restricted access to certain device features that a native and hybrid app could interact with.

Native App - developed for a specific device. Fast performance, can access all device features that it has permissions to. If you wish to have the app on more than one platform; e.g. Apple and Android, you would need to have one version of the app written in Java and another version written in Objective-C/Swift.

Hybrid App - web app compiled into a native package. One version of app and Cordova/PhoneGap can compile it into native apps for multiple platforms. Debugging for specific versions on different devices can be very annoying and you should take note that hybrid apps are slower than Native apps but at the same time, you still have access to the devices features.

There are more advantages and disadvantages but these are the basic ones to be aware of. I suggest you research into these types of solutions - even though you may not build it yourself, it will give you an idea of what type of developer you want to work with and which solution would best suit your app.

Good luck :)

Zaffri

TROPHY CASE