As the Software Development team (ca. 10 members) at Age Partnership we build .NET applications and services for our colleagues in roles such as Financial Advisors, Administrators and Customer Solutions Agents in the Financial Services sector.
Apply through the above portal or email adam dot morgan at age partnership dot com for more information. At the moment we can only accept candidates with right to work in the UK.
As the Software Development team (ca. 10 members) at Age Partnership we build
.NET applications and services for our colleagues in roles such as Financial
Advisors, Administrators and Customer Solutions Agents in the Financial
Services sector.
I too got bored of having to go through every little transaction and categorising them according to my budget. I had already simplified my expenses budget down to three categories; essentials, luxuries and goals.
My solution was to open a dedicated current account and or credit card for each category. This makes assigning a category to transactions simple because I know which budget category each account is designated to.
This also helps with day-to-day budgeting because I have setup scheduled transactions to top-up my essentials and luxuries bank accounts with the correct amount of funds from my savings. A side effect is the stark reminder that using the credit cards eats away my goals budget because I've already spent my allocated funds for essentials or luxuries.
One downside here is losing the credit card protection on some purchases. The work around is to transfer funds back to savings when making these purchases. Another is that it's difficult to adopt immediately because opening several accounts may affect credit rating or rouse suspicion from financial institutions.
He alludes to the fact that the text you wrote as a comment is transmitted as "information" in the form of bytes.
But to formulate a counterpoint to this argument and support your original comment: The bytes we send via cables to transmit text are at a basic level just that: bytes. Ones and zeros. What makes these bytes understandable information is the fact that we have all agreed that a certain sequence of bits is assigned to a certain picture: A text symbol. This agreement has been a major source of pains and problems throughout the history of computing, think all these different text encodings and the problems that arise when you try to open a file with a different encoding than the one which it was saved with: You see a gibberish of symbols that do not make sense.
Which is why you have a point here: The pc does not care what information it transmits, it is only text because we have "taught" the pc to display a specific symbol (picture) when a certain sequence of bits is encountered.
Yep, no matter what, when I need to create a lightweight desktop app, I always come back to Windows Forms. Lazarus/FPC get brought up in these threads a good bit too, but I still prefer .NET because the ecosystem seems more active.
This saves me from throwing away my working copy when I switch to a different task;