Opperman, Jeffrey J., 1971- author

Messer, Kent D., author

Alegre, Helena, author

Earll, Robert, author

Clavijo, Katherine, author

Sergeev, G. B. (Gleb Borisovich)

Online Resource

Online Resource

Online Resource

Barker Library - TP1151.L37 S3613 2018

Online Resource

Montero, Roman A., author, translator

Drake, Matthew, author

Lewis, Bob, author

Egerton, Peter, author

Stull, Edward. author

Heskett, James L

Davies, Joseph, 1962-

Stanek, William R., author

Zacker, Craig

Ellis, Charles D

Ellis, Charles D., author

Zhu, Wei-Dong, author

Bush, Mirabai, 1939- author

Bush, Mirabai, 1939- author

Grinberg, Alex. author

Interview with Raghav Tripathi, MPH, and Jeremy Scott Bordeaux, MD, MPH, authors of Association of Demographic and Socioeconomic Characteristics With Differences in Use of Outpatient Dermatology Services in the United States

Interview with Ian Leslie. Mcallister, FRANZCO, author of Two-Year Efficacy of Ranibizumab Plus Laser-Induced Chorioretinal Anastomosis vs Ranibizumab Monotherapy for Central Retinal Vein Occlusion: A Randomized Clinical Trial

Interview with Jonathan H. Lass, MD, author of Donor, Recipient, and Operative Factors Associated With Increased Endothelial Cell Loss in the Cornea Preservation Time Study

Interview with Laura Hawks, MD, author of Trends in Unmet Need for Physician and Preventive Services in the United States, 1998-2017, and John Z. Ayanian, MD, MPP, author of Looking Back to Improve Access to Health Care Moving Forward

Interview with Jason Ying Kuen Chan, MBBS, author of Practical Aspects of Otolaryngologic Clinical Services During the 2019 Novel Coronavirus Epidemic: An Experience in Hong Kong

In this 90-minute webinar, we will show you how to get around in the software and what functions are available to make you more productive. Includes an in depth look at Family Coupling, File attachments and the Pathfinder, what they are and how to use them to improve your productivity. This session is intended for those who are new to the Cantax software and those who would like a refresher of all the menu items and their function.

Available Sessions for this Seminar:

ipwebinar.aspx?tab=1&smid=1698, December 17, 2014
ipwebinar.aspx?tab=1&smid=1698, January 16, 2015
ipwebinar.aspx?tab=1&smid=1698, January 23, 2015
ipwebinar.aspx?tab=1&smid=1698, January 28, 2015

For over five hours, as migrant workers and stranded tourists boarded the Shramik special train, the two loco pilots ran over checklists and discussed their route in the engine of train number 01602.

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.

Haslam, Stephanie

Slonczewski, Joan, author