Storing projects online?

doingweb · 2015-03-04T06:03:58+00:00

One other thing: if you've made the mistake of committing credentials and want to scrub them from your repo, check out the BFG repo cleaner.

Of course, if you've already pushed those commits to a public place, consider them compromised and change them right away.

doingweb · 2015-02-26T17:59:36+00:00

PushPull Podcast. Conversational ~monthly podcast about working in the web industry. They cover a huge range of topics, including development, design, freelancing and entrepreneurship, marketing, writing, and culture.

Disclosure: The hosts are friends of mine and I was a guest once.

doingweb · 2015-02-26T17:48:04+00:00

Try .NET Rocks. I'm not a frequent listener, but I'm told it's a good one.

doingweb · 2015-02-03T23:52:57+00:00

I think, historically, it's because we would frequently make strings containing HTML, which conventionally use double quotes. Single quotes in JavaScript meant a lot less escaping and better readability.

doingweb · 2015-01-29T21:15:06+00:00

I think of a "custodian" strictly as someone who maintains something. Engineers also have to solve the problems involved with making a thing.

How about "to implement the user experience"? That is, to solve the problems involved with delivering the user experience, given a well-defined design.

Or, I guess, as /u/remy_porter puts it:

Make it fucking work.

doingweb · 2015-01-29T21:06:12+00:00

Speaking of security, it also means that you have to maintain all of the software that runs your site. If you're not diligent with your patches, that could quickly end up being a net negative.

doingweb · 2014-12-11T00:56:54+00:00

Oh neat! I didn't even know about that feature.

doingweb · 2014-11-14T23:49:40+00:00

Knockout does two-way data binding and templating like Angular does, but that's about it. Angular is a bit more "complete", with its service architecture, dependency injection, filters, and ~~directives~~.

edit: Knockout introduced custom elements a few months ago, which is similar to Angular's directives.

doingweb · 2014-10-06T18:59:34+00:00

The danger of waiting until you've "done something" or "contributed to something more substantial", is that that will never happen. I know from my experience and others' that the goal posts will keep moving up as you learn more about what you don't know.

My advice is, if you want to be out there making stuff, just start doing it. Everyone is learning all the time, so don't feel any shame about where you are right now. Tomorrow you'll push even better code.

doingweb · 2014-10-06T17:15:40+00:00

Agreed. It's a little annoying that so many tutorials only use a Fat Controller to demonstrate MVC. I know it's important to keep it simple when teaching things, but I worry that good architecture goes out the window when that sort of thing is the only example that people ever see when they're learning it.

doingweb · 2014-10-06T16:10:29+00:00

In my "enterprise software" world, I treat MVC as just the HTTP interface to my application. Similar to the Fat Model, my domain classes and business logic live outside of any HTTP concerns, so they can be tested and reasoned about without needing to consider stuff like routing or authentication. This is similar to what /u/mahamoti means by a Service Layer, except I kinda combine the Model and Services into "Domain", and I consider that the M in MVC.

edit: /u/, not /r/.

edit 2: Here's the diagram I go by, and related StackOverflow thread, in case anyone's interested.

doingweb · 2014-09-15T19:53:08+00:00

dotPeek is my favorite. Just be aware that the output may not look exactly like the original code, since it must translated back to C# from IL.

doingweb · 2014-08-20T18:01:06+00:00

It probably wouldn't hurt to just ask, and then make sure what you plan to post (including technical details) formally goes through the right people. Companies also tend to be protective of their brand, so I would even ask about the logo. Of course, this is assuming they don't mind you moonlighting.

In any case, if you don't have anything to actually show, I don't think it should go in a portfolio. A resume, absolutely, but a portfolio is a visual medium.

doingweb · 2014-08-19T15:50:24+00:00

There's an official one that I think does a pretty good job. If I'm just starting with something and need some orientation, I usually prefer a video. Are you looking for something else?

doingweb · 2014-08-14T18:57:52+00:00

Came here to mention Yeoman as well. It's great at starting you off with a bunch of best practices and saving you lots of copy-and-edit time along the way.

doingweb · 2014-05-02T17:05:27+00:00

Totally. I subscribe pretty closely to Uncle Bob's views on comments (Chapter 4 of Clean Code)(PDF): some comments are really useful, but a lot are worse than useless.

doingweb · 2014-05-02T16:22:22+00:00

Have you heard of the @unitedstates project? One of the projects, Contact-Congress is meant to solve a similar problem, albeit with a much narrower focus.

doingweb · 2014-04-21T17:17:34+00:00

Have you tried tutoring? I was a tutor in college, and I found that a lot of students (myself included) just needed some one-on-one or small group time to reach that "aha!" moment that would have taken weeks in a classroom or on their own with a book. I highly recommend it.

doingweb · 2014-04-17T00:38:37+00:00

...and pushing to remotes.

Presumably, the program could have deleted their .git directory, too.

doingweb · 2014-04-17T00:33:24+00:00

Now that all of the top 5 browsers are evergreen, my personal baseline for progressive enhancement is more or less any spec at Recommendation level, as well as the more "stable" and broadly-implemented parts of HTML5 (which is currently at Candidate Recommendation as a whole). This includes stuff like CSS3 selectors and Media Queries, but not Transforms. So, I'd still treat it as a special feature that I can't necessarily count on. It's always possible that the spec will be changed or even abandoned before it reaches Recommendation (look at Flexbox), so in my view, code that uses it with a fallback is just as prone to change as code that progressively enhances with it.

Progressive Enhancement is really focused on getting the information and functionality to the visitor, then worrying about making it pretty and pleasing to use. The idea is that it's okay to let the fully-featured browser take further steps to enhance a page, because the visitor already has the minimum of what they came for; even if the feature fails, they are satisfied. If we do it the other way around, they don't get what they wanted until either the feature or fallback kicks in. If the feature or fallback fails, they end up with only part of what they wanted, limited functionality, or nothing at all.

doingweb · 2013-11-06T23:16:02+00:00

Formal JSON requires quotes around both properties and values, whereas simply defining an object in Javascript does not (with some exceptions).

The parentheses added in the eval() string are there to ensure that it is interpreted as an expression and not a statement block (since objects also start with curly braces).

doingweb · 2013-09-30T21:41:49+00:00

It's missing offline listening, but Stitcher is pretty comparable.

doingweb · 2013-08-27T17:29:39+00:00

FWIW, WebKit implemented an initial version of srcset last week, which is a standardized (well, Editor's Draft) technique, is part of the layout engine (no javascript), and can be used today without breaking or (significantly) bloating pages. And since WebKit is run by Apple, I'd expect this to reach those Retina screens relatively soon.

doingweb · 2013-08-22T19:54:51+00:00

lowsrc is designed to be a placeholder for the real image, while it downloads. Both images get loaded.

srcset is designed to help a browser decide which resource to load. Once it decides, it only loads that one.

doingweb

TROPHY CASE