Live data from Hacker News

That Time I Made A Website

tiffany-young.com

101–110 of 124 posts

Re: That Time I Made A Website

#101

Earlier quoted context omitted.

I know hacker news is going to kill me for asking this, but what's wrong with center?

I'll bite. The idiomatic way to create webpages, in this day and age, is to try to separate content of a page from how the browser presents it. HTML is for the content and structure of a page. CSS is for controlling how it's displayed. The tag is an HTML tag that only exists to control how a page is displayed. In case you're wondering what to use instead, adding 'margin: auto;' as a css rule will do the trick.

The idiomatic way to create webpages, in this day and age, is to try to separate content of a page from how the browser presents it.

Which is why "modern" frameworks like bootstrap still encourage grid layouts using explicit width classes like span3?

Face it, we haven't gotten any better since Mosaic.

Re: That Time I Made A Website

#102
post #76

Earlier quoted context omitted.

>Well .... making a website != programming. Oh man, I remember when everyone looked down on web programmers and PHP monkeys. Hah. (I also did my much of my early programming on a trs-80, but mine was an obsolete tandy model 100 that I brought to school in the mid-90s, mostly to automate the 'guess and check' rote math homework.) It used to be that there was a strong hierarchy. I know in the '90s and the first half of…

> "Will we have 'visual FoxPro' for the web?" IMO we've already seen the automation of web-CRUD. It used to be a lot of work to set up even a simple CRUD app on the web, now a brain-dead simple CRUD app is 15 minutes in skilled hands. This differs from Visual FoxPro substantially. Our jobs are being automated, but instead of automating into the hands of an army of lay users, it's automating into the hands of a few sk…

>IMO we've already seen the automation of web-CRUD. It used to be a lot of work to set up even a simple CRUD app on the web, now a brain-dead simple CRUD app is 15 minutes in skilled hands.

hm. so what tools would a skilled developer use to, say, write a simple invoicing system in 15 minutes?

Re: That Time I Made A Website

#103

If I were an employer, I would be more impressed with the way the author responded to feedback/criticism and was able to improve her site on future iterations more so than I'd be impressed with the site itself (although it looks great).

I immediately thought that, too. I've worked with junior developers who, instead of learning from their mistakes, were defensive in code reviews and never took time to learn from their mistakes.

I'm 3ish months into my first post-graduation development job. It's really hard to go from school, where results counted, to an internship, where there was far more emphasis on getting shit done than how it was done (enterprise back office systems) to a professional software development job on a fully functional profitable web app.

It's not so much that the skillset that's required is different, though that's certainly part of it, it's that us junior devs are simply not used to having our code scrutinized very much. Sure, we've done some pair programming and group projects, but that was with other inexperienced undergrad/grad students, and it was difficult to just say "this code sucks, do it over" to an equal, just as much as it was difficult to hear that.

It's simply a mindset that is hard to break out of. A lot of us, myself included, were not ready for the reality that is a code review. I've gotten a lot more used to it, and I'm settling nicely into my role I think. Until now my mindset has been "make it work". I'm now transitioning to "make it work well. It's still hard to have to defend your code or methodology, or worse yet, during code review have the sudden realization that it is indefensible.

Re: That Time I Made A Website

#104

Earlier quoted context omitted.

Maybe a public forum wasn't the best place for a comment meant specifically for the author. I'm the person who criticized the .

I know hacker news is going to kill me for asking this, but what's wrong with center?

No, you'll live another day :-)

https://news.ycombinator.com/item?id=4370206

Re: That Time I Made A Website

#105
> For about 15 minutes, I thought about keeping it the way it was since it was practical and straightforward, but I couldn't. Every time I looked at it I felt the urge to throw my computer out the window cause it was so UGLY.

Sad to see another soul giving in to the temptation of "over-designing" things. For fuck's sake, what's wrong with light text on a white/gray backgrounds? She could've tweaked the fonts, spacing and colors a bit, but people no longer do that these days, instead she went full steam and overdesigned the shit out of it and it still looks bad.

...she could've learn a bit of Javascript and called herself a programmer instead of masturbating with CSS and posting about it on Facebook.

If you're not a designer, don't overdo design because you're not gonna do it well! If you are a designer, just stop when it looks "good enough" and start working on something more interesting than a bloody website design! We're wasting waaay too much of our lives "designing" stuff, whether it's our garden or a blog, instead of actually putting things and information in order (no, just "search" is no good enough though I guess some day I'll be able to google for my keys) or actually building cool new things!

Re: That Time I Made A Website

#106
post #43
post #25

This is why I love programming -- and the programming community, warts and all. Tiffany's an Environmental Science major who had a month of free time so she decided to learn how to make web pages. That's the same way I started (albeit as an English major), and the cocktail of instant feedback and ease of discovery kept me as a happy addict of the command line ever since. To me, accessibility and approachability are t…

Well .... making a website != programming. Maybe it's because I'm old (41, starting programming on a TRS-80 in the early 80s), but I'm astonished sometimes at how much fuss is made over such relatively minor achievements. This is lowering the bar on what stories are 'interesting', and - honestly - turns me off coming to HN because of the (for me) lower signal : noise ratio. And I disagree that accessibility is so imp…

Well .... making a website != programming.

A friend told a story about a recent job interview for a devops position. He'd already had phone interviews and a breakfast chat with some engineers from a company with offices in his city, and all that was left was meeting the bigwigs at their office.

As the interview started, one of the executives asked, "So what programming languages do you use most often?" My friend replied, "Well, it depends on the job. PHP, Perl, Python, shell, ..." "Oh," the executive interrupted, "so you're not a programmer, you're a scripter!"

I understand and appreciate the sentiment that marking up text isn't programming, but it reminds me of the sort of mindset that says you're not a real programmer unless you're banging machine code into memory using the front panel of a MITS Altair 8800.

Re: That Time I Made A Website

#107

Earlier quoted context omitted.

> If you only know HTML and CSS, you aren't a "programmer" because you don't have the tools and knowledge it takes to write programs that do any nontrivial computation. This is not a requirement for being a "programmer." It never has been. > If you only know Python, you don't have the tools and knowledge it takes to make an attractive static website. Nor, um, do you necessarily have the tools to do anything...

> This is not a requirement for being a "programmer." It never has been. Programmers program computers. We call them programmers because they program. If you can't write programs, you're not a programmer. What other definition of "programmer" could you possibly be using?

> Programmers program computers. We call them programmers because they program.

You've yet to give a definition of "program" I cannot satisfy with HTML, CSS and Javascript. The notion of "non-trivial" is not rigorous.

> What other definition of "programmer" could you possibly be using?

This is what I am wondering, because by any rational examination of what you've presented you've refuted your own claim. HTML+CSS is turing complete, which in practice means I can "program" arbitrary logic in it. It is a dialect of computer programming heavily focused on displaying content, but clearly it can do things.

Clearly explain to me: why is making a modern webpage any different from writing a simple modern Ruby script? Or a trivial iPhone app, for that matter? Open up a nib file and you'll see a serialized object graph, heavily biased towards the presentation and its structure. Callbacks are annotated into the system. But you could make a "dumb" iPhone app without ever writing a single line of code, using drag and drop components and GUI clicks. Oh my, that seems even less like programming, but in many cases it's indistinguishable from programming.

You really need to step back and ask yourself, "What is the actual difference here?" Your primary justification so far has been about people, but your original claim was about what "programming" is. If a "programmer" is someone who programs computers and we cannot cleanly and clearly explain why webdev is not programming, then what?

And to be honest, it's sort of patronizing and discouraging to new users. HTML+CSS+JS is the most widely deployed, used, programed, customized, and maintained programming environment in human history. Most people will find their way to the discipline via web browsers now, just as most kids in my childhood did via BASIC (also a victim of aspersions like what you cast).

Methods change and evolve. Environments change and evolve. Most of all, requirements change and evolve.

Re: That Time I Made A Website

#108
post #102

Earlier quoted context omitted.

> "Will we have 'visual FoxPro' for the web?" IMO we've already seen the automation of web-CRUD. It used to be a lot of work to set up even a simple CRUD app on the web, now a brain-dead simple CRUD app is 15 minutes in skilled hands. This differs from Visual FoxPro substantially. Our jobs are being automated, but instead of automating into the hands of an army of lay users, it's automating into the hands of a few sk…

>IMO we've already seen the automation of web-CRUD. It used to be a lot of work to set up even a simple CRUD app on the web, now a brain-dead simple CRUD app is 15 minutes in skilled hands. hm. so what tools would a skilled developer use to, say, write a simple invoicing system in 15 minutes?

Most would most likely use only one essential tool: google. Finding, for example, this: https://www.djangopackages.com/grids/g/ecommerce/

Re: That Time I Made A Website

#109
A lovely read, but I must say, that last line gave me a little adrenaline rush.

What seemed like a first timer progressing, giving you the ahh, how cute (like a cat video), all ended for me on the last line, where she addressed me with my first name.

I immediately assumed it was someone who had used a facebook/google 0-day to get profile information and show off at the end, hitting you while you were at ease, reading this lovely progression... until I continued to read and figured she just had a friend called Nick :P Guess I'm to paranoid for the internet :)

Re: That Time I Made A Website

#110

Earlier quoted context omitted.

> If you only know HTML and CSS, you aren't a "programmer" because you don't have the tools and knowledge it takes to write programs that do any nontrivial computation. This is not a requirement for being a "programmer." It never has been. > If you only know Python, you don't have the tools and knowledge it takes to make an attractive static website. Nor, um, do you necessarily have the tools to do anything...

> This is not a requirement for being a "programmer." It never has been. Programmers program computers. We call them programmers because they program. If you can't write programs, you're not a programmer. What other definition of "programmer" could you possibly be using?

Why won't you acknowledge that web development is not about HTML+CSS only? Why are you insisting that web developers know these technologies and not JavaScript, and in effect do not program?

You're obviously not very familiar with web development. The one who you have in mind is called designer. He's as you say, although it's still very hard and important job.

Web developers are programming all day long. They use JS almost exclusively with occasional excursions to HTML-land, without (in principle) ever touching CSS.

I'm a backend developer, so you will probably agree that I'm a programmer and I know what programming is. Just last week I had to fix/rewrite something on a frontend. It was a routine which retried an AJAX request until it either succeeded or failed a given amount of times, but with a twist - it cycled through a list of URLs while retrying. That's a very simple problem, I know, but I really felt as if I was programming while doing this - don't tell me I wasn't. And given JavaScript peculiarities it was full of surprises and overall a rather pleasant experience.

Now, design and programming are really two different skillsets. One is clearly programming, another is maybe-somewhat-with-HTML5-and-CSS3-almost-programming. You're confusing them both into one and so your conclusions are equally confused. To summarize: I know too little about design to really argue, but web development is, of course, programming.

Post reply on HN