|
Check your access logs for those IPs; odds are that you'll find multiple exploit attempt URLs pushed to your server by the Chinese traffic. They basically do Hail Mary attacks against every website all the time.
I have a WAF on a slightly (but not terribly much) more trafficked website and the crap that I see from them is just remarkable.
"Never attribute to malice that which can be explained by stupidity."
- Hanlon's Razor
|
|
|
|
|
|
They want to take over any server so they can launch their real attacks from an IP that does not track back to them.
|
|
|
|
|
That makes sense of the whole thing (+)
Ravings en masse^ |
---|
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein | "If you are searching for perfection in others, then you seek disappointment. If you seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
How we identify to others inside explosive contest (10)
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Explosive: T NT
How we identify to others: OUR NAME
Contest: TOURNAMENT
|
|
|
|
|
You are up tomorrow!
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Nice clue ?
"I didn't mention the bats - he'd see them soon enough" - Hunter S Thompson - RIP
|
|
|
|
|
I liked it?
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Yes so did I
"I didn't mention the bats - he'd see them soon enough" - Hunter S Thompson - RIP
|
|
|
|
|
Well, just had a first attempt before I have to go and do some work, and if it stays like it is, no, sorry, it's a stinker!
(Not sure if you were complimenting OG for his clue or asking if mine will be nice!)
modified 10-Aug-21 9:38am.
|
|
|
|
|
|
Greetings!
After spending more years that I care to discuss in a procession of unrewarding, soul crushing jobs, I am thinking of making a change to programming for my sunset years, and I'm looking for advice on the best ways to make that happen.
A bit of background; in the late 80s I signed my life away for a student loan to attend a "technical college" where I learned Pascal, C, 8086 Assembly, dBase/Clipper, and some RPGIV. I was, however, never able to actually land a programming job, and since food and rent cost money, I moved on to other things. (I don't call the experience wasted, I met my wife there.)
However, I'm just at that point where I am likely to go completely around the bend if I don't mmake a positive change. And while there seems to be a truckload of advice for younger people out there, I'm finding very little for older people such as myself. So, begging the indulgence of the gallery, I've some questions I wish to pose:
1. I am no spring chicken. While the word "junior" in a title would not bother me in the slightest, how likely are hiring managers going to be to hire a middle aged 'junior' programmer?
2. As near as I can tell, my best bet for languages would be C#, Java, C++, and JavaScript. Am I missing something there which would make me more employable? (of those 4, the only one I feel like I might struggle with is C++, not so much syntax wise, but just because of how rich the language is when used correctly.)
3. I am not above a boot camp style program with an ISA, but experiences with this soft of arrangement seem to be mixed. Can anyone who's actually gone that route relate their experiences? And would having a boot camp on my resume (as opposed to just being self taught) help or hinder my efforts?
I'm sure that there's an important question I may not be asking, so I'll again beg your indulgence in that and ask that if something jumps out, please speak up.
I also note that most of those who read this have jobs and responsibilities, so I understand if you don't drop everything to answer this. I honestly expect that the whole process is going to take at least a year, so its not like this is urgent. Meanwhile, I do thank you for your kind attention!
|
|
|
|
|
1) I am over 40 and started a new job two years ago (and probably not the last). So... there are still managers that valuate experience (not necessarily in exactly what the job is about).
2) It is mostly personal taste. Try all, see what you like more and get good at it. I personally think that with your background and what you say about c++, you will probably like c# too, and I with it you'll have covered a wide range of possibilities.
3) Boot Camps have not a good reputation over here. I suppose there are some good ones worth the money, but I think most of them are just a legal version of a scam. There are enough good resources out there to learn about many things. A good book, a couple of online sites and practice, practice, practice...
I don't know how fast you can learn and how good you were back at college, but many here will tell, that knowing the language is not necessarily the most important thing. Logical thinking, problem solving, abstraction, creativity, a bit stubbornness... those skills are the ones that can make the difference.
As I said, the first you should have clear is to know what you want to do and which of those languages is the one that you like most. Then get a compiler for it and start with something online, if you think "yeah, that's it" then buy a good book about it and start doing more complicated stuff and do not hesitate to come back with questions when you get stuck.
Good luck
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Cue Guns N Roses: Welcome to the Jungle
Kevin, I'm an old fart (just turned 0x3C ) and have been programming professionally since 1980. What you've described is certainly worthwhile and doable, especially if you're presently unhappy. I won't lie to you though, my gut says it's also not going to be nearly as easy as a 20-something fresh out of school would find.
Part of that arises from your time limit. I assume you do want to retire in the not-too-distant future. A common primary element to entry-level positions is that you are trainable, and will be around long enough to put that training to use. How much training and how long to use it depends upon the business' needs. The companies interested in you will be different if you're retiring in 10 years versus 5.
Another part, which you have no control over, is an industry-wide distaste for older programmers. In my case the assumption is that while I may be highly-skilled, those skills are only in older technologies. It's also assumed my thinking will be inflexible when it comes to working with other developers and business processes. Since you're starting out you don't have these issues, but hirers may assume you do if they discover your age.
My thinking is that you will need to find a 'niche' position, a job where the business needs programming, doesn't mind that you're inexperienced, and your *cough* maturity *cough* is appealing. If you can generalize (do IT stuff, networking, set up new PC's, install/maintain apps) in addition to the programming even better. A guy I worked with found a company where he is the sole tech guy in the place. He's revamped their IT setup and been programming applications for their CNC machines (they're a high-end tool and die sort of place). He's much happier now than he was when he worked for us.
Good luck!
Software Zen: delete this;
|
|
|
|
|
I had programmed for 10 years or so coming out of college with a degree in CS then had a nasty divorce and got out of programming for 13 years.
I spent 2 years learning and catching up with all I missed and finally landed a job programming in a small shop.
2 of us were hired me and a kid just out of college. I couldn't keep up and became miserable and after 1-1/3 years they let me go.
These young men just out of college are bright and quick and it's very hard to compete with them.
Good luck!
The less you need, the more you have.
Even a blind squirrel gets a nut...occasionally.
JaxCoder.com
|
|
|
|
|
I really hate to dump on your enthusiasm but I would think you have buckleys chance of breaking into large company development, they have too many young, cheap and enthusiastic fodder to entertain an older entrant. Besides you probably would not put up with the sh*t some companies throw at juniors.
Go with Gary's idea of finding a small organisation where you can fit in as the IT guy, learn the ins and outs of setting up and maintaining small networks and systems then move into development work.
The idea that you will become conversant with a language/technology within a year may be somewhat optimistic.
I do wish you all the luck you can get.
Never underestimate the power of human stupidity -
RAH
I'm old. I know stuff - JSOP
|
|
|
|
|
You might check out platforms like OutSystems.com or SalesForce.com.
They are more solution oriented, but you might find them interesting. They have two different approaches.
|
|
|
|
|
I'd look to the industry/industries in your procession of other jobs - and try to find ways to leverage any domain expertise you've picked up through that time.
Who are the vendors with products that specialise in those domains and how can apply your domain knowledge.
Maybe it leads a little more to a non-programming but still software related role:
- testing/validation
- design/workflow/user experience/business process analysis
- implementation or project management
- documentation/training
Of course, you didn't say what area you soul crushing jobs were - may well be one of the above...
|
|
|
|
|
Based on my recent experience job hunting, it seems JavaScript is the big one. C# with SQL (and Azure) has demand. I've found that in general, companies are shunning senior and fresh junior developers; they'd rather underpay mid-range developers with 5-10 years experience (who also won't make waves.)
One challenge you'll run into are hiring managers worried that you're after their job.
|
|
|
|
|
First the bad news: ageism is definitely a 'thing' in IT. Even those of us with many, many, years of experience can struggle to get work. You are right to fear that many hiring managers will put your CV in the 'No pile' after a 30 second scan.
On the up side, if you listen to the 'industry experts', (and that's not always wise!), there's a big skills shortage in the IT sector.
I agree with other posters: finding a small company that needs help with IT, may give you a way in - but, be careful that it's not a way in to something that is not going to give you the opportunities you are looking for.
I would definitely look at (free) on-line courses as a starter. This is not a recommendation, but I used Codecademy, (back in 2012), to learn PHP and found it very easy. But that may be because PHP is quite similar to my 'normal' programming language.
Good luck.
|
|
|
|
|
Look at local job listings -- what skills are requested? Let that drive what you decide to learn.
You have a year? Take some programming courses at a local community college (or the equivalent). I suggest JavaScript, SQL, and one of C# or Java. Additionally, get books likes SAMS Learn XXX in 21 Days. The books are not all the same quality, but contain organized lessons which get you into the the basics of a language.
Why actual courses? Night courses are often available so you may not have to disrupt your normal life. Also, the time span of a semester provides the time to think about what you're doing, not cram a language into your head and hope you can actually use the syntax.
This is where bootcamps fail -- they address the least important part of learning to program -- the language itself. Your ability to think and use the tools properly is important, not the syntax.
Write a real program. I've written and re-written an address book program in every language I've learned. I know the requirements really well, know what it needs to do, and it covers UI, DB, and everything in between.
You have ~30 years of doing something else? Leverage that if you can -- you are a domain expert in some field(s), so look for IT jobs related to those field(s). Being able to talk to the customer intelligibly using words they understand is a very marketable skill.
Consulting/contracting. Ageism, IME, is a lot less prevalent in contracting. But it's different from having a steady paycheck, so ya gotta prepare -- both mentally and financially for the differences.
These days remote work is more common -- a friend was laid off from a manufacturing firm after nearly 30 years (place was sold and cut up). He found a remote position AND he's on retainer with the owner of his old employer to help with systems the new owners do not understand.
|
|
|
|
|
Hey Kevin,
I'll echo a few of the previous comments. Ageism is rampant in IT. Most large companies are looking for younger talent. But all is not lost, I think you need to change your focus. I started with with the programs you learned, working on mainframes, then transitioning many times to different platforms. I am currently working on a C#/Blazor application. I think you will find breaking into "modern" application development will be difficult, but, there is another sector that pays very well, and is desperate for new talent.... Cobol. Banks and large organizations are trying to break free, but Cobol programmers are literally dying off. Younger people aren't interested, but it might be perfect for you.
Mark
|
|
|
|
|
You certainly wouldn't have a lot of young competition with COBOL, and the language has been updated and you'd be using modern editors, so it wouldn't be as annoying as it was in the 80's.
Learning to read COBOL code and figure out what it's doing would be a very useful skill- especially paired with SQL. They may be desperate enough to let you work remotely, too.
|
|
|
|
|
2. These languages are quite fine
Regarding 1. I'm sure there may be some bias depending on where are you located but I believe you'll be able to overcome it! Good luck with that!
|
|
|
|
|