in my experience corporate appathy in large companies is a near infinite resource but im probably still to optimistic.
it reminds me of a mysterious building no one knew the origin or purpose of. someone filled a form for poor cleaning then the message bounced around between a dozen cleaning companies who didn't have a contact for it. after decades a cleaning company filled a form because it didn't have a number and wasn't on the drawings.
i had a hilarious argument with the significant other when my messages appeared a very lame response to messages i didn't receive.
i think the mental model should be what is most useful in court. if a netsplit occurs the state of the room doesn't exist anymore, conversation can continue but it should be a different room populated with working available clients. The main room can be restored and the missed convo can be a 3rd room
minimal effort can be fun. you cam always think of people as specialized tools with needs. if you get a good idea about both and refresh it periodically you are done. If you document enough you will be able to satisfy some needs, sometimes with very little effort. They will remember they owe you and love to elaborate about what else they need. Listen and move on. fill up the rolodex
The native slider is hideous as f and further offends me by being called a range. Why are stupid simple things missing like display the value? We could even have a same name number input that displays the set value or an <input for=""
html forms in general got very little love. They should be taken to the drawing board along with sql and get some relation therapist to blame the earlier for the endless fighting. over the years of growing up together json made an effort to make the marriage work but html forms are very stubborn and unreasonable.
Things actually got worse when pressing the back button erased the fields. What we wanted was a way to put the same form with the same values back on the page after failed validation. I have backends where that stuff takes up 60% of the code. imagine <form src="foobar.json"/> with a nice widget displaying the key value pairs, with outlines for nested fieldsets?
anyway, thanks for the nice dual slider. my own experiments didn't result in something nice enough that i would dare use.
I would like to see a contest with cash prizes for designing better html forms with backwards compatibility. Winning entries should be put in the spec. Im sure we would pay plenty if it would ease the suffering. :)
And then some wonder why people resort to js-controlled spas and tend to forget how they cursed after their “simple html form” deleted input due to navigation or accidental refresh. Input is the most valuable data in a program because it cannot he recalculated and usually reqiures work to produce. Anything that doesn’t get this principle sucks.
That said, I don’t think src=form.json would help. Some type of a local permanent storage is basically required for app-level interaction, because the page state is so transient and fragile. I’d say it should be <form storage="foo."> and all controls would be saved as foo.<name> into localStorage. With <form storage="foo." reset> received from backend to reset it explicitly if needed.
Most egregious thing is many times when people roll their own forms they end up actually removing things. The amount of forms I encounter where autofill and spellcheck are broken is crazy.
Maybe it’s some “best practice” library popular in the react ecosystem, I see it often enough to suspect that but autofill and spellcheck are my input and my business and a form shouldn’t decide if they’re enabled.
didn't give it much thought but couldn't you eventually run schools and universities on a percentage of student income tax (and remove all other sources) combined with a periodic questionnaire (for life) how [?????] one thinks their education was.
probably a bad idea but it gets me to ponder long term measurements
This assumes that schools are run purely for the future profitable careers of students. If you were a dean deciding what to invest in, would you ever give the teaching school more money? Would the medical school ever train another tropical disease specialist?
i wonder, is that specialist suppose to not make money their entire career? I think actually good education would allow them to do all kinds of things.
I do feel the raw idea is bad then added the survey to measure [????] say quality of life kind of things. If a school produces somewhat useful people who are really happy it seems to merit more funding. The economy may die if everyone has a good life
> i wonder, is that specialist suppose to not make money their entire career? I think actually good education would allow them to do all kinds of things.
School teachers and tropical disease specialists both make money, but they often make less money than others with similar educations. If a school is judged on future earnings it will optimize around that, and the predictable outcome to such an incentive is that programs that lead to lower paying careers will suffer.
wouldn't the scarcity increase the value? Why would we want people to study things we don't need and not study things in high demand? I wonder what the real cost is. My school does about 80:1 in diplomas:jobs every year. I got the job :) no one else did but they didn't do anything wrong. They just wasted years and money both their own and public funds.
our architects love building the house before making the drawings. i imagine we will probably figure it out eventually when the feature set can be strictly defined.
(maybe you eventually want a bath tub and a toilet in each room? maybe not?)
I've got architectural plans for my house. Parts of them are useful, but most of it isn't because the house doesn't match the plans. The details on the plans for the parts that match aren't trustworthy, because of all the parts that don't match. This is a relatively new construction, with minimal remodeling; it's just as they were building, they decided to do something else, and not update the drawings.
This is different than commercial work where in addition to the original plans, you also get as-builts, which can be expected to be accurate, and are expected to be updated.
If you only want to document once, it makes sense to do it once the thing is built, rather than before, because there's a good chance the actual thing will be different than the plan. If you will update it, it might make sense to start documentation before the thing is built.
Of course, if you never get around to writing documentation, it never needs to be updated.
It really depends on the nature of the project, but UI design often requires a lot of "Paving the Bare Spots"[0]. It's really just too damn complex and counter-intuitive (or too intuitive) to catch in Requirements.
Software allows us to iterate this incredibly quickly. Hardware design also does it, but at a much slower pace, and a much greater cost.
writing great documentation is extremely hard. sometimes it is so well done you only notice it in how fast and easy you progress. the funniest opposite was documentation i wrote myself but turned out to complicated for the future self. i kept thinking, what is this guy on about?? it assumed the reader knew all kinds of things i didn't and it made effort to explain the obvious.
it reminds me of a mysterious building no one knew the origin or purpose of. someone filled a form for poor cleaning then the message bounced around between a dozen cleaning companies who didn't have a contact for it. after decades a cleaning company filled a form because it didn't have a number and wasn't on the drawings.