Just a bit jealous. We didn't have compos back when people mistakenly double clicked web site links. Was almost forced into using a barely templatable database engine.
Disqualified from a National Web Design Competition for Using GitHub
291–300 of 329 posts
Re: Disqualified from a National Web Design Competition for Using GitHub
#292Earlier quoted context omitted.
my understanding was that they were DQed for using github, not hosting there. Which is just bananas. I can't think of a single decent piece of software that doesn't use Version Control, and 99.9999% of the software I know uses git for VC. We need a new format. This institutional nonsense is for the birds.
How about reading and adhering to client project specs? That is a legitimate and important aspect of engineering. The spec said no github. Jekyll is also a legitimate tool for "decent software". In the professional realm, you will be using code generating tools, so the argument that 'X is commonly used for software development and thus the requirements are boneheaded' does not hold up,
Sure, if the spec uses it's terminology accurately and is unambiguous, but...
> Template engine websites, tools, and sites that
> generate HTML from text, markdown, or script files,
> such as Webs, Wix, Weebly, GitHub, Jekyll, and Replit,
> are NOT permitted.
Github is certainly not a template engine website.
One could make the argument that it falls on the engineer to discuss the spec with the client - but these are high school students, and when they did attempt to discuss the spec with someone they were given the bureaucratic runaround.
edit: formatting
Re: Disqualified from a National Web Design Competition for Using GitHub
#293Thats okay, these are always run by idiots. I graduated in 2001 and we worked really hard on our site to profesionally design a site for a real company and we lost to a crappy site with a marquee and blink tag because it was more "dynamic".
Re: Disqualified from a National Web Design Competition for Using GitHub
#294Earlier quoted context omitted.
That is a super good idea, some of our posts have taken off and we have even been contacted by the vp of developer relations for github. I'll contact the rest of the group and see what they think. Although, I do happen to know that fbla has a similar type contest to TSA so we might just move to that next year.
If you do go ahead with this, I'd be willing to act as a judge and help out generally with advice. My contact details are in my profile.
+1
yourusername at myusername dot se
Re: Disqualified from a National Web Design Competition for Using GitHub
#295Earlier quoted context omitted.
How about reading and adhering to client project specs? That is a legitimate and important aspect of engineering. The spec said no github. Jekyll is also a legitimate tool for "decent software". In the professional realm, you will be using code generating tools, so the argument that 'X is commonly used for software development and thus the requirements are boneheaded' does not hold up,
Sure, if the spec uses it's terminology accurately and is unambiguous, but... > Template engine websites, tools, and sites that > generate HTML from text, markdown, or script files, > such as Webs, Wix, Weebly, GitHub, Jekyll, and Replit, > are NOT permitted. Github is certainly not a template engine website. One could make the argument that it falls on the engineer to discuss the spec with the client - but these are…
Exactly. Lesson here (and I hope OP and teammates read this) in my opinion is precisely this:
1 Spec conflates "github" and "templates".
2 Students take spec to teacher (who ended up being the judge!) and inform them of the error.
3 Spec is changed OR restriction (however boneheaded -- remember, clients) remains in place.
4 Team knows exactly what is what.
5 No article on HN. The end.
Re: Disqualified from a National Web Design Competition for Using GitHub
#296Re: Disqualified from a National Web Design Competition for Using GitHub
#297Earlier quoted context omitted.
Sure, if the spec uses it's terminology accurately and is unambiguous, but... > Template engine websites, tools, and sites that > generate HTML from text, markdown, or script files, > such as Webs, Wix, Weebly, GitHub, Jekyll, and Replit, > are NOT permitted. Github is certainly not a template engine website. One could make the argument that it falls on the engineer to discuss the spec with the client - but these are…
Exactly. Lesson here (and I hope OP and teammates read this) in my opinion is precisely this: 1 Spec conflates "github" and "templates". 2 Students take spec to teacher (who ended up being the judge!) and inform them of the error. 3 Spec is changed OR restriction (however boneheaded -- remember, clients) remains in place. 4 Team knows exactly what is what. 5 No article on HN. The end.
Yeah, this is indeed one of those life lessons that is inevitable. I just feel like this is the kind of thing you should learn after you've had a chance to pursue your interests enough to turn them into skills.
Programming is a joy. Engineering is a discipline. Customer relations is an unfortunately necessary workaround to a set of dumb problems.
Re: Disqualified from a National Web Design Competition for Using GitHub
#298This would be a facepalm moment for me if I were these guys. Because while they used GitHub in the most common manner, to host a code repository. Not only did they violate the rules technically, they also inadvertently violated them practically. README.md is a markdown file. GitHub parses this into that little blurb you see below the repo. This is technically a violation of the rules. Part of your project is technica…
> GitHub parses this into that little blurb you see below the repo. This is technically a violation of the rules. Part of your project is technically generated by GitHub. No, that's Github interpreting markdown for display on Github.com. That's not generating any part of the project that they submitted.
You can't use a site that takes markdown and generates HTML. It is a file in the project. By the letter, it counts.
And the reason stuff like this happens is because of people who like to bend the rules on technicalities. Where they hold to the letter but violate the spirit.
You have to draw lines somewhere in a competition.
Re: Disqualified from a National Web Design Competition for Using GitHub
#299In the rules for the competition, there's this: I. Template engine websites, tools, and sites that generate HTML from text, markdown, or script files, such as Webs, Wix, Weebly, GitHub, Jekyll, and Replit, are NOT permitted. [1] So the fact that you hosted it on Github disqualifies you. Regardless of whether you used their jekyll engine. I would immediately resubmit it from a shared hosting provider or by setting up…
kids don't have credit cards; the organization should have been providing free paid hosting with git support and ability to deploy through github actions...it should have been: git and github is a requirement for hosting your code. imho
You're absolutely right. They should have provided VM's for each team using a secure linux os and instructions on how to connect and what their url is/would be along with a git repo to pull those instructions using the students ssh keys. If the students want to use actions to auto-deploy, that's fine, just make sure the key isn't in the repo and is supplied via params. This would have made any restrictions about "template engine" irrelevant and simplified the contest as well as provide a safe haven for the kids to "compute" in.
Re: Disqualified from a National Web Design Competition for Using GitHub
#300That's not even a tough break. It is the product of administrators who are not qualified to run the competition. I wonder if the same thing would have occurred if they used Plastic SCM.