I need to be unique. Like a primary key.
We have started to name our releases at work with a name of our choosing.
And today it was my turn to issue the release, I came up with this invented marvelous creation:
It’s just a cool practice we adopted at work to motivate us to make releases because usually it is the task that nobody wants to do so much it takes you time and make you stress out.
Cool stuff !
* I know there’s a typo in MillenNium it is a feature not a bug =p
I just want to tag this day like you would
git tag your project. I liked my job today, I felt contributing actively and positively working with very different kind of people like journalists, designers and dba. It was fun.
The day started with a terribly blocking bug to solve and continued with campaigning to other developers to get them to review my 176 files pull request. It is hard duty because you need to chase them so much they flee from you at all cost, but once you capture one you need to be nice. As for the blocking bug, fortunately once you think hard enough anything can be solved. Solving it unblocked us for our big goal of the day.
Here are some updates, I am on a new contract since three months now. I changed my settings. This is the story of what happened to me after my last introspective dilemma. And my discovery of a new type of developers. Wanna read about that?
Religion is so far better than computing. If only we had some kind of prophet too, at least we would know what to do in advance. Seriously.
– Today at work. In the end, we decided to go for it and refactor later :-D
Job inquiry : software prophet.
Today’s story is about security. At work, one of our big construction site is to move old SOAP webservices into modern RESTful webservices. One of these webservices’ job is to generate a personalized pdf for a user based on the id of their banking operation. Doing this was not trivial considering our architecture, but it was rather fun, and it came with extra fun because developers are left alone with themselves to decide how to do things with no site manager to supervise how the building is going to be. No plan, just build it. Developers are expected to be their own architects. So developers are also expected to communicate with each other on how they’re going to do things. Sometimes it leads to funny situations.
So today I had an interesting conversation at work. They filled me in about a new position they want to open for a front engineer and they would like me to take the role. Obviously the job interests me, but it interests me only for its technical appeal because it’s an architect job – and this is what I want to do. They were pretty confident for the technical part of the job and didn’t even mention it which was reassuring. However, their biggest concern was if I would be motivated enough to learn more about the actual activity of the company in order to create interfaces with all the business logic in mind. In other words I would need to have a pretty sharp knowledge of the business logic to do the job, I would need to interact with non technical teams and such, they said “We want the closest person to the application to know our business the best” – wow. This is new.
Today I had the impression I was hostile with one of my non-tech co-worker. He asked me something, and instead of giving him a full well-formed answer I redirected him to reading his emails. It’s only later that I realized what I had done because he seemed a bit pissed about it.
Posted in Devsworld