As a product manager in this space, this stood out to me too. If I had to speculate:
- “Low code” is the current shiny thing
- These products are not sold to engineers, they’re sold to management types
- Management will only consider bringing in low code tools, because they believe this will save money on devs in the long run
- But that’s never how things play out, and engineers get involved anyway
So by making a “low code tool for engineers”, it seems they’re acknowledging the reality of the low code space and making sure the person who ultimately has to maintain this has the tools to make them successful while doing so…while also acknowledging the reality of selling integration/automation tools in 2022.
I could be way off here, but this is the only way that positioning makes much sense.
I guess it's meant to be low-code but as engineers they understand you can't low-code your way out of everything so escape hatches or advanced settings are provided for when "low code" isn't enough.
Google Maps has functionality for reporting problems. I've done the same when it suggested an unsafe bicycle street-crossing and they updated the routing.
“His problem was that the postcode for his east London flat was incorrect on Google Maps, so any driver using the service for navigation ended up not at his address, but in parkland at Three Mills Green, Bromley-by-Bow, half a mile away as the crow flies, but a mile and a half to drive.
What was an easily fixable error resulted in three years of frustration for Borghs, who first noticed the problem when an Uber driver took a wrong turn when taking him home.”
> Are you also of the opinion that you can't buy used phones?
Depends, if you want a throwaway phone for a call or two that are not important, go ahead.
But if you're looking for a phone you'll keep for multiple years and you want the least possible risk of being tracked by someone else than who made your phone, then I would absolutely not buy a used phone.
Small problem as OK phones can be bought for ~$100 or less in most parts of the world.
Do NOT accept it as admission of incorrectness. That will typically create an image that you're not a good worker, even when you're just trying to be polite to the person giving feedback.
Here's the pattern that I've found useful:
1/ Rephrase the feedback "What I heard you say...". This buys you a bit of time and putting feedback in your words takes the personal sting out
2/ Turn it into a non-hostile discovery discussion by saying something like "I'm interested in understanding why you think x, y, z...". Layer in any relevant context in your question phrasing... e.g. if the feedback is contradicting the project objectives then you may want to add that in your question
3/ Rephrase what you heard in your own words
4/ Repeat steps 2-3 until you have sufficient clarity
5/ Decide the appropriate next steps and articulate that. A feasible next step might be to take no action because you either resolved the issue through discussion or identified it's not a priority
100% Agree. My first startup job, I learned a ton but the second one was pointless. Target strartups with superstars - those who have a track record of winning. It makes a difference.
I've had similar issues. Tried delivery services for first time recently through Chipotle with ETA of 15-20min. Doordash was fulfilling the order, which showed up after 1 hr. By the way, the Chipotle was 3 min drive from my place. Since then I've been picking food myself.
There are no universal sources. Each source should be viewed with skepticism. That said, I have found small discords to be pretty good for PC hardware/tech related recommendation. Reddit on the other hand seemed a bit terrible at times with outdated or overly fishy marketing power speaking instead of the consumer.
Not sure I understand the product positioning