$650 is a lot of money. Yes, definitely have those checks. I'd rather they call and check and everything is fine, than they not call, and things not be fine.
650 dollar bills is a lot of singles, it could feed a man for a month or more, or provide enough gas to drive across the US, it must be a lot of money, but it's quickly lost when it comes to basic needs like housing, healthcare and education.
For those saying it's not a lot of money, I shall gladly accept your donations.
$650 would allow me to buy myself a new office chair, or sort out a DIY project. Sure, I can save for these things, but if it's an inconsequential amount for you - it's an amount of consequence for me.
I think having very infrequent large long outages is the norm here actually.
I can't think of any company this size that didn't have some outage of this magnitude at least once.
Facebook BGP for instance, Slack in Feb of '22, Cloudflare in June, YouTube, Twitch, Sony PlayStation etc etc have all had incidents this wide and long.
If your experience has been entirely Python then a compiled language is the way to go.
SOLID principles still apply, but I've found multi-threaded applications to be more sensible in compiled languages.
More SQL is valid, up to a point. Make sure you're familiar with the basic syntax for SELECT, UPDATE, DELETE.
After a compiled language, try a different scripting language: JS, Ruby, PHP. JS is interesting because it's browser based. Ruby is interesting because of its ActiveRecord layer. PHP is interesting because of its legacy, and where it's going syntactically.
I wouldn't stop there either. Once you've done the above, write a Domain Specific Language on top of one you're familiar with. I wrote my first one on top of C#.
Write a terminal only application, and then extend it to be visual. Does it have to be HTML? Write a flashcard program, there are so few about.
In my experience, Ruby was good for prototyping, and then JRuby for performance.
Python was good for quick science and then R, C or C++ for performance.
PHP was good for prototyping websites, and then you switch it to become the view layer with API support for scaling.
Once you've done the above, try an esoteric language such as Piet.
I'd add putting in a static code analysis tool in there because that will give you a number for how bad it is (total number of issues at level 1 will do), and that number can be given to upper management, and then whilst doing all the above you can show that the number is going down.
There is significant danger that management will use these metrics to micromanage your efforts. They will refuse changes that temporarily drive that number up, and force you to drive it down just to satisfy the tool.
For example, it is easy to see that low code coverage is a problem. The correct takeaway from that is to identify spots where coverage is weakest, rank them by business impact and actual risk (judged by code quality and expected or past changes) and add tests there. Iterate until satisfied.
The wrong approach would be to set something above 80% coverage as a strict goal, and force inconsequential and laborious test suites on to old code.
Many tools allow you to set the existing output as a baseline. That's your 0 or 100 or whatever. You can track new changes from that, and only look for changes that bring your number over some threshold. You can't necessarily fix all the existing issues, but you can track whether you introduce new ones.
BuilderStorm is an established software engineering company that provides a SaaS solution to the construction industry. We're a full plot-of-land to finished-building solution focusing specifically on document control.
We're looking for a mid level full stack engineer to help with day to day maintenance of our server, but ultimately helping to reduce our backlog of issues.
PHP 7.4/jQuery/MySQL/NginX with a bit of Redis on the side.
Salary - £36,000 to £40,000K per annum
To apply, please send a CV and covering letter to jobs@builderstorm.com. Please include a link to code examples and describe your existing server maintenance experience.
I've been doing a lot of flow diagrams and PlantUML has been invaluable.
I specifically like it because sharing the flow means sharing some text, which itself is vaguely human-readable.
There's an online renderer (bottom of the page in the above link), which means simple diagrams are also quick to create and view.
It's got a few different modes that it understands but I'd definitely add it to the list when you need simple vector graphics.
Has an online split screen view with your text on one side, and the diagram in the other. It's quite crude - no auto refresh, for example - but it works.
The best thing about plant is that you don't draw things out. you describe them. I actually feel like this is the way we SHOULD do diagrams so that we have flexibility to re-do them. I wish that Markdown would include plantUML natively.
PlantUML looks great, all the features I need, but their page is infested with fake ads, including fake download buttons of 5 different kinds. They also link to download page on SourceForge (hmmm, it's still alive) with even worse ads. Maybe it just me, but I immediately lost any desire to try it.
I second, third and fourth this. Anytime I'm not sure about a design, I sketch it out in plantuml and play around with it. Every project of mine has at least one or two plantuml diagrams checked into it.
I can highly recommend the PlantUML plugin for Visual Studio Code [1]. I mainly use this for sequence diagrams and component diagrams. The plugin makes editing and previewing the diagrams awesome.
Also checkout PlantUML integration for GitLab [2]. We recently deployed this at work, so not many miles yet, but looks pretty awesome. Main feature is to render embedded PlantUML markup in text files (markdown).
My only complaint is that you can't manipulate layout directly. You can do some hacks like invisible directional arrows, but ultimately any change you make risks turning your beautiful diagram into complete spaghetti.
I wish there was a tool combining plaintext description with explicit layouting.
Use plantuml a ton. Their google docs integration is quirky (it is hard to tell if you are going to edit the text in the doc or the diagram) but it's fast and anyone can edit it easily; I love it.
I use a combination of plant for sequence flows and lucid for arch diagrams.
I'm 100 agree! Plantuml is great, not as pretty as other tools but build diagrams for internal doc is awesome!like conflucence, wiki, sphinx, etc.. I'm in love with!
World First Ltd | Millbank Tower, London | Full time | ONSITE
World First is an established currency company. We have a medium sized IT team looking for PHP developers to continue development on the existing World First systems. The stack is PHP, Apache/Nginx and MySQL.
World First Ltd | Millbank Tower, London | Full time | ONSITE
World First is an established currency company. We have a medium sized IT team looking for PHP developers to continue development on the existing World First systems. The stack is PHP, RabbitMQ, Apache/Nginx and MySQL.
World First Ltd | Millbank Tower, London | Full time | ONSITE
World First is an established currency company. We have a medium sized IT team looking for PHP developers to continue development on the existing World First systems. The stack is PHP, RabbitMQ, Apache/Nginx and MySQL.
World First Ltd | Millbank Tower, London | Full time | ONSITE
World First is an established currency company. We have a medium sized IT team looking for PHP developers to continue development on the existing World First systems. The stack is PHP, RabbitMQ, Apache/Nginx and MySQL.
