• 0

Logo thoughts?


Question

Hey, not sure if this is in the right place or not..

I'm in the process of setting up a new personal design portfolio so I can work freelance over the summer and get some extra work, and just wanted to get some opinons on the logo/identity of the site. I'm aiming for a pixelated, neon kind of theme for the site, with grey, neon pink, green and blue being the colour scheme.

I've been staring at the logos for days now and I feel like I've lost all my judgement lol..so any feedback or criticism is welcome. I've got a feeling a couple of the logos are a bit filter crazy..I tend to do that when I get bored of something.

logo1.jpg

logo2.jpg

logo3.jpg

logo4.jpg

Comments appreciated :)

Link to comment
https://www.neowin.net/forum/topic/636129-logo-thoughts/
Share on other sites

22 answers to this question

Recommended Posts

  • 0

I have to admit I don't like the third and fourth, as they seem a little dull, but I totally dig the first one, maybe try playing with the in and out of the light line in the first one. The corona isn't quite working imho, other than that it's my favourite by far, great work. :)

Link to comment
https://www.neowin.net/forum/topic/636129-logo-thoughts/#findComment-589389684
Share on other sites

  • 0

While #1 does look kind of cool, I can't help but be reminded of the 80/90's when 3D animation first really popped into the world.

I like the fourth one, but without the corona pink thing. Without that it would be slick and web 2.0 and look excellent with a site designed in the same fashion.

Link to comment
https://www.neowin.net/forum/topic/636129-logo-thoughts/#findComment-589389807
Share on other sites

  • 0

I was kinda going for the retro 80/90's look kind of 'fused' with the modern web 2.0 look..thats how the idea and name came about...but it's just experimentation for now.

Do you mean without the whole dynamite logo? I did try it without and and it seemed kind of bland, as if something else was needed..

Link to comment
https://www.neowin.net/forum/topic/636129-logo-thoughts/#findComment-589389840
Share on other sites

  • 0

honest opinion:

i think you should steer clear of the 80's look. it is a turn off for most people imo. a simplistic web site is the way to go for a designer cause honestly clients will see your fancy logo and think that is all you can do or associate you with that kind of style. however, your portfolio should have as much of a variety as possible so that they can see you dont just do 80's pixel art.

-duritz

here are some examples i found:

PaleBirdDesign

Swirl

Link to comment
https://www.neowin.net/forum/topic/636129-logo-thoughts/#findComment-589389896
Share on other sites

  • 0

Last one for it's simplicity and versatility (it's look pretty good on anything). It'd go well on a light or dark background.

1st looks ok but its at too steep an angle. Maybe playing about with it would make it better (although I'd still prefer the last). 2nd Favs prob the 2nd one but although I would loose that circular logo think to the left perhaps.

Link to comment
https://www.neowin.net/forum/topic/636129-logo-thoughts/#findComment-589389909
Share on other sites

  • 0

Thanks for the advice.

Last one for it's simplicity and versatility (it's look pretty good on anything). It'd go well on a light or dark background.

After having a break for a bit and coming back to the PC, I think you're right. I plan to have a fairly dark background and it is probably the simplest and cleanest looking logo, and also very web 2.0

clients will see your fancy logo and think that is all you can do or associate you with that kind of style

I guess so, which I don't really want. I just want a nice clean style, with not too much attention on the logo but more on the variety of overall design skills shown on the site and portfolio

I decided to go with #4, whipped up a quick splash page while I crack on with the site now. The advice was much appreciated!

Link to comment
https://www.neowin.net/forum/topic/636129-logo-thoughts/#findComment-589390194
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Waymo recalls self-driving software after cars enter closed freeway work zones by Paul Hill Waymo, the self-driving car maker owned by Alphabet – the parent company of Google –, has recalled some of its fifth-generation Automated Driving Systems (ADS). It did so after some of its cars drove through closed construction zones. According to the National Highway Traffic Safety Administration (NHTSA), the affected vehicles were capable of driving through a closed freeway construction zone and continuing to drive at speed. The listing on the NHTSA website says that Waymo is currently developing a solution to fix this issue, but in the meantime, freeway driving is being restricted. Waymo will update its ADS software so that vehicles can detect when they can avoid entering construction zones. According to the Safety Recall Report, on April 20, 2026, Waymo’s Field Safety Committee began meetings reviewing an event from April 11, 2026, and five events from April 19, 2026, where Waymo’s autonomous vehicles didn’t recognize and drove past ramp closure signs into the pre-planned freeway construction zones. This took place in Phoenix, Arizona. Separately, on May 18, 2026, seven Waymo vehicles entered freeway lanes with active construction in the San Francisco Bay Area by driving between cones that were placed to show the lane was closed. On the back of both of these events, Waymo restricted freeway driving until it could address the issue. In June, Waymo’s Safety Board reviewed the issue and additional information related to ADS performances around construction zones; then, as a result, it decided to conduct a recall. This development is not good for Waymo as it adds to a growing list of technical hiccups its cars have experienced. Ultimately, it will lead to more scrutiny from lawmakers around the world who will be more cautious about letting autonomous vehicles on their roads without tighter regulation. For readers in areas where Waymo operates, does this news make you more wary about stepping into one of these vehicles?
    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • And with SO much better perf than the laggy mess that is Files.
  • Recent Achievements

    • First Post
      BizSAR earned a badge
      First Post
    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      598
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      80
    4. 4
      Michael Scrip
      76
    5. 5
      Steven P.
      69
  • Tell a friend

    Love Neowin? Tell a friend!