Yes but not as an employee. I'm a freelance python developer in Brussels, Belgium with just over 10 years exp and 32 years of age. The jump from employee to freelance wasn't easy but I sure wish I'd done it sooner. Short term and urgent contracts are worth a lot more than long term (2weeks versus 6months). You need to know your worth. I always calculate "how much time/costs" will you save as a result of my software: I want a fair piece of that. I focus on those shorter contracts. This year brought me almost twice what you're looking for (before tax). And a good accountant friend helps me keep as much as I legally can. Next year, I'm hoping to finally hit the 250k mark. As an employee just 2 years ago, I was amongst the "high paid employees", bringing in 55k net a year as a comparison. I suggest you look into doing the same with either becoming independent or starting a 1 person company. Contact an accountant ASAP to get the best advice on which structures best fit for you.
I've always stuck with very local (in the same city where I reside). I'm not against looking further or even remote but I've never had to look too far. It's normally a question of hours between posting my availability+updated CV and finding my next contract.
Another one man-team here, I find it fascinating how our stacks have at least a 90% overlap. Also funny that we both build analytics tools :)
For your front to back integration: I suggest you look into django-graphene and reacts apollo-client. That small addition to my stack has, at least, doubled if not tripled my churn speed. Throw in something like Django-channels and you get a modern full async websocket capable reactive framework :)
I love reading these. My daughter is only 2 but I've been compiling these tips as "learning hacks" to present as soon as she's ready since before she was conceived! I was also introduced to software development through "hacking" some 20 years ago and immediately fell in love (ms frontpage websites made in school and hosted on free hosting servers that injected banner ads.. my first ever hack was getting rid of those pesky ads with a bit of js back when "js is a dead technology, don't use it" :D) Ive since believed the thrill of "hacking" is the best intro into programming in that it's like a sort of gamification of logical thinking where you need to beat the game by finding and exploiting the weaknesses. Best of luck and please continue sharing your experiences!
A better way, such as? You mean like writing email / tweet requests directly to those responsible? What's this magical alternative method? FWIW, this method seems to have worked where the reasonable and common methods clearly failed. He bought his own nails and cross when he promised action would be taken but failed to execute.
> A better way, such as? You mean like writing email / tweet requests directly to those responsible? What's this magical alternative method? FWIW, this method seems to have worked where the reasonable and common methods clearly failed. He bought his own nails and cross when he promised action would be taken but failed to execute.
Is shaking your head, maybe adding an email filter or reporting as spam, and moving on with your life too traumatic an experience to go through? Is your life not worth living at that point unless you pull the fire alarm, evacuate the whole building, and publicly obtain vengeance?
I run into this all the time at work. We're at the point where we've spent 5 whole minutes talking about some software-driven bad behavior. Nobody is sure if this is the first time we've been affected by it (maybe it's the fifth time already, but it is starting to feel like deja vu.)
Someone suggests it isn't really a problem and we should ignore it. This person is very effective at their job and gets lots of stuff done once we've decided to take action. But there's a problem, actually tons of them, they're piling up now and we still have daily conversations about how they aren't a problem, (on a big long rotation so nobody seems to recall if we've seen this one before on any given day.)
No. Nobody said don't deal with the problem. Nobody said it isn't really a problem either. I'm saying go ahead and deal with the problem as best as you can, privately. If you still can't solve it at the source, then mitigate it on your end, and move on. Just because ∃ a problem and you encounter it for a long time, that doesn't mean you need to alarm people across the planet over it, or to publicly crucify someone in the process.
Nobody is being crucified. Nobody said they can't solve it at the source. They seem to want to solve it, at least outwardly. You're forgetting that only this forum seems to have the capability of reach, to reach those who are empowered to fix the problem.
If it was just a problem for this one person, well that would be a real anomaly. But adding a filter rule to always block is ignoring the problem, in the context of my work-life analogy, not fixing it.
In all software I've seen dealing with these issues (ofac, aml, Dow Jones listings, etc) the flagging should result in manual verification but you're able to configure risk allowances. They almost all certainly allow some bad transactions through accepting the potential risk/cost of actually hiring huge teams of manual auditors. Just being flagged does not always lead to audits.
I had tons of headaches trying to get toml to do what's trivial in Json (nested arrays of objects of arrays of ... etc). 1/10 would not try again. For very simple, hear "flat" config it checks out. But then, so does yaml or even ini files. Anything requiring composite types was just a nightmare. I'd even prefer xlm before using toml again.
toml really is best for mostly flat data. when your config grows more complex than that, i recommended you break it into multiple files and use directory structures or filenames to convey their relationship. or, of course, switch to a configuration format that is more well suited to deeply-nested data.
your comparison to yaml or ini is apt; toml's strength over yaml is syntax simplicity and toml is more-or-less a superset of ini (which itself is poorly-defined).
I would venture a guess that on the surface, it's about its verbosity and the pyramids of doom you can get when editing.
On a deeper level, I think they might be frustrated with the ability to develop custom formats (XSDs) which effectively make XML not one format, but a gazillion formats.
