by bartq on 12/12/21, 9:48 AM with 92 comments
So I'm asking here: what would you like to read about, what are your current doubts about programming in general or related to dreaded by many subject of JavaScript and frontend frameworks. Is there any 'next level' you'd like to reach?
This question can help many other people in situation similar to mine. Thanks!
by ciarcode on 12/12/21, 11:18 AM
I mean, I'm not interested in a html/css/javascript tutorial, we have enough resources on that. What I found really missing on the internet (maybe I'm not that good at searching), is a step-by-step detailed guide on how to deploy/update/maintain a website. An unordered list of thing that came up to my mind:
- How to deploy the website on a server
- Which server should one use
- How to expose it on the internet (buy domain name)
- Version control and hosting the repository (GitHub vs gitlab vs ...)
- Updating your website (CI/CD like Jenkins?)
- Reproducible environments (Docker?)
- How to integrate analytics
- How to integrate ads respectfully (of your users)
- How to integrate paying contents
- How to address security
- Ho to address scalability
by onion2k on 12/12/21, 10:16 AM
This might be an answer you don't like very much, but seriously, all the best articles that I've read and shared in the past have been been things that the author would probably have felt compelled to write even if no one bothered read their work. I can't imagine that soliciting for ideas really works.
I think this is the main reason why I've always failed to be the blogger I aspire to be. There are few subjects that I care enough about to write consistently on. It's weird, because I post on the web a lot and I feel like I'm pretty passionate about web stuff. It just doesn't manifest in the form of blog posts though.
by mg on 12/12/21, 10:23 AM
Say we start with a fresh Debian install, the first line might be
apt update && apt upgrade
The second line might be apt install php
Or Python or Node. And then the commands to create the project directory, switching to it, installing a webserver etc would follow. At some point there would be a line echo "<h1>Hello World</h1>" > index.php
At this point, we accomplished serving a static page.And then line by line, a full web application is created, with routing, templating and user accounts. With no other tool than the command line. So the page would never say "Click on this then click on that..." or "Depending on your environment...". No, you could simply copy every line, paste it to your terminal and thereby create the exact same application.
Ideally the page would have one column of commands for every typical approach like Django, Flask, Laravel, Symfony, NextJS etc.
I would expect this page to start with just one approach - say Django. And then accept pull requests from experts for the other approaches.
So we would have side by side examples of what steps are needed in different environments to create a typical web app nowadays.
I had this idea for a while but so far did not get around doing it. If someone wants to collaborate on it, hit me up.
by ploika on 12/12/21, 10:57 AM
People who are fine with control flow, git, unit tests etc, but who would be lost if you start talking about things like state machines or depth-first search.
I'm largely talking about myself here, but I've worked with dozens of colleagues in several different jobs who would also match this description.
by kristopolous on 12/12/21, 10:58 AM
Create a
1. Mandelbrot
2. Julia set
3. Ray tracer with shading and shadows of a few simple spheres
4. A simple virtual machine
5. Rewrite the first three programs in the virtual machines assembler
6. A simple language such as Forth for the virtual machine
7. Rewrite the first three programs in your implemented language
All of these 7 tasks together will likely take under 2,000 lines of code, maybe even under 1,000.
If you know what you're doing, each one individually should take under an hour.
Doing a write-up about your experience with this would be great. Each one of these tasks has tradeoffs and can reflect personality and approach.
This is version 1.0 of this, and I just came up with it a few hours ago so I'm open to slight modifications (perhaps an extremely easy game instead of one of the fractals)
by OliverJones on 12/12/21, 10:46 AM
This would help countless people new to development. Lots of systems (I'm looking at you, Java) throw up vast splats of tracebacks. Others chunder out great chunks of poorly digested code. Sometimes daunting even for experienced people.
An article with basic advice about looking for the one or two useful lines in error messages would be great.
by kulikalov on 12/12/21, 10:27 AM
by xtiansimon on 12/19/21, 5:35 PM
Now I get the general idea of what I could do--clone the code, start editing it, setting breakpoints, walking the code execution, and essentially rewriting making their code my code. But it's a tangled web, no? Not easy. And then there must be (?) shortcuts? Plus, I'd like to read about the terminology and methods so I can search for other people's tutorials.
by dcminter on 12/12/21, 10:27 AM
Most things I found when my interest was piqued were from the perspective of building or running NixOS, which is (for now) much less interesting to me.
(Edit: If anyone feels like they have the technical knowledge but not the writing skills, I'd be happy to team up!)
by mastah88 on 12/12/21, 10:50 AM
by marttt on 12/13/21, 1:24 PM
Being a fan of minimal, clear languages, Lisps, Forths, Rebol etc, I've somewhat unexpectedly found myself immersed in the stuff by Perl community (perlmonks.org). I seem to like the free-form madness that surrounds this language (and the Monks), and Perl's linguistic roots and Larry Wall's thoughts on this are very interesting. Sigils and the verbosity strangely make sense to me, etc.
But, installed Perl is Big, at least compared to Picolisp, Rebol, or Lua.
I read about Microperl [1], but seems like it hasn't found (didn't find, in its day) wider usage. This philosophy -- deliberately writing Perl with a minimal amount of external dependencies -- doesn't seem very popular, aside of one-liners, which is a different thing imo. I wonder why. I've found a few contemplations [2, 3], but not much. Are people who have loved Perl first and foremost because of its syntax, semantics, TIMTOWDY etc, a tiny minority as compared to those who were dug in primarily because of CPAN?
And I wonder if Perl 6 (Raku) will be any different in this regard -- will its design encourage or favor minimal uses or systems a little more?
1: https://www.foo.be/docs/tpj/issues/vol5_3/tpj0503-0003.html
2: From 2018, "I want Circuit Perl now!": https://www.perlmonks.org/?node_id=1210076
3: From 2003, on Microperl: https://www.perlmonks.org/?node_id=228040
by karmakaze on 12/12/21, 9:20 PM
I'm continuously surprised by the ad-hoc manner in which devs use frameworks not understanding what the syntax they wrote means to the database. Many are confused by joins, or vs left-joins, and if a query runs slow have little idea how to index or change their schema to be more appropriate.
While we're here I'd also say data modelling. The DB is not meant to have a row-to-screen/page cardinality matching, unless you're a startup using MongoDB (or other document store).
The third one would be about API design. There are many blog posts that discuss one or two specific aspects of a particular API type (REST, gRPC, GraphQL) but it would be great to pick one of them and have it all lair out.
There may be print books that cover the above, but certain important topics always seem to fall in the gaps, like how exactly does one bound their microservice context? Most books gloss over this with a hand-waving trio of Order, Product/Widget, Customer.
by srvmshr on 12/12/21, 12:02 PM
For example, hundreds of papers talking about 'inductive bias' or 'SE(3) operators' and what not. There isn't even a general boundary between unsupervised and self supervised learning (Remember Yann Lecun stepping in one such debate but without a conclusively clear demarcation). Very few actually try to explain a view that general practitioner can connect (with some basic exposure). Google maintains a ML glossary but that sorely needs some updation beyond the very basic stuff.
by Adrig on 12/12/21, 12:28 PM
by csours on 12/12/21, 12:11 PM
The technology in IDEs, the things you Google, the bugs you get, stack trace messages, none of these things TELL YOU WHAT TO DO OR FIX. They are clues or evidence. You have to bring the understanding and intention.
I expect that some people disagree about this being a problem, but I've seen it enough times to recognize it. Senior developers need to remember that they were not always senior.
by jcun4128 on 12/12/21, 10:16 AM
by roydivision on 12/12/21, 12:07 PM
I’ve had an idea for a while that it would be interesting to document a computer language with a complete set of example code. This example code would exhibit all the language’s functionality. It would be written with best practices in mind.
The code wouldn’t necessarily need to do anything useful, The goal would be the code itself.
by rapnie on 12/12/21, 11:41 AM
So many projects list a gazillion features on their site, and then leave you with a "Good luck! The features are in the code base".
by pknerd on 12/12/21, 1:47 PM
I myself maintain a blog and run a Youtube channel in local Urdu language. When I started, I did not think what others want. I shared what I loved and could do on my own.
As long as you are original, authentic and honest, people would enjoy even a Hello World video by you.
by webmaven on 12/13/21, 5:43 AM
OpSec/Tradecraft for Developers
The metaphysics of CS/stats/DS/ML/etc. (I have a vague impression that the Bayesian vs. frequentist argument is just one tip of a multifaceted iceberg)
Protocol design and File format design
Game Theory as applied to de jure and de facto standards-making (incl. network effects, adversarial interoperability, etc.)
by chakkepolja on 12/12/21, 9:18 PM
* A in-depth, conceptual explaination of HTML/CSS layout and common UI idioms, so that I don't have to google something every now and then when making a website
* Back-end security related topics in one place. Various type of attacks and edge cases. (OWASP comes quite close I think.)
* Using Databases efficiently.
by jeffwiederkehr on 12/12/21, 10:37 AM
by hrnn on 12/12/21, 12:39 PM
I find the first hand story of how different architectural decisions turn out in real world scenarios are way more valuable than all the blogs out there writing about any new hot piece of tech. I'm curious what you found interesting and even check regularly.
by chespinoza on 12/12/21, 10:39 AM
-How to do modern frontend dev without installing almost a Gb of transient onliner JS deps.
-Modern Frontend development for Backend devs.
-Mobile apps development without installing huge frameworks and heavy tooling.
by gefhfff on 12/12/21, 10:02 AM
by zealsham on 12/12/21, 11:58 AM
by newusertoday on 12/12/21, 6:02 PM
by hazard on 12/12/21, 7:36 PM
by lsferreira42 on 12/13/21, 3:51 PM
by slmjkdbtl on 12/12/21, 3:01 PM
by micouay on 12/12/21, 10:35 AM
by hermann123 on 12/13/21, 6:53 PM
by neophyt3 on 12/12/21, 10:19 AM
by etiam on 12/12/21, 10:20 AM
by randomcarbloke on 12/12/21, 11:49 AM
It seems like it'd be a fun pet project.
by ssss11 on 12/12/21, 10:18 AM