IF it is not a challenge to invent new glyphs and manufacture new keys, then perhaps we can rethink the markup as well. It is a rather open-ended question and I appreciate your asking. I have some thoughts, mainly inspired by the original inspiration to things like cascading styles, which was an inheritance of concepts and a jumble loosely associated with how magazines are structured and arranged / composed on a series of pages that flip together and have images and text. It seems that there are, by now, largely, conventions that are stuck to in the online realm, so maybe there is an amazing shorthand we could develop to get the same point across, now. What we are discussing is becoming closer and closer a reality because the amount of code pressing TAB will output (autocomplete) is increasing, and evening time and sunset time on actual "coding" might happen in our lifetimes. Perhaps not for microprocessors on solo devices requiring direct register access and pointer circuiting, but the trend is that less or fewer keystrokes can produce just as rich content. The markup language makes it "hypertext," right?
꜐expandꜘourꜛglyph꜅workꜝ Wikipedia has something closer to what I envision as what the dudes who done did CSS done thought. Someothing closer to arranging your magazine on the page for others to surf, and also link it with other pages. The soothing letters of English and their stradivarian font-signatures so carefully plucked and delicately labored on in the ethers of Apple headquarters, are bruised and battered by slashing and elbowing />
<!-- strong disagree -->
All I'm saying is that if you were to make a semantic markup of English today, would you really want to use keyboard-convenient glyphs just because it's hardware-convenient?
What would be the best way to add markup to English? It seems like an unexplored question. And if we were to explore it, we would find many alternatives, ranking much higher on the "for people" scale than HTML.
You think something that starts with "less than exclamation point" is made for people? "less than exclamation point minus minus" ah yes it just rolls off the tongue. HTML was clearly designed to add "semantic web" to the existing text data of the internet, no matter the cost to human readability. If it's "made for people" it's only in the roundabout fashion that eventually it gets hidden away by the interface to change the font color, etc.
You can write "down" with your left because immediately above your hand on the page there's no hand to "drag behind." I had to think about your sentence for a while. (It might just mean I'm not very bright.)
Scoping work is just as vital as work itself. If you are going apple picking you must go to the correct orchard. You cannot go to a forest bereft of apples and start picking what is not there. Nor can you pick all the apples in one day, or maybe if you do you will be so fatigued that you cannot work any more days that week. Scoping work is the ability to "bite off exactly as much as you can chew" and add "buffer time" so that you can successfully complete that delicious morsel. Indeed, the only way to success is to celebrate small victories, and you must now regulate what those are on your own. That means biting off not too much to chew, and overcelebrating what goes right. And finding the most essential meaningful path to your goal via junctures where you work on just enough of the project to accomplish either the: knowledge gain required, the app upgrade required, or the app creation required. Bit of a free-flow ramble for ya, but hope it helps.
Kanban is good once you have multiple brains looking for idle work. Until then, my recommendation as a driven, solo-starter who has created 3 ~huge projects more-or-less solo, is to rely on a `notes-todo` file where you religiously and often and frequently log the date and time and then write some notes. Append to the TOP of the file so you can see the latest words at the top, and then you scroll down and it's like a historical feed. You can put what you accomplished in the log to start. Eventually you will have design questions, debates, breakthroughs, and even just long treatise on what you want to accomplish. All this is amazing. You need a written record that helps you sort out where you are in the process. Remember, when working it's microscopic zoom mode surgeon style, and when reflecting it's telescope mode from the space station. You need to be kind to yourself moving between the two, and the answer is NOTES
I read the thread on metafilter, apparently its sponsored by the John Muir whatever and is for people who enjoy sketching nature and sharing their sketches, I think.
What do you mean "No" ? I am asking if it's traversing red lights while they are otherwise safe to traverse (no lateral traffic). What's with this amazing pessimism infecting this forum lately.
Get paid to answer important questions instead of getting paid to provide sought-after results. I think that's the end-point, the "how we get there" is now the question!
YouTube just "infers the context" meaning it uses some sort of tracking to realize you're at the gym versus "just chilling." But what's really chilling is that they don't mention location data or how they get it anywhere in this post.
This is a really cool ask, and I want to know more about what you want to know. Are you looking for a specific way to get caught up on solar and only solar?
It's so funny to me, this is normally read aloud as "security vulnerabilities disclosed after patching" but in reality this is a natural part of how software is made. You make compromises. Terrible ones. Security ones. In the beginning. Not always, but some places, some applications, some websites, some languages, sometimes you make some concessions for sake of simplicity or prototyping or proof-of-concept'ing that ends up making it all the way to prod. And then these "vulnerabilities" are really things that mean your company grew way faster than you anticipated, and lucky for you some ethical hackers "exploited" these concessions, first.