background preloader


Facebook Twitter

#Dossier : Devenir un pro de la com en partant de zéro ! - J'M Entreprendre. On vous le dit et vous le répète, communiquer c’est donner de la visibilité à son projet, le faire exister !

#Dossier : Devenir un pro de la com en partant de zéro ! - J'M Entreprendre

Une idée géniale sans communication, c’est comme un gâteau Prince sans chocolat, ça ne vaut pas grand-chose… Vous vous dites alors certainement : « Oui mais la communication c’est vaste, on est bourré d’infos tout le temps et ça coûte cher… ». Cet article est là pour vous prouver le contraire, vous redonner le sourire et la motivation pour se dire « Je suis prêt à communiquer efficacement et (quasi) gratuitement ». 1ère partie : Un peu de méthodo pour partir sur de bonnes bases… Analyse du contexte Qui sont mes concurrents ? Analyser le contexte dans lequel on évolue revient à faire de la veille pour s’inspirer de ses concurrents, des process qui marchent et pouvoir proposer une communication originale qui va se différencier de celles des autres. #LastuceEn+ : Au fait, un concurrent c’est quoi ? A peu près tout le monde pense savoir ce qu’est un concurrent.

Poser sa problématique. Behind The Scenes of the Web Design Process [INFOGRAPHIC] (click image to enlarge) Share the INFOGRAPHIC On Your Site, Copy The Code Below:

Behind The Scenes of the Web Design Process [INFOGRAPHIC]

Cahier des charges Site Web - TheCodingMachine. Printable Sketch Templates for Wireframing. At the beginning of a web (or application) development project I always create the sketches first.

Printable Sketch Templates for Wireframing

While sketching can be done on a blank paper, it’s much better to use a sketch template. For me that is the best and most productive way to work on and improve my ideas before application development begins (and things get more complicated :-)). This way I won’t pay too much attention to some details that should be taken care of later, but stay focused on general layout and functionality.

3884016462 de68fc6d15 o. Front-End Dev guidelines. Overview This document details the guidelines and standards adhered to by the Creative Technology department at TMW, and all web applications built should take these into consideration.

Front-End Dev guidelines

It is an evolving document and should be reviewed as and when required to keep up with changes in technology and best practice. These guidelines have been compiled looking at various previously written guidelines - credit goes to Isobar and CSS Wizardry both of which have been used as foundations to build upon for this document, and in some sections been directly quoted. Contents All front-end code should display clear separation of presentation, content, and behaviour.Markup should be well formed, semantically correct and generally valid.JavaScript should progressively enhance the experience Use feature detection rather than browser sniffing (edge cases such as performance are acceptable)Gracefully degrade functionality when not present (e.g GPS, box-shadow, forms etc).

What is a Full Stack developer? Is it reasonable to expect mere mortals to have mastery over every facet of the development stack?

What is a Full Stack developer?

Probably not, but Facebook can ask for it. I was told at OSCON by a Facebook employee that they only hire ‘Full Stack’ developers. Well, what does that mean? To me, a Full Stack Developer is someone with familiarity in each layer, if not mastery in many and a genuine interest in all software technology. Good developers who are familiar with the entire stack know how to make life easier for those around them. Server, Network, and Hosting Environment.This involves understanding what can break and why, taking no resource for granted.Appropriate use of the file system, cloud storage, network resources, and an understanding of data redundancy and availability is necessary.How does the application scale given the hardware constraints? Other Pieces of the Puzzle: Ability to write quality unit tests.

What is a Work Breakdown Structure? Examples of a WBS. Written by: Ann Gordon • edited by: Michele McDonough • updated: 10/24/2014 A Work Breakown Structure (WBS) is used for breaking down a project into easily manageable components, or bites.

What is a Work Breakdown Structure? Examples of a WBS

Here we'll break down the process for you, making it easy to use these structures in your project planning. Company owners and project managers use the Work Breakdown Structure (WBS) to make complex projects more manageable. The WBS is designed to help break down a project into manageable chunks that can be effectively estimated and supervised.Some widely used reasons for creating a WBS include:Assists with accurate project organizationHelps with assigning responsibilitiesShows the control points and project milestonesAllows for more accurate estimation of cost, risk and timeHelps explain the project scope to stakeholdersA work breakdown structure is just one of many project management forms. Scrum Task Board. GanttProject: free desktop project management app. What is Incremental model- advantages, disadvantages and when to use it?

In incremental model the whole requirement is divided into various builds.

What is Incremental model- advantages, disadvantages and when to use it?

Multiple development cycles take place here, making the life cycle a “multi-waterfall” cycle. Cycles are divided up into smaller, more easily managed modules. Each module passes through the requirements, design, implementation and testing phases. A working version of software is produced during the first module, so you have working software early on during the software life cycle. Each subsequent release of the module adds function to the previous release. Principles behind the Agile Manifesto.

Dribbble. ODM. Topcoder. CodeChef.