Thewebcraft's Posts
Nairaland Forum › Thewebcraft's Profile › Thewebcraft's Posts
1 2 3 4 5 6 7 8 9 10 (of 10 pages)
seunthomas:Thats what you think, and thats why most developers cant build their own frameworks. |
bot101:Yeah |
FincoApps:Lolzz.... ![]() |
charliebiz:UI is poor (CSS components they use bootstarp) android 2.2 doesn't full support Css 3, For me its still in beta, Ionic is far better.. |
Djtm:No got it from a friends blog..... |
FincoApps:Hello Boss |
Not everyone is cut out to be a programmer. Sure, anyone can learn how to program, but learning how to program is not the same as making a career out of it. In fact, it’s entirely possible to be a talented coder and still be a mismatch for the career. It sounds strange, I know, but it’s truer than you might think. There’s more to it than the act of coding. You have to consider the entire picture. If you aren’t completely sure that you’re meant to be a programmer, here are some signs that may point you in the right direction. Sign #1: You Lack Experimental Creativity Despite being heavy on the logic, programming is ultimately a creative art. A new program is like a blank canvas and your paintbrushes are your languages, frameworks, libraries, etc. You’re creating something out of nothing and this is a process that hinges on experimental fearlessness. Dogmatic coders will tell you that there’s “one true way” to write good code, but that’s not true at all. Such a statement is as nonsensical as saying there’s only one way to build a house, write a novel, or cook a stew. There are many ways to code software and you should be willing to experiment. Without natural curiosity, you’ll develop tunnel vision and always approach your coding problems from the same angle. At that point, programming becomes rote work and loses much of what makes it rewarding in the first place. Sign #2: You Are Not Self-Driven All good programmers need to be self-driven and there’s no way around this. When you strip away all of the extraneous details, programming is fundamentally repetitive. If you have no personal stake or ambition in the code you write, then you’re just going to be miserable. This is true of any creative endeavor (and no matter what anyone says, programming is creative). Your motivation to write code has to come from within. You have to love the act of coding just as much as the potential for walking away with a final product. If you don’t love the process, you’ll never reach the product. If you wake up in the morning and you don’t feel a burning desire to work on your project, perhaps programming is not the right outlet for you. Sign #3: You Hate Logic Problems Despite being a creative endeavor, programming is more about fixing than it is creating. While other creative outlets do involve a fixing process (such as writers who need to revise their drafts), programming is unique in that most of the problems that pop up are based on logic-based faults. This fixing process, known properly as debugging, is the heart of programming. Are you fascinated by riddles and logic puzzles? Do you have an innate desire to repair that which is broken? And by extension, are you naturally inquisitive about the inner workings of things? You should be able to answer “Yes” to all of the above. Much of the reward in programming comes from fixing bugs. The more complicated the bug, the more rewarding it is when you finally solve it. If you find no satisfaction in this, then programming will be nothing more than an endless string of frustrations. Sign #4: You Can’t Sit For Long Periods The nature of programming requires that you sit in front of a computer for extended lengths of time. You may be able to work around it by building a standing desk but the essence is the same: you’re going to spend a lot of time in front of your computer. There are some concerns when it comes to this kind of computer-related sedentary lifestyle and it can lead to serious health issues if you ignore it for too long. Along similar lines, you may have to wrestle with mental issues like unwanted distractions, cabin fever, and lapses in productivity. Ultimately, the question is: are you comfortable being in front of a computer for most of your day? In fact, comfortable may not be enough; you have to prefer being in front of a computer. If not, productivity and happiness are going to be uphill battles. Sign #5: You Want Normal Work Hours Programming careers fall into one of two types: 1) you work for someone else or 2) you work for yourself. Either way, it’s not uncommon to hear stories of late nights, long coding sessions, and an overall low quality of life. Software development is a deadline-centric industry and deadlines don’t play nicely with traditional 9-to-5 work days. As deadlines loom closer, coding teams often enter a phase of “crunch time” defined by all-nighters. Even when working for yourself, you’ll have to pour in many daily hours if you want to stay ahead of your competition. In addition, programming problems tend to get stuck in your brain and follow you around everywhere you go. You’ll be working through solutions while in the shower, while commuting, and even while lying in bed. Because so much of programming happens in your head, compartmentalization can be difficult if not impossible. If you’re lucky you may be able to find a company that doesn’t do crunch time, but I wouldn’t count on it. Sign #6: You Expect To Get Rich Quick There was a time when software development was a lucrative pursuit. Nowadays, programmers who get rich quick are the exception to the rule. If your primary motivation for being in this industry is to make a lot of money in the shortest amount of time, you’re in for some disappointment. Overnight success stories, such as the popularity of Flappy Bird, can lure us into false expectations and delusional confidence. A lot of people have tried their hand at indie game development in the hopes of striking similar levels of success only to flop and |
charliebiz:Anjular Mobile isn't fully a framework yet... Ionic Is the Best. |
dwebdesign:Thanks |
proxy20:GCM Alone with PHP is easy.... |
dhtml18:Why not .... Creating a plugin that uses GCM, APN and the windows Azure service with php curl is no joke... |
yungcheda:Yes it is, I started because i found it interesting and was passionate about it, I took it seriously building pet projects and it became a skill, now I'm building for Enterprises and client...it is very profitable because its hard to learn, when you can create a product that solves a real problem. The whole point of writing codes for computers is to create solutions and solve problems that is not possible to be solved by humans in an efficient way. It was like this from the first generation of computing devices and it's still the same with today technologies and frameworks. They are all serving this single purpose. Also as soon as you have yielded one or more products that demonstrate something of value that meets someone's need. It can be the need of a small group of people (a company with a job opening where you can demonstrate the coding skills to do the position), or a larger group of people (customers that can all benefit from an app or service you've created). Knowledge is essential, but one or more actual programming products will go a long way in proving your capabilities to those with the money. |
osile2012:Bro since you know php i think you should start with Cordova, build your app with html, css and JavaScript..build the backend with php. He is how it works: Mobile App Connects to Backend and the backend searches the db for the request and brings back the response as json your mobile app gets and displays the json response... e.g lets say i want to search for a product named Gik you will perform a post request to my php script with Ajax e.g htttp://mywebsite.com/myscript.php?product=gik and the response can be: [{"product_id":"1","name":"Gik"}] ..... just use your JavaScript to get the json...... |
My toughest was when i was building a wordpress plugin (My First) for a client.. the plugin notifies all the mobile app users for the blog (through Push Notification) when a new post is made by the admin, it sends the post title, Intro content and comments count.... i didnt shut down my laptop for a week was hibernating.. (If i was my own project its normal) my browser tab(s) on wordpress documentation, google gcm and apple push and windows was more than 40... after the project when i tried shutting down it took 30mins for my pc to shut down.. |
trytillmake:"Although Phonegap does not yet support all the plugins and functions of a native development platform" - 100% Wrong.. Seriously you're speaking like a web designer who just wants to download all the premium templates for free and doesn't want to learn how to code one...... I created an Android Launcher With features like that of Solo, Nova or Go Launcher with widgets and lock screen for my Company tablet, with Cordova a.k.a Phonegap.......... |
FincoApps:It doesn't but its not hard to create one.. |
Emusan:Hello I hope you don't mind send me ur email and I'll forward a real working example, eg u select a state and you see the local government area's in that state in another select box |
godlypaul72:Just ignore him, I'll have to say you ui/ux is very poor, its not about "Nigeria's 1st ever Android Photo Editor" the app has a few basic feature any photo editor can give ..... just work on more features that make it stand out. |
nollyj:This is very important question.. I develop for IOS & andriod @FincoApps is a Blackberry developer. |
larisoft:Yeah |
FincoApps:I know you are talking about developing for Blackberry, When I first published an app two years ago on the Playstore I got 1000+ downloads in a week, On Apple i go twice the downloads. For Blackberry, the two major pluses are: 1. Super stable OS. If you make use of the recommended best practices, you benefit greatly from RIM's solid JVM implementation and OS layer. 2. HUGE user base. Especially if your app is free (or on a freemium model) you have the potential to really benefit from a large user base that's hungry for interesting apps. If you're new to BlackBerry you should expect 2-3 months of just becoming familiar with developing on BlackBerry and overcoming some of the initial hurdles. The huge gap between the touch devices users (eg: Storm, now Torch...) and the trackball devices users (leading by far) was and is still a huge problem. Particularly when it's time to design a convenient UI and UX that will suite both environment. Speaking of code, you need to know your Java. The learning curve and the availability of relevant documentations on the SDK is also lacking compared to Apple's iOS, or Android OS. That's why you don't see much graphic designers with minor coding experience making the leap to BlackBerry Apps development as opposed to iOS and Android. I would prefer building for Blackberry Smartphones (OS 10x). |
FincoApps:Lol...Yes but only when you rely 100% on them, i know a web developer who doesnt know the difference between Css margin, background-color, color and padding but knows all the bootstrap classes A-Z, that's Laziness... |
In my code journeys and programming adventures I’ve encountered many strange foes, and even stranger allies. I’ve identified at least five different kinds of code warriors, some make for wonderful comrades in arms, while others seem to foil my every plan. However they all have their place in the pantheon of software development. Without a healthy mix of these different programming styles you’ll probably find your projects either take too long to complete, are not stable enough or are too perfect for humans to look upon. 1. The duct tape programmer Duct Tape - The code may not be pretty, but damnit, it works! This guy is the foundation of your company. When something goes wrong he will fix it fast and in a way that won’t break again. Of course he doesn’t care about how it looks, ease of use, or any of those other trivial concerns, but he will make it happen, without a bunch of talk or time-wasting nonsense. The best way to use this person is to point at a problem and walk away. 2. The OCD perfectionist programmer Perfectionist - You want to do what to my code? This guy cares about your deadlines or budgets, those are insignificant when compared to the art form that is programming. When you do finally receive the finished product you will have no option but submit to the stunning glory and radiant beauty of perfectly formatted, no, perfectly beautiful code, that is so efficient that anything you would want to do to it would do nothing but defame a masterpiece. He is the only one qualified to work on his code. 3. The anti-programming programmer Anti-Programming - I’m a programmer, damnit. I don’t write code. His world has one simple truth; writing code is bad. If you have to write something then you’re doing it wrong. Someone else has already done the work so just use their code. He will tell you how much faster this development practice is, even though he takes as long or longer than the other programmers. But when you get the project it will only be 20 lines of actual code and will be very easy to read. It may not be very fast, efficient, or forward-compatible, but it will be done with the least effort required. 4. The half-assed programmer Half-assed - What do you want? It works doesn’t it? The guy who couldn’t care less about quality, that’s someone Else's job. He accomplishes the tasks that he’s asked to do, quickly. You may not like his work, the other programmers hate it, but management and the clients love it. As much pain as he will cause you in the future, he is single-handedly keeping your deadlines so you can’t scoff at it (no matter how much you want to). 5. The theoretical programmer Theoretical - Well, that’s a possibility, but in practice this might be a better alternative. This guy is more interested the options than what should be done. He will spend 80% of his time staring blankly at his computer thinking up ways to accomplish a task, 15% of his time complaining about unreasonable deadlines, 4% of his time refining the options, and 1% of his time writing code. When you receive the final work it will always be accompanied by the phrase “if I had more time I could have done this the right way”. Where do you fit? Personally, I’d have to classify myself as the perfectionist. So, which type of programmer are you? Or perhaps you know another programming archetype that is missing from my list? Post a comment below. |
what do you wanna do with your life? You want to rock, naturally! Or at least be a rockstar programmer. It's not a question that typically gets a serious answer, But I think this is a different and more serious class of question, one that deserves real consideration. Not for the interviewer's benefit, but for your own benefit. The "where do you see yourself in five years" question is sort of glib, and most people have a pat answer they give to interviewers. But it does raise some deeper concerns: what is the potential career path for a software developer? Sure, we do this stuff because we love it, and we're very fortunate in that regard. But will you be sitting in front of your computer programming when you're 50? When you're 60? What is the best possible career outcome for a programmer who aspires to be.. well, a programmer? What if I told you, with tongue firmly planted in cheek, that there were Eight Levels of Programmers? 1. Dead Programmer This is the highest level. Your code has survived and transcended your death. You are a part of the permanent historical record of computing. Other programmers study your work and writing. You may have won a Turing Award, or written influential papers, or invented one or more pieces of fundamental technology that have affected the course of programming as we know it. You don't just have a wikipedia entry – there are entire websites dedicated to studying your life and work. Very few programmers ever achieve this level in their own lifetimes. Examples: Dijkstra, Knuth, Kay 2. Successful Programmer Programmers who are both well known and have created entire businesses – perhaps even whole industries – around their code. These programmers have given themselves the real freedom zero: the freedom to decide for themselves what they want to work on. And to share that freedom with their fellow programmers. This is the level to which most programmers should aspire. Getting to this level often depends more on business skills than programming. Examples: Gates, Carmack, DHH 3. Famous Programmer This is also a good place to be, but not unless you also have a day job. You're famous in programming circles. But being famous doesn't necessarily mean you can turn a profit and support yourself. Famous is good, but successful is better. You probably work for a large, well known technology company, an influential small company, or you're a part of a modest startup team. Either way, other programmers have heard of you, and you're having a positive impact on the field. 4. Working Programmer You have a successful career as a software developer. Your skills are always in demand and you never have to look very long or hard to find a great job. Your peers respect you. Every company you work with is improved and enriched in some way by your presence. But where do you go from there? 5. Average Programmer At this level you are a good enough programmer to realize that you're not a great programmer. And you might never be. Talent often has little do do with success. You can be very successful if you have business and people skills. If you are an average programmer but manage to make a living at it then you are talented, just not necessarily at coding. Don't knock the value of self-awareness. It's more rare than you realize. There's nothing wrong with lacking talent. Be bold. Figure out what you're good at, and pursue it. Aggressively. 6. Amateur Programmer An amateur programmer loves to code, and it shows: they might be a promising student or intern, or perhaps they're contributing to open source projects, or building interesting "just for fun" applications or websites in their spare time. Their code and ideas show promise and enthusiasm. Being an amateur is a good thing; from this level one can rapidly rise to become a working programmer. 7. Unknown Programmer The proverbial typical programmer. Joe Coder. Competent (usually) but unremarkable. Probably works for a large, anonymous MegaCorp. It's just a job, not their entire life. Nothing wrong with that, either. 8. Bad Programmer People who somehow fell into the programmer role without an iota of skill or ability. Everything they touch turns into pain and suffering for their fellow programmers – with the possible exception of other Bad Programmers, who lack even the rudimentary skill required to tell that they're working with another Bad Programmer. Which is, perhaps, the hallmark of all Bad Programmers. These people have no business writing code of any kind – but they do, anyway. These levels aren't entirely serious. Not every programmer aspires to the same things in their career. But it's illuminating to consider what a programmer could accomplish in ten years, twenty years, or thirty years – perhaps even a lifetime. Which notable programmers do you admire the most? What did they accomplish to earn your admiration? In short, what do you wanna do with your life? |
FincoApps:Wrong.... Frameworks are not only bootstarp, jquery, Anjular. Nodejs they are also software's we use as developers, are you saying you've or you are not using a framework ?, why dont you code your apps with machine language, dont use any software..... |
iamayodeji:Backend: python |
Nonsense.... |
Kodejuice:https://github.com/Whebcraft/Downloader |
