Search Results

Search found 87926 results on 3518 pages for 'deft code'.

Page 542/3518 | < Previous Page | 538 539 540 541 542 543 544 545 546 547 548 549  | Next Page >

  • SPS 2010 Tips

    - by Gino Abraham
    1. Error occurred in deployment step 'Retract Solution': Cannot start service SPUserCodeV4 on computer      When i got this error i searched in net and found a solution to enable Microsoft Sharepoint foundation User Code Service in services section of Central Administration. Unfortunately i couldnt find a service with that name. While searching in services.msc i found that SharePoint 2010 User Code Host was not started. Once the Service was started  the issue was resolved.   Will be updated...

    Read the article

  • Google I/O 2012 - Go in Production

    Google I/O 2012 - Go in Production Andrew Gerrand Since Go's release in 2009 many companies (besides Google, of course) have used the language to build cool stuff. In this session programmers from several companies will share their first-hand experience using Go in production environments. For all I/O 2012 sessions, go to developers.google.com From: GoogleDevelopers Views: 182 4 ratings Time: 49:45 More in Science & Technology

    Read the article

  • App Scripts Office Hours - August 30, 2012

    App Scripts Office Hours - August 30, 2012 In this week's episode of Google Apps Script office hours, Eric and Ikai: - Highlight a blog post on Google Analytics in Apps Script (goo.gl - Answer questions about Charts Dashboards and other topics. - Discuss the upcoming Apps Script hackathon in Austin, Texas (goo.gl To find out when the next office hours will be held visit: developers.google.com From: GoogleDevelopers Views: 135 16 ratings Time: 33:51 More in Science & Technology

    Read the article

  • Google I/O 2012 - So You've Read the Design Guide; Now What?

    Google I/O 2012 - So You've Read the Design Guide; Now What? Daniel Lehmann, Tor Norbye, Richard Ngo The Android Design Guide describes how to design beautiful Android apps, but not how to build them. In this talk we'll give practical tips for how to apply fit & finish as you are implementing your design, we'll show you how to avoid some common pitfalls, we'll describe some useful patterns, and show you how tools can help. For all I/O 2012 sessions, go to developers.google.com From: GoogleDevelopers Views: 38 1 ratings Time: 56:31 More in Science & Technology

    Read the article

  • GDD-BR 2010 [1G] Android: Building High-Performance Applications

    GDD-BR 2010 [1G] Android: Building High-Performance Applications Speaker: Tim Bray Track: Android Time: G [16:30 - 17:15] Room: 1 Level: 151 Build Android applications that are smooth, fast, responsive, and a pleasure to use. Also, learn about the tools and techniques we use to track down and fix performance problems. From: GoogleDevelopers Views: 20 0 ratings Time: 33:34 More in Science & Technology

    Read the article

  • GDL Presents: Creative Sandbox | Google+ API

    GDL Presents: Creative Sandbox | Google+ API Tune in to hear about two cool, new campaigns that use the Google+ API from the core creative teams at Goodby Silverstein & Partners, Hook and RESN in conversation with a Google+ Developer Relations expert. They'll talk about how they pushed the possibilities of the Google+ API - and will inspire you to do the same. From: GoogleDevelopers Views: 0 0 ratings Time: 01:00:00 More in Science & Technology

    Read the article

  • Google+ Platform Office Hours: A Movember of Metro-style Apps!

    Google+ Platform Office Hours: A Movember of Metro-style Apps! This week join Google+ Developer Relations team members Joanna Smith, Jonathan Beri, Silvano Luciani, and Gus Class for a special Movember GDL. We'll share updates for Google+, demonstrate Google+ Metro style apps integration in C#, and answer any questions you ask in the event and live YouTube comments. From: GoogleDevelopers Views: 0 0 ratings Time: 30:00 More in Science & Technology

    Read the article

  • Maps We Like, and Why We Like Them

    Maps We Like, and Why We Like Them Live from Sydney (now in HD!) Paul and Chris talk about their favorite maps, why we like them, and how we find cool maps. 1:40 Showcase | 5:45 Geo Developer Blog | 8:25 GTA4 Street View map | 11:00 Internet Map | 14:40 How we find cool maps | 20:30 Map of the Dead | 24:50 Old Maps Online | 27:10 Wind Map From: GoogleDevelopers Views: 3 0 ratings Time: 29:18 More in Science & Technology

    Read the article

  • So, I though I wanted to learn frontend/web development and break out of my comfort zone...

    - by ripper234
    I've been a backend developer for a long time, and I really swim in that field. C++/C#/Java, databases, NoSql, caching - I feel very much at ease around these platforms/concepts. In the past few years, I started to taste end-to-end web programming, and recently I decided to take a job offer in a front end team developing a large, complex product. I wanted to break out of my comfort zone and become more of an "all around developer". Problem is, I'm getting more and more convinced I don't like it. Things I like about backend programming, and missing in frontend stuff: More interesting problems - When I compare designing a server that handle massive data, to adding another form to a page or changing the validation logic, I find the former a lot more interesting. Refactoring refactoring refactoring - I am addicted to Visual Studio with Resharper, or IntelliJ. I feel very comfortable writing code as it goes without investing too much thought, because I know that with a few clicks I can refactor it into beautiful code. To my knowledge, this doesn't exist at all in javascript. Intellisense and navigation - I hate looking at a bunch of JS code without instantly being able to know what it does. In VS/IntelliJ I can summon the documentation, navigate to the code, climb up inheritance hiererchies ... life is sweet. Auto-completion - Just hit Ctrl-Space on an object to see what you can do with it. Easier to test - With almost any backend feature, I can use TDD to capture the requirements, see a bunch of failing tests, then implement, knowing that if the tests pass I did my job well. With frontend, while tests can help a bit, I find that most of the testing is still manual - fire up that browser and verify the site didn't break. I miss that feeling of "A green CI means everything is well with the world." Now, I've only seriously practiced frontend development for about two months now, so this might seem premature ... but I'm getting a nagging feeling that I should abandon this quest and return to my comfort zone, because, well, it's so comfy and fun. Another point worth mentioning in this context is that while I am learning some frontend tools, a lot of what I'm learning is our company's specific infrastructure, which I'm not sure will be very useful later on in my career. Any suggestions or tips? Do you think I should give frontend programming "a proper chance" of at least six to twelve months before calling it quits? Could all my pains be growing pains, and will they magically disappear as I get more experienced? Or is gaining this perspective is valuable enough, even if plan to do more "backend stuff" later on, that it's worth grinding my teeth and continuing with my learning?

    Read the article

  • Switch from back-end to front-end programming: I'm out of my comfort zone, should I switch back?

    - by ripper234
    I've been a backend developer for a long time, and I really swim in that field. C++/C#/Java, databases, NoSql, caching - I feel very much at ease around these platforms/concepts. In the past few years, I started to taste end-to-end web programming, and recently I decided to take a job offer in a front end team developing a large, complex product. I wanted to break out of my comfort zone and become more of an "all around developer". Problem is, I'm getting more and more convinced I don't like it. Things I like about backend programming, and missing in frontend stuff: More interesting problems - When I compare designing a server that handle massive data, to adding another form to a page or changing the validation logic, I find the former a lot more interesting. Refactoring refactoring refactoring - I am addicted to Visual Studio with Resharper, or IntelliJ. I feel very comfortable writing code as it goes without investing too much thought, because I know that with a few clicks I can refactor it into beautiful code. To my knowledge, this doesn't exist at all in javascript. Intellisense and navigation - I hate looking at a bunch of JS code without instantly being able to know what it does. In VS/IntelliJ I can summon the documentation, navigate to the code, climb up inheritance hiererchies ... life is sweet. Auto-completion - Just hit Ctrl-Space on an object to see what you can do with it. Easier to test - With almost any backend feature, I can use TDD to capture the requirements, see a bunch of failing tests, then implement, knowing that if the tests pass I did my job well. With frontend, while tests can help a bit, I find that most of the testing is still manual - fire up that browser and verify the site didn't break. I miss that feeling of "A green CI means everything is well with the world." Now, I've only seriously practiced frontend development for about two months now, so this might seem premature ... but I'm getting a nagging feeling that I should abandon this quest and return to my comfort zone, because, well, it's so comfy and fun. Another point worth mentioning in this context is that while I am learning some frontend tools, a lot of what I'm learning is our company's specific infrastructure, which I'm not sure will be very useful later on in my career. Any suggestions or tips? Do you think I should give frontend programming "a proper chance" of at least six to twelve months before calling it quits? Could all my pains be growing pains, and will they magically disappear as I get more experienced? Or is gaining this perspective is valuable enough, even if plan to do more "backend stuff" later on, that it's worth grinding my teeth and continuing with my learning?

    Read the article

  • A TDD Journey: 2- Naming Tests; Mocking Frameworks; Dependency Injection

    Test-Driven Development (TDD) relies on the repetition of a very short development cycle Starting from an initially failing automated test that defines the functionality that is required, and then producing the minimum amount of code to pass that test, and finally refactoring the new code. Michael Sorens continues his introduction to TDD that is more of a journey in six parts, by implementing the first tests and introducing the topics of Test Naming, Mocking Frameworks and Dependency Injection

    Read the article

  • Google I/O 2012 - Monetizing Android Apps

    Google I/O 2012 - Monetizing Android Apps Chrix Finne, Kenneth Lui There's more than one way to make money with your Android app: Paid apps, in-app billing, advertising, and so on. This session covers the subject comprehensively, with details on the monetization tools in Google Play and a close look at the AdMob SDK, ad network mediation and Google Analytics. Walk away armed with knowledge on how you can make more money, get more users and gain more insights. For all I/O 2012 sessions, go to developers.google.com From: GoogleDevelopers Views: 198 7 ratings Time: 52:49 More in Science & Technology

    Read the article

  • Google I/O 2012 - Gaming in the Cloud

    Google I/O 2012 - Gaming in the Cloud "Fred Sauer Many games developers are finding the easy development and deployment experience of Google App Engine ideal for building cloud based state-storage, matching making services and collaborations services. When you have a hit game, the last thing you want to do is worry about your server provisioning. App Engine has an always-free tier to get you started and then scales seamlessly to any size of usage. Game developers also use Google Cloud Storage to easily store and quickly deliver media files to clients around the world. For all I/O 2012 sessions, go to developers.google.com From: GoogleDevelopers Views: 1 0 ratings Time: 01:02:17 More in Science & Technology

    Read the article

< Previous Page | 538 539 540 541 542 543 544 545 546 547 548 549  | Next Page >