From my experience, you build that non-fluff boundaries in the first one or two meetings with a senior leader.
I’d advise against going in the first one throwing punches.
Go with actionable feedback and be honest about what it is and what is not something you can solve. From there, if you genuinely care about whatever you’re complaning, you are more likely to be taken seriously.
> I’d advise against going in the first one throwing punches.
I’d advise against going in any one throwing punches. Instead, give actionable, honest, factual feedback with the intent to legitimately help the other person.
Fair enough, while I agree, in real project life, this calm, honest, factual feedback isn’t always enough for senior management to prioritise your issue.
Sometimes you need to a bit more assertive and blunt so that you become the top of the agenda, that’s what I meant by “throwing punches”.
Perhaps it means a much more over the top attitude in your view? (Happy to be corrected here)
If I need an issue prioritized, I'd have a discussion with senior leadership until one of us was convinced of the other's viewpoint, or we understood why we can't agree. For example, if my issue is clearly higher priority than anything else, I should easily be able to demonstrate that to senior leadership, and vice-versa. If we can't agree for a specific reason, we can say "the data is too fuzzy to know either way" and try to minimize risk.
Not all organizations will work like this, but that's a dysfunction that will need to be corrected. In that case, you should do what works (and that will be different for everyone), my particular situation won't apply to your particular situation.
Which drives me mad, given that Uranus should really be pronounced like the greek god Uranus (uran-os, with U pronounced like in Uzbekistan), not "ur anus".
Congratulations Francois! Thanks for maintaining Keras for such a long time and overcoming the corporate politics to get it where it is now.
I've been using it since early 2016 and it has been present all my career. It is something I use as the definitive example of how to do things right in the Python ecosystem.
Obviously, all the best wishes for you and your friend in the new venture!!
Notes is a very different app to Notepad though. Nobody uses the Notes app to edit plain text files, which is the sole use case of Notepad. Notes is for writing, well, notes. Notes also has a lot of other editing modes and features like drawing with the apple pencil, scanning documents, cross device syncing, etc. As far as I’m aware Notepad can only edit plain text files.
It's unfortunate that Apple Notes doesn't handle plain text. I'd use it like this if possible.
Anyway, I use TextEdit in plain text and autocomplete, autocorrect and spellcheck all work just fine, as they work in every text box in macOS. That Windows' Notepad got some of that just in 2024[1] is bonkers…
I used Notes to edit a text file once and learned a very important lesson; It changes all your double-quotes to fancy Unicode double-quotes. They may look prettier, but they completely break the code you are working on.
Right. What am I looking at? It seems clearly a case that it started with the final logo they wanted and finished with 27 pages of pure justification BS.
Yes, but that's just how it works. A respected designer brings talent and years of experience, expertise, theoretical knowledge, and intuition to their task. But like most of us, they aren't very good at introspecting to explain the real reason they arrived at a particular design.
They are, nevertheless, required by business types to come up with some sort of justification, and that's what you just read. It doesn't matter whether it's truthful or accurate, so long as it's plausible from a business perspective.
I’d advise against going in the first one throwing punches.
Go with actionable feedback and be honest about what it is and what is not something you can solve. From there, if you genuinely care about whatever you’re complaning, you are more likely to be taken seriously.
reply