This isn’t an answer so much as it is thought flow on project programming. With experience this becomes faster and you can of course re-use code with a little bit of tweaking across many projects. Instead of making a mess and confusing forward and backward iterations of your true project, you step outside to “test” or “play” with several things in a manageable way. This same methodology can be applied to anything you code. Once I was happy (comfortable) with it, it was much more efficient and less troublesome to build it into the overall application. On a clean slate a took a much smaller “dummy” data set and simply developed the system to grab the data, make the variable amount of selection lists (of variable length), and handle the list selection and potential user errors. I needed to generate a variable amount of selection lists from this data (in a separate pop up form). Your stub is very precise and only deals with the part you are messing around with, once you are comfortable you incorporate it into your project with scale-ability.Ī recent example of this is I had to process a large data set pulled from a database. You have your project, but in order to trial and master a certain concept you build a stub or mini-project that is less complex and usually has less data. I will give you an example from programming in other languages for other projects. I concur with that most projects (web or not), 80% of the time dedicated generates the framing and functionality, another 20% for tuning and aesthetics. Maybe it’s chrome, I’ll have to try another question seems a little wide open. And that’s if you’re coding from scratch or utilizing a framework or a CMS or anything really.īy the way, is it just me or can you guys not collapse the employee bios once you’ve expanded them (by clicking “Read Bio”)? I thought it was a neat way to do them but soon realized there’s no X or close link or clicking a second time on the screen to undo the overlay. It becomes like muscle memory and then it goes faster. Practice is key and knowing the languages/tools you’re using. We can have a page shift and adapt in ways that would take alot of time and tweaking to pull off (and probably some scripting too in some cases). That’s why I’m so dang excited about CSS Grids becoming more and more standardized. If you start out building fluidly you’ll have a bit of an easier time, and again it seriously depends on the layout. If you’re not using a framework, like myself, depending on how complex the layout is, making sure everything looks and acts correctly on desktop all the way down to mobile on as many browsers as possible is what for me takes the most time. (Are you using a framework like Bootstrap? Or are you coding everything from scratch?) To mirror everyone, it really does depend on some factors:ī.) The scope of the project (Is it one page? Fifty pages? Does it require a lot of interactive features like forms, sliders, or eCommerce? Is the design itself complicated?)Ĭ.) What you’re using to build it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |