All I Want Is You Zip Miguel
Christel Malden
I have told you all before that my glass is half empty and it is leaking. You can say that it is a negative attitude or what ever you want but this type of thinking has served me well during my life time and it helped me immensely in my 38 year career in IT.
I can live with Eddie Rosario and Byron Buxton covering left and center and Sano camping out in right field because I am not buying a ticket to watch Sano play in the outfield, I am there to watch Miguel Sano hit. Sano has more power that Harmon Killebrew and people will indeed stop whatever they are doing to watch Sano hit, just like they did for Hall of Famer Harmon Killebrew. Say what you want, but Miguel Sano is indeed too big to fail no matter how you slice and dice it.
QUESTION: That was very beautiful. I want to ask you just a couple more questions. In your book you talk about faith, and what you said about faith is really important. Can you talk about the difference between blind faith and real faith?
QUESTION: I know that The Voice Of Knowledge is destined to be the international bestseller that The Four Agreements has been because it is filled with so much wisdom. I want to let people know that they can visit your website to get more information about all of your books and any programs that you are offering. And I want to thank you for sharing all your wisdom and love through the books you have written.
Good hiring is one of the important things a marketing director does. There are things every HR tells you to do: how you should hire people with specific values and skills that fit well in the company. We need to hear our HR teams and follow their recommendation, because there is a reason why they made such recommendations, which is that they want to create a team of people who can work well together, so finding commonalities is crucial.
I'm going to start by admitting that even though I have received some support, there has been a lot of push back as well. I really have no problem with this, as I don't hide from criticism. In this follow up article I'm going to talk about the good and the bad takes that resulted from my blog post, but I especially want to dissect the opposing views.
Before I start to discuss a list of topics I collected from the feedback to my previous article, I want to mention something I have not said in that post, and I should have. In spite of this very specific disagreement I have with them, I highly appreciate the work that the Flask team does, and have a lot of respect for them. I understand that they are volunteers, that they often face difficult decisions that will always end up affecting someone one way or another, and that they always try to make the best judgements. Basically what I'm saying here with respect to their decision making process is that while I do not agree with some of their decisions, I know that they always have good intentions and come from a good place.
That's great! I don't claim I'm the only one with the answers. If you think this community has improvements to make with regards to these problems, it is important that you voice your opinions, even if they are not aligned with mine. You are welcome to reach out to me if you want to chat about them, or better yet, join the Flask team's Discord server and tell them directly.
I think this should have been a 2.4 myself, if they wanted to be consistent. It is especially strange to me that they decided to bump Werkzeug also to 3.0, given that this restructure affected only Flask. It appears their intention is to pair the version numbers of Flask and Werkzeug, but I don't recall anything being ever said about this.
I agree that a version numbering scheme is whatever the maintainers want it to be. If they want to follow the Python versioning style I have absolutely no problem with that, and in fact I use this style of versioning myself for some of my projects. So on this I'm with them.
Do you want to know the dates for the deprecation and removal of the FLASK_ENV environment variable in Flask? The deprecation announcement came with Flask 2.2.0, in October 2022. The variable was removed with 2.3.0, out in April 2023, just six months later and without any releases in between other than bug fixes.
I have a bit of a problem digesting this. It sounds good as a general statement, but Phil fails to address that every time a breaking change is introduced, someone has to pay the price for it. I can accept that renaming a variable or argument, or getting rid of some old function can make a Flask maintainer feel better or even save a bit of time, but the cost of these changes is far from free. I would allow this way of thinking for a project that is in its early days and growing, but I really do not want to see things renamed, deprecated or removed in every Flask release. Flask is not only a mature framework, but also the most used in the entire Python ecosystem. Breaking changes in a project of Flask's standing should be the exception, not the norm.
Even if we could agree that the Flask team owes nothing to anyone and can do whatever they want and break as many things as they want, I also don't owe anyone anything and am free to disagree with them and voice my disagreement with their policies and track record on this area. And I will continue to do so, in spite of people like you who think I'm overstepping.
It is still not clear what you want, if you don't want longer and more formal deprecation periods. Asking for no "trivial" changes is very silly, because what is "trivial" to you may be a valid reduction of maintenance burden for developers striving to put most of their effort into innovation. And it's not your call. And who cares if there are ten "trivial" changes when one breaking change is necessary even by your own standards?
Of course change requires effort. The payback is the benefit it brings. This is what we say when a community moves forward together. If people hadn't done this in the past, there would be no flask. Your attitude looks like "stop the world, I want to get off". And you can do this with version pinning.
I've read your past few articles and can really feel your frustration. In a world where us developers are valued by how well the things we make work, and how well they make OTHER things work, it's been a rough year. SQLAlchemy's update had me rewrite just over 200,000 lines of code, the new Flask doesn't work with the JUST right versions of of all the unix server related libraries, and if you change to old flask, you could be going down a 2 week long dependency nightmare. This Flask Login thing is rough. @Miguel I've been watching your stuff for years, and reading all that I can if you authored it. I don't really have a lot of valuable insight to add here, I just finished the second post I'd read of yours, and wanted to take a second to let you know that you are heard man. Sometimes the internet feels like screaming into a black hole. I feel for you dude. Keep fighting the good fight.
Illustration?
Illustration. I saw that the University of Idaho had a program for animation, 3D modeling, digital illustration as part of their art and architectural programs. It seemed like a good fit; I could get a job with a guaranteed paycheck and still draw and paint on the side. I did enjoy what I learned; I was fascinated by 3D modeling, but I got burned out and realized I just wanted to do more 2D work, more fine arts.
Interviews with visionaries and leaders around emerging ideas in innovation, leadership, culture. Interviews with luminaries from Cambridge, Harvard, and MIT. We want to inspire the conversation with inspiring interviews, portraits.
There is something invariably open about Miguel de Icaza when you meet him. When I arrived at the Microsoft offices in Kendall Square, de Icaza, dressed in casual jeans and a sweater, was talking to a colleague in his office while tapping away on his computer and called out to me in the hallway to set up wherever I wanted and to let him know whenever I was ready. I made myself at home. It should come to no surprise that interviewing the poster child for open source coding, likened to the Wikipedia for developers around the world, would be open and freely accessible.
I wouldn't feel badly about not coding. I think that anybody could pick it up if they wanted. Right now the whole world is obsessed with Deep Learning and I don't know much about it. I started reading up about it but it's a new thing and it turns out that I'm ill equipped to understand Deep Learning.
I think we were all operating in this modern world up until November. I think that we saw the world through a world of possibility and a lot of challenges. I think it was clear that we were not living in a perfect world and that there were a lot of progressive views that wanted to push the government. We wanted to get Obama doing certain things and Hillary doing certain things but we were on a path to get those things going and people were talking about issues that matter and now it just seems like we're regressed so much. It's very regressive. All these issues that mattered eight months ago, and they still matter, have now taken second place to the urgency that is the disaster that is happening across the board.
If I look back at October or even two years ago, I think that we've already known that we needed to do a lot for people in those positions in order to be retrained and help them and there's an opportunity for all these people to learn these skills and be repurposed but it requires government intervention. If we wanted to retrain these people, it requires a large effort in a large-scale government intervention.
582128177f