Where’s the course on managing your reaction when the client starts moving the goal posts on a project that you didn’t specify well enough (or at all), because you’re a young eager developer without any scars yet?
This is interesting. I’m wondering how programmable this is. Would this project (or any similar ones) be able to POST a json payload with a field set to “now()”?
About the poor memory stuff, just get it in writing. “In writing“ could mean in an email, or a chat, or more likely in an issue tracker that has an audit log. When there’s a discrepancy, just link to where it was written down.
I was quoting from the article, which, admittedly, isn’t straight from the horses mouth. If there’s a discrepancy, one of them is wrong (I think I know which).
> While there’s no display, the illuminated ring behind the grip does provide a visual indicator of what the iron is doing: solid blue means it has power but the heating element is off, a pulsing blue indicates the iron is heating, and orange means it has reached the desired temperature. If you flick the heater switch off, the ring pulses purple until it cools back off and returns to blue.
I like this mentality, truly, makes perfect sense. Check in often to make sure you’re building the right thing. Keep going until it’s done.
However, the client is going to want to know (A) how much it’s going to cost, and (B) how long it’s going to take. These are extremely reasonable questions in most cases/industries. To answer these questions with a shrug is a nonstarter. The client is working with a time budget and a financial budget, and they need to have some sense of the numbers.
If the Waterfall and Agile methods are opposite ends of a spectrum, somewhere in between is where I’ve found an acceptable middle ground for both developers and clients.
Looks nice, both the site and the app! The first thought I had though was, here's a central place where potentially hundreds, thousands, perhaps tens of thousands (or more, depending on how successful you are) of database credentials are stored. Your https://visualdb.com/datasecurity/ page says "Database credentials are encrypted before being stored" but how do I know that? Encrypted how? This equates to "I pinky promise I won't get hacked, and even if I do, all your passwords would be impossible to crack anyways". Security-conscious users probably will need a bit more than that. Any thoughts on using other authentication methods?
Edit: as other commenters have mentioned, an on-prem version would certainly ease concerns a bit.
> getting people to use even the first layer of threads is very difficult, especially non-technical people
Indeed. We use Google Chat which is roughly a Slack clone in terms of structure. A discussion will start at the root level, and then branch into a thread after a few comments, but some users will miss this and continue to use the root level, which of course gets mixed into unrelated comments. It’s easy to create a mess, and it’s even worse when a discussion has multiple threads.
This “thread-based” style of space/channel was forced upon Google Chat users late last year. Prior to that, we had the option of “topic-based” channels, where every discussion had its own thread and there was no root level. Any reply to a topic would bump the topic into view. These were great for some use cases (one topic for each software issue, one topic for each support case, etc), and were easy to understand for non-technical people, because you could explain it like “each topic is like an email chain”. We got into the habit of summarizing the first comment of each topic, which always remained visible, so you could browse the list of discussions, again, much like email.
Anything that you can relate to email is great for the non-tech crowd.
> companies that offer a free service but start charging once they've locked in a client-base (I'm looking at you Heroku).
I don’t know much about Heroku, or if it’s been enshittified (yet?), but a company that offers a free product and somewhere down the line starts charging for it sounds fine to me.
And anyone who believed a product produced by real people working at a real company could be free forever was kidding themselves.
(In general though I agree with the sentiment of the article.)
I used Kali too, for Descent and other games. The chat rooms were true communities, probably one of the first times as a kid that I connected with other like-minded people (aka nerds).
This looks really nice! Something my staff would definitely appreciate, especially the ability to 'version' the text file (even if it's just different copies of yaml files in a directory). But the deployment aspect is a non-starter, I just can't tell my staff "install (the correct version of) graphviz (for your OS), then install (the correct version of) python, then run it from the commandline giving the yaml file as an argument". At minimum it'd have to be a standalone executable, and running it would need to be simplified, maybe not with a real GUI but perhaps "drop the yaml file on the executable" would suffice.
Perhaps I could rig up an internal webapp where a user could submit/post a file from an html form and it would download the resulting image, but that'd be a bit of a clunky process for the user.
Yes, this! In this day and age, if you’re applying for a remote position but you’re still fumbling around, unable to smoothly join a zoom meeting with a working microphone, it doesn’t bode well.
This reminds me of using xquery with MarkLogic circa 2010 to store the data, act as the middle tier, and generate the xhtml views, all in the same language. It had its quirks, but it was refreshing to do everything in one language.
I know exactly where the expectation comes from. The whole world has demanded absolute precision from computers for decades.
Of course, I agree that if we want computers to “think on their own“ or otherwise “be more human“ (whatever that means) we should expect a downgrade in correctness, because humans are wrong all the time.
