Our Best Practices consultation session is structured as a 2-day course.
 
Designed to ensure a smooth implementation, a knowledgeable consultant will guide your firm's implementation leaders through important decisions within the software.

Through the first day of this course, new customers gain a head start on using the software to its full potential while existing customers benefit from a detailed
review of their current use of ProSystem fx Practice Management.  Both new and existing customers learn how to implement CCH's recommended best practices.

Day two provides a more detailed look at the Implementation Checklist resulting in a customize Best Practices document that will suit your firm's workflow
and organizational structure. Additional time will also be available to discuss more complex technical, procedural and functional implementation issues.

Topics

    - Assess implementation goals
    - Discuss setup items you need to complete for a successful conversion
    - Use the implementation checklist to create a to-do list for conversion and implementation
    - Make assignments and set due dates in the implementation checklist
    - Begin updating the Best Practices guide to build best practices specific to your company
    - Ensuring an in-depth understanding of the implementation checklist and related best practices documents
    - Customizing a "Policies and Procedures Guide"
    - Working through complete multi-office or large-scale implementations

Attendees

Practice Management Champions Team, which should include representation from each department that will use the program.

Available Sessions for this Seminar:

ipwebinar.aspx?tab=1&smid=1334, December 16, 2014

Available Sessions for this Seminar:

ipwebinar.aspx?tab=1&smid=1635, December 15, 2014
ipwebinar.aspx?tab=1&smid=1635, December 15, 2014
ipwebinar.aspx?tab=1&smid=1635, January 05, 2015
ipwebinar.aspx?tab=1&smid=1635, January 05, 2015
ipwebinar.aspx?tab=1&smid=1635, January 06, 2015
ipwebinar.aspx?tab=1&smid=1635, January 07, 2015
ipwebinar.aspx?tab=1&smid=1635, January 07, 2015
ipwebinar.aspx?tab=1&smid=1635, January 20, 2015
ipwebinar.aspx?tab=1&smid=1635, January 27, 2015
ipwebinar.aspx?tab=1&smid=1635, January 27, 2015
ipwebinar.aspx?tab=1&smid=1635, January 29, 2015

What’s typically involved in an npm version release? How can you determine the release process for an existing project? Can project maintainers do anything to make it easier for new contributors?

The responsive images spec is fantastic and covers a lot of use cases, but most of the time you’ll only need one: resolution switching using the `srcset` and `sizes` attributes.

Problem-solving is an essential part of software development. Sometimes we get stuck on a particularly baffling problem, and this can feel frustrating and discouraging. The following are some strategies for getting yourself "unstuck."

If you’ve ever had to review a PR where the only code change is adding a wrapper element, you’ll be familiar with the pain of reviewing what appears to be a massive change but is actually trivial.

Goan diagnostic system manufacturer, Tulip Diagnostics (P) Ltd, has received the nod from the Central Drugs Standard Control Organisation (CDSCO) to manufacture ‘Coviscreen’, a rapid, double antigen test for total antibodies to Sars-Cov2 virus.

A few serious breaches to the bandh network of the khazan extending from Carambolim and Mandur to Neura and Agasaim pose grave danger to villages in the area due to possibility of massive flooding.

Faced with acute funds crunch and a 90% drop in tax mop up due to the lockdown in April, the state government has been left with no choice but to stagger payments. From maintenance grants for aided schools to payments to contractors, temporary workers and non-essential disbursements, have all been put on hold.

The Goan Seamen Association of India on Friday met governor Satya Pal Malik over their demand of repatriating seafarers back to India.

A senior resident attached to the radiology department of Goa Medical College (GMC) and hospital, Bambolim, was placed under suspension pending inquiry for alleged negligence. The doctor was allegedly absent from duty when former MLA Jitendra Deshprabhu was brought to GMC in a critical state on April 21.

I was on the podcast A Question Of Code recently. It was fun! The podcast is aimed at people who are making a career change into web development, so it’s right up my alley.

I sometimes get asked about what a new starter should learn. On the podcast, I mentioned a post I wrote a while back with links to some great resources and tutorials. As I said then:

For web development, start with HTML, then CSS, then JavaScript (and don’t move on to JavaScript too quickly—really get to grips with HTML and CSS first).

That’s assuming you want to be a good well-rounded web developer. But it might be that you need to get a job as quickly as possible. In that case, my advice would be very different. I would advise you to learn React.

Believe me, I take no pleasure in giving that advice. But given the reality of what recruiters are looking for, knowing React is going to increase your chances of getting a job (something that’s reflected in the curricula of coding schools). And it’s always possible to work backwards from React to the more fundamental web technologies of HTML, CSS, and JavaScript. I hope.

Regardless of your initial route, what’s the next step? How do you go from starting out in web development to being a top-notch web developer?

I don’t consider myself to be a top-notch web developer (far from it), but I am very fortunate in that I’ve had the opportunity to work alongside some tippety-top-notch developers at Clearleft—Trys, Cassie, Danielle, Mark, Graham, Charlotte, Andy, and Natalie.

They—and other top-notch developers I’m fortunate to know—have something in common. They prioritise users. Sure, they’ll all have their favourite technologies and specialised areas, but they don’t lose sight of who they’re building for.

When you think about it, there’s quite a power imbalance between users and developers on the web. Users can—ideally—choose which web browser to use, and maybe make some preference changes if they know where to look, but that’s about it. Developers dictate everything else—the technology that a website will use, the sheer amount of code shipped over the network to the user, whether the site will be built in a fragile or a resilient way. Users are dependent on developers, but developers don’t always act in the best interests of users. It’s a classic example of the principle-agent problem:

The principal–agent problem, in political science and economics (also known as agency dilemma or the agency problem) occurs when one person or entity (the “agent”), is able to make decisions and/or take actions on behalf of, or that impact, another person or entity: the “principal”. This dilemma exists in circumstances where agents are motivated to act in their own best interests, which are contrary to those of their principals, and is an example of moral hazard.

A top-notch developer never forgets that they are an agent, and that the user is the principal.

But is it realistic to expect web developers to be so focused on user needs? After all, there’s a whole separate field of user experience design that specialises in this focus. It hardly seems practical to suggest that a top-notch developer needs to first become a good UX designer. There’s already plenty to focus on when it comes to just the technology side of front-end development.

So maybe this is too simplistic a way of defining the principle-agent relationship between users and developers:

user :: developer

There’s something that sits in between, mediating that relationship. It’s a piece of software that in the world of web standards is even referred to as a “user agent”: the web browser.

user :: web browser :: developer

So if making the leap to understanding users seems too much of a stretch, there’s an intermediate step. Get to know how web browsers work. As a web developer, if you know what web browsers “like” and “dislike”, you’re well on the way to making great user experiences. If you understand the pain points for browser when they’re parsing and rendering your code, you’ve got a pretty good proxy for understanding the pain points that your users are experiencing.

Sætre, Glenn-Peter, author

Lenoir, Timothy, 1948- author

Roe, Shirley A., 1949- author

Wilson, Brenda A., author

Manz, A. (Andreas), author

McDonald, Roger B., author

Hill, Richard W., author